Dave Beckett Nikki Rogers Participants in W3C's Semantic Web Deployment Working Group. Alistair Miles Sean Bechhofer An RDF vocabulary for describing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', other types of controlled vocabulary, and also concept schemes embedded in glossaries and terminologies. SKOS Vocabulary QUDT Schema - Version 2.1.32 abstract author contributor created creator modified replaces rights source subject title allowed pattern The 'qudt:example' property is used to annotate an instance of a class with a reference to a concept that is an example. The type of this property is 'rdf:Property'. This allows both scalar and object ranges. example An 'expression' is a finite combination of symbols that are well-formed according to rules that apply to units of measure, quantity kinds and their dimensions. expression Provides a way to reference a source that provided useful but non-normative information. informative reference The property "dtype:orderIndex" is an annotation property to specify a position that some value or structure will have. One use is to specify the place that a resource has in a sequence. One use is on property occurrences in class axioms. Here "vaem:orderIndex" is placed on a restriction to specify how that property may be transformed into a representation where ordering has some importance, for example, in XML Schema sequences. order index An annotation property that can be freely used on any kind of resource. The range of the property is "xsd:string" definition The property "vaem:dateCreated" is intended for general use as the name implies. The range of the property is set as "vaem:dateUnion" so as to allow a value to have a number of forms from a year only to a full timestamp An annotation used to reference a graph that elaborates (adds properties and axioms to) a resource isDefinedBy The property "vaem:lastUpdated" is intended for general use as the name implies. The range of the property is set as "vaem:dateUnion" so as to allow a value to have a number of forms from a year only to a full timestamp The property "vaem:logo" is a reference to an image that is used for publishing the ontology" As it name implies, a way to attach an annotation about a "todo" task todo The property "vaem:usesNonImportedResource" is used to express dependencies on resources from graphs that are not imported uses non-imported resource The property "vaem:withAttributionTo" is an annotation property that is either used to hold either a string or a reference to an instance of "voag:Attribution", from the VOAG ontology with attribution to The range of skos:altLabel is the class of RDF plain literals. skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. alternative label An alternative lexical label for a resource. Acronyms, abbreviations, spelling variants, and irregular plural/singular forms may be included among the alternative labels for a concept. Mis-spelled terms are normally included as hidden labels (see skos:hiddenLabel). change note A note about a modification to a concept. definition A statement or formal explanation of the meaning of a concept. editorial note A note for an editor, translator or maintainer of the vocabulary. example An example of the use of a concept. The range of skos:hiddenLabel is the class of RDF plain literals. skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. hidden label A lexical label for a resource that should be hidden when generating visual displays of the resource, but should still be accessible to free text search operations. history note A note about the past state/use/meaning of a concept. note A general note, for any purpose. This property may be used directly, or as a super-property for more specific note types. A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag. The range of skos:prefLabel is the class of RDF plain literals. skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. preferred label The preferred lexical label for a resource, in a given language. scope note A note that helps to clarify the meaning and/or the use of a concept. float percentage 0.0 100.0 integer percentage 0 100 is replaced by ANSI SQL Name applicable CGS unit applicable ISO unit applicable Imperial unit applicable physical constant applicable Planck unit applicable SI unit applicable US Customary unit See https://github.com/qudt/qudt-public-repo/wiki/Advanced-User-Guide#4-computing-applicable-units-for-a-quantitykind on how `qudt:applicableUnit` is computed from `qudt:hasQuantityKind` and then materialized applicable unit This property associates a system of quantities with an enumeration that enumerates the base dimensions of the system in canonical order. base dimension enumeration This property relates a unit of measure to the system of units in which it is defined as a base unit for the system. The base units of a system are used to define the derived units of the system by expressing the derived units as products of the base units raised to a rational power. is base unit of system basis belongs to system of quantities bit order Byte order is an enumeration of two values: 'Big Endian' and 'Little Endian' and is used to denote whether the most signiticant byte is either first or last, respectively. byte order Datatype name in the C programming language C Language name cardinality categorized as <p>A system of units is coherent with respect to a system of quantities and equations if the system of units is chosen in such a way that the equations between numerical values have exactly the same form (including the numerical factors) as the corresponding equations between the quantities. In such a coherent system, no numerical factor other than the number 1 ever occurs in the expressions for the derived units in terms of the base units. For example, the \(newton\) and the \(joule\). These two are, respectively, the force that causes one kilogram to be accelerated at 1 metre per (1) second per (1) second, and the work done by 1 newton acting over 1 metre. Being coherent refers to this consistent use of 1. In the old c.g.s. system , with its base units the centimetre and the gram, the corresponding coherent units were the dyne and the erg, respectively the force that causes 1 gram to be accelerated at 1 centimetre per (1) second per (1) second, and the work done by 1 dyne acting over 1 centimetre. So \(1\,newton = 10^5 dyne\), \(1 joule = 10^7 erg\), making each of the four compatible in a decimal sense within its respective other system, but not coherent therein.</p> https://en.wikipedia.org/wiki/Coherence_(units_of_measurement) coherent unit system data encoding datatype The default element in an enumeration default This property relates a unit of measure with the unit system that defines the unit. defined unit of system denominator dimension vector This property relates a unit of measure to the unit system in which the unit is derived from the system's base units with a proportionality constant of one. is coherent derived unit of system This property relates a unit of measure to the unit system in which the unit is derived from the system's base units without proportionality constant of one. is non-coherent derived unit of system This property relates a unit of measure to the system of units in which it is defined as a derived unit. That is, the derived unit is defined as a product of the base units for the system raised to some rational power. is derived unit of system dimension inverse dimension vector for SI An element of an enumeration element element kind encoding enumerated value enumeration exact match Provides a link to an image. figure This property relates a unit system with a unit of measure that is not defined by or part of the system, but is allowed for use within the system. An allowed unit must be convertible to some dimensionally eqiuvalent unit that is defined by the system. allowed unit has base quantity kind This property relates a system of units to a base unit defined within the system. The base units of a system are used to define the derived units of the system by expressing the derived units as products of the base units raised to a rational power. base unit A coherent unit of measurement for a unit system is a defined unit that may be expressed as a product of powers of the system's base units with the proportionality factor of one. coherent unit This property relates a unit system with a unit of measure that is defined by the system. defined unit has quantity kind dimension vector denominator part derived coherent unit has coherent derived unit This property relates a system of units to a unit of measure that is defined within the system in terms of the base units for the system. That is, the derived unit is defined as a product of the base units for the system raised to some rational power. derived unit has dimension dimension expression has dimension vector has quantity kind dimension vector numerator part prefix unit has quantity has quantity kind has reference quantity kind has rule has unit system is dimension in system This property relates a unit of measure with a system of units that either a) defines the unit or b) allows the unit to be used within the system. is unit of system numerator dimension vector om unit ORACLE SQL name ordered type permissible maths permissible transformation Associates a unit with the appropriate prefix, if any. prefix protocol buffers name python name denominator dimension vector numerator dimension vector a property to relate an observable thing with a quantity (qud:Quantity) quantity quantity value reference reference unit relevant quantity kind This property is used for qudt:Discipline instances to identify the Unit instances that are used within a given discipline. Relevant Unit rule type scale type system definition system derived quantity kind system dimension unit for value for quantity Vusal Basic name superseded by Aproperty for constructing composite data structures composite of The property "dtype:defaultValue" is a general property for specifying a value in situations where none is specified, or can be determined. In some cases of use, this property could have a scalar value and in other cases may need to refer to a first class concept that holds a "value object". For this reason, the type of this property is set as "rdf:Property" and the property is rangeless. default value A property for specifying a derivation relationship. derived from A property for specifying how member elements make up a data structure. has member An indirection pointer for relating a slot in am occurrence data structure, such as "dtype:ValueReference" with another resource. refers to datatype The property "dtype:value" is a general property that in some cases could have scalar values and in other cases may refer to a first class concept that is a "value object". For this reason, the type of this property is set as "rdf:Property" and the property is rangeless. value The property "vaem:hasAspect" is used to distinguish among sets of features of a domain or subject area. The term is borrowed from "aspect-oriented" programming, where it is used to separate concerns. An ontology may be characterized by this dimension so as to parition features that are orthogonal. For example, in a systems ontology we can distinguish aspects for "structure", "function", "behavior" and "interface". The property is an "rdf:Property" to allow both scalar and object values has aspect The property "vaem:hasDimension" is used categorize an ontology. In VAEM, the property is used to characterize an ontology graph. has dimension The property "vaem:hasDiscipline" is used to indicate relevance of a set of resources, or a resource itself, to a specific discipline of work or study. Examples of disciplines in the engineering domain are electrical engineering, mechanical engineering and, in the financial domain, risk assessment, investment analysis. In VAEM, the property is used as a dimension for characterizing an ontology graph. The property is an "rdf:Property" to allow both scalar and object values has discipline The property "vaem:hasDomain" is used to specify how a set of resources, or an individual resource is grounded in a domain, that is, a subject area of interest. Examples of domains are "enterprise", "process", "organization" and "system". In VAEM, the property is used as a dimension for characterizing an ontology graph. The property is an "rdf:Property" to allow both scalar and object values has domain The property "lms:hasGraphRole" is used to characterize how a resource participates in an ontology set. The property is used to specify the role that a graph plays, for example, an ontology graph can be a schema, vocabulary, dataset, script, or ruleset has graph role The property "vaemhasIdentifier" is intended for general use as a means to specifiy a unique reference to something. This is an object property that is a sub-property of "vame:id" has identifier The property "vaem:hasLicenseType" points to an entry in the VOAG ontology for licenses has license type The property "hasMetadata" is used to reference a metadata information structure. has metadata has owner A property that is used to refer to a "Steward", that is, the party or role that is responsible for maintaining an asset, in the case of VAEM, an ontology graph. has steward The property "vaem:hasViewpoint" is used to denote how a set of resources, or an individual resource, is relevant to a context of use. The term "viewpoint" is adopted from the ISO RM-ODP specifications and its more recent use in enterprise architecture descriptions. In VAEM, the property is used as a dimension for characterizing an ontology graph. The property is an "rdf:Property" to allow both scalar and object values has viewpoint To express how statements in a model can be reifiable, this property is used to explicitly associate a property with a user-defined sub-class of "rdf:Statement". A recommended way of using this is to declare the properties that share the same reification constructs as sub-properties of a parent property that carries the "vaem:reifiableBy" property. The parent property should be of type "rdf:Property" so that it can have both datatype and object properties as sub-properties. By this means use and transformations of a model can be understood through a fully specified metamodel. "vaem:reifiableBy" is rangeless in order to comply with OWL DL semantics. Its range would have been rdfs:Class in order to refer to "rdf:Statement" sub-classes reifiable by has broader match skos:broadMatch is used to state a hierarchical mapping link between two conceptual resources in different concept schemes. has broader transitive skos:broaderTransitive is a transitive superproperty of skos:broader. By convention, skos:broaderTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application. has close match skos:closeMatch is used to link two concepts that are sufficiently similar that they can be used interchangeably in some information retrieval applications. In order to avoid the possibility of "compound errors" when combining mappings across more than two concept schemes, skos:closeMatch is not declared to be a transitive property. skos:exactMatch is disjoint with each of the properties skos:broadMatch and skos:relatedMatch. has exact match skos:exactMatch is used to link two concepts, indicating a high degree of confidence that the concepts can be used interchangeably across a wide range of information retrieval applications. skos:exactMatch is a transitive property, and is a sub-property of skos:closeMatch. has top concept Relates, by convention, a concept scheme to a concept which is topmost in the broader/narrower concept hierarchies for that scheme, providing an entry point to these hierarchies. is in scheme Relates a resource (for example a concept) to a concept scheme in which it is included. A concept may be a member of more than one concept scheme. These concept mapping relations mirror semantic relations, and the data model defined below is similar (with the exception of skos:exactMatch) to the data model defined for semantic relations. A distinct vocabulary is provided for concept mapping relations, to provide a convenient way to differentiate links within a concept scheme from links between concept schemes. However, this pattern of usage is not a formal requirement of the SKOS data model, and relies on informal definitions of best practice. is in mapping relation with Relates two concepts coming, by convention, from different schemes, and that have comparable meanings has member Relates a collection to one of its members. For any resource, every item in the list given as the value of the skos:memberList property is also a value of the skos:member property. has member list Relates an ordered collection to the RDF list containing its members. has narrower match skos:narrowMatch is used to state a hierarchical mapping link between two conceptual resources in different concept schemes. Narrower concepts are typically rendered as children in a concept hierarchy (tree). has narrower Relates a concept to a concept that is more specific in meaning. By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources. has narrower transitive skos:narrowerTransitive is a transitive superproperty of skos:narrower. By convention, skos:narrowerTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application. skos:related is disjoint with skos:broaderTransitive has related Relates a concept to a concept with which there is an associative semantic relationship. has related match skos:relatedMatch is used to state an associative mapping link between two conceptual resources in different concept schemes. is in semantic relation with Links a concept to a concept related by meaning. This property should not be used directly, but as a super-property for all properties denoting a relationship of meaning between concepts. is top concept in scheme Relates a concept to the concept scheme that it is a top level concept of. was derived from An abbreviation for a unit is a short ASCII string that is used in place of the full name for the unit in contexts where non-ASCII characters would be problematic, or where using the abbreviation will enhance readability. When a power of abase unit needs to be expressed, such as squares this can be done using abbreviations rather than symbols. For example, <em>sq ft</em> means <em>square foot</em>, and <em>cu ft</em> means <em>cubic foot</em>. abbreviation acronym bits bytes conversion multiplier conversion offset Alphabetic Currency Code as defined by ISO 4217. For example, US Dollar has the code 'USD'. currency code https://en.wikipedia.org/wiki/ISO_4217 The currency exponent indicates the number of decimal places between a major currency unit and its minor currency unit. For example, the US dollar is the major currency unit of the United States, and the US cent is the minor currency unit. Since one cent is 1/100 of a dollar, the US dollar has a currency exponent of 2. However, the Japanese Yen has no minor currency units, so the yen has a currency exponent of 0. currency exponent Numeric currency Code as defined by ISO 4217. For example, US Dollar has the number 840. currency number https://en.wikipedia.org/wiki/ISO_4217 data structure dbpedia match deprecated dimension exponent dimension exponent for amount of substance dimension exponent for electric current dimension exponent for length dimension exponent for luminous intensity dimension exponent for mass dimension exponent for thermodynamic temperature dimension exponent for time dimensionless exponent exact constant figure caption figure label height The "qudt:id" is an identifier string that uniquely identifies a QUDT concept. The identifier is constructed using a prefix. For example, units are coded using the pattern: "UCCCENNNN", where "CCC" is a numeric code or a category and "NNNN" is a digit string for a member element of that category. For scaled units there may be an addition field that has the format "QNN" where "NN" is a digit string representing an exponent power, and "Q" is a qualifier that indicates with the code "P" that the power is a positive decimal exponent, or the code "N" for a negative decimal exponent, or the code "B" for binary positive exponents. qudt id image image location This property is used to identify a Quantity instance that is a measure of a change, or interval, of some property, rather than a measure of its absolute value. This is important for measurements such as temperature differences where the conversion among units would be calculated differently because of offsets. is Delta Quantity is metric unit Provides a way to reference the ISO unit definition. normative reference (ISO) java name Javascript name landscape latex definition The symbol is a glyph that is used to represent some concept, typically a unit or a quantity, in a compact form. For example, the symbol for an Ohm is \(ohm\). This contrasts with 'unit:abbreviation', which gives a short alphanumeric abbreviation for the unit, 'ohm' for Ohm. latex symbol length literal lower bound math definition mathML definition matlab name maxExclusive is the exclusive upper bound of the value space for a datatype with the ordered property. The value of maxExclusive must be in the value space of the base type or be equal to {value} in {base type definition}. max exclusive maxInclusive is the inclusive upper bound of the value space for a datatype with the ordered property. The value of maxInclusive must be in the value space of the base type. max inclusive Microsoft SQL Server name minExclusive is the exclusive lower bound of the value space for a datatype with the ordered property. The value of minExclusive must be in the value space of the base type or be equal to {value} in {base type definition}. min exclusive minInclusive is the inclusive lower bound of the value space for a datatype with the ordered property. The value of minInclusive must be in the value space of the base type. min inclusive MySQL name A negative change limit between consecutive sample values for a parameter. The Negative Delta may be the encoded value or engineering units value depending on whether or not a Calibrator is defined. negative delta limit Provides a way to reference information that is an authorative source providing a standard definition normative reference ODBC name OLE DB (Object Linking and Embedding, Database, sometimes written as OLEDB or OLE-DB), an API designed by Microsoft, allows accessing data from a variety of sources in a uniform manner. The API provides a set of interfaces implemented using the Component Object Model (COM); it is otherwise unrelated to OLE. http://en.wikipedia.org/wiki/OLE_DB http://msdn.microsoft.com/en-us/library/windows/desktop/ms714931(v=vs.85).aspx OLE DB name online reference order out of scope A plain text description is used to provide a description with only simple ASCII characters for cases where LaTeX , HTML or other markup would not be appropriate. description (plain text) A positive change limit between consecutive sample values for a parameter. The Positive Delta may be the encoded value or engineering units value depending on whether or not a Calibrator is defined. Positive delta limit prefix multiplier The relative standard uncertainty of a measurement is the (absolute) standard uncertainty divided by the magnitude of the exact value. relative standard uncertainty si units expression The standard uncertainty of a quantity is the estimated standard deviation of the mean taken from a series of measurements. standard uncertainty The symbol is a glyph that is used to represent some concept, typically a unit or a quantity, in a compact form. For example, the symbol for an Ohm is \(ohm\). This contrasts with 'unit:abbreviation', which gives a short alphanumeric abbreviation for the unit, 'ohm' for Ohm. symbol upper bound url vector magnitude width A property for expressing an encoded value. The range has been set to "xsd:anySimpleType" to allow for a variety of scalar datatypes. code A boolean flag to state that a value is invalid with respect to its type. is invalid A general purpose property for holding string literals. literal The property "dtype:order" provides a means to specify a precedence. One use of order is in specifying ordered enumerations such as "voag:ConfidentialityLevel". A similar property, but with an important type difference, is "vaem:orderIndex". This is for use on property occurrences in class axioms where it can be placed on a restriction to specify how that property may be transformed into other representations where ordering has some importance, for example, in XML Schema sequences. Whereas "vaem:order" is a datatype property, "vaem:orderIndex" is an annotation property. order position The property "vaem:abbreviation" provides a common way to define a commonly used abbreviation on a resource abbreviation The property "vaem:acronym" provides a common way to define a commonly used abbreviation on a resource acronym The property "vaem:date" is intended for general use as the name implies. The range of the property is set as "vaem:dateUnion" so as to allow a value to have a number of forms from a year only to a full timestamp. The property is also the parent of all dates so that queries can be made for any date on an ontology date description The property "vaem:filePrefix" is for specifying a preferred file prefix for a graph. For example a schema graph may be given the file prefix "SCHEMA" followed by an underscore "_". file prefix The property "vaem:id" is intended for general use as a means to specifiy an identifier. The type of this property is intentionally set to "rdf:Property" so that use of the property can allow both object and scaler values. For this reason, the property is rangeless id The property "vaem:intent" is used to outline a statement of purpose. This typically expresses one or more desired outcomes intent The property "vaem:latestPublishedVersion"is a URL to documentation for the latest version of a graph. latest published version The property "vaem:name" is intended for general use. In many cases "rdfs:label" could be used give names to resources. In the case where compliance with a specific naming rule is needed, "vaem:name" allows a resource to carry a name that is used in more specific contexts. name The property "vaem:namespace" is the onotlogy URI with which a graph is primarily associated. The intent is to allow multiple graphs to define statements for resources in the same Ontology namespace. For example, a foundation level graph with the base URI of "http://www.somesite.com/1.0/schema/OurOntology" may define general concepts for "OurOntology". Another graph with the base URI "http://www.somesite.com/1.0/schema/level2/OurOntology" may add more specific details to the same "OurOntology". Each of these two graphs would carry the same value for "vaem:namespace", that is, "http://www.somesite.com/schema/OurOntology". In other words, an ontology URI is the URI associated with the resources of a controlled namespace. On the other hand the graph URIs (the base URIs) identify the graphs that hold resources that make up an ontology namespace The property "vaem:namespacePrefix" specifes a short handle or label for the URI of an Ontology. Multiple graphs can define statements for resources in the same Ontololgy namespace. For example, a foundation level graph with the base URI of "http://www.somesite.com/1.0/schema/OurOntology" may define general concepts for "OurOntology". Another graph with the base URI "http://www.somesite.com/1.0/schema/level2/OurOntology" may add more specific details to the same "OurOntology". Each of these two graphs would carry the same value for "vaem:namespacePrefix", for this example, perhaps, "ourOntology" namespace prefix owner The property "vaem:previousPublishedVersion"is a URL to documentation for the previous version of a graph. previous published version A description of a justification for some other assertion or value rationale The property "vaem:rdfxmlFileURL" is used to provide a link to the location of the ontology's RDF/XML file RDF/XML file URL The property "vaem:releaseDate" is intended for general use as the name implies. The range of the property is set as "vaem:dateUnion" so as to allow a value to have a number of forms from a year only to a full timestamp release date The property "vaem:revision" is a property intended for general use as the name implies. revision The property "vaem:specificity" is intended to specify the level of detail of an ontology. The values that can be set for this property are restriced to an integer from 1 to 5. An ontology at level 1 has concepts of more general applicability than one at level 5. By having graphs at different levels of specificity it is possible to support greater modularity for selective imports specificity title The property "vaem:turtleFileURL" is used to provide a link to the location of the ontology's turtle file turtle file URL The property "vaem:url" is intended for general use as the name implies. The range of the property is set as an XSD URI url notation A notation, also known as classification code, is a string of characters such as "T58.5" or "303.4833" used to uniquely identify a concept within the scope of a given concept scheme. By convention, skos:notation is used with a typed literal in the object position of the triple. 0 0 Quantity Kind (abstract) Aspect Class 1 1 http://en.wikipedia.org/wiki/Dimensional_analysis http://web.mit.edu/2.25/www/pdf/DA_unified.pdf <p class="lm-para">A <em>Dimension</em> expresses a magnitude for a base quantiy kind such as mass, length and time.</p> <p class="lm-para">DEPRECATED - each exponent is expressed as a property. Keep until a validaiton of this has been done.</p> Base Dimension Magnitude A <em>Binary Prefix</em> is a prefix for multiples of units in data processing, data transmission, and digital information, notably the bit and the byte, to indicate multiplication by a power of 2. Binary Prefix A bit encoding is a correspondence between the two possible values of a bit, 0 or 1, and some interpretation. For example, in a boolean encoding, a bit denotes a truth value, where 0 corresponds to False and 1 corresponds to True. Bit Encoding Boolean encoding type This class contains the various ways that information may be encoded into bytes. Byte Encoding 1 The class of all character encoding schemes, each of which defines a rule or algorithm for encoding character data as a sequence of bits or bytes. Char Encoding Type 1 1 Provides a simple way of making citations. Citation 0 1 Comment 1 1 1 1 1 1 The root class for all QUDT concepts. QUDT Concept 1 Used to specify the values of a constant. Constant value Used for all units that express counts. Examples are Atomic Number, Number, Number per Year, Percent and Sample per Second. Counting Unit 1 Currency Units have their own subclass of unit because: (a) they have additonal properites such as 'country' and (b) their URIs do not conform to the same rules as other units. Used for all units that express currency. Currency Unit 1 1 1 <p><em>Data Encoding</em> expresses the properties that specify how data is represented at the bit and byte level. These properties are applicable to describing raw data.</p> Data Encoding 1 1 1 1 1 1 1 1 1 1 1 1 1 A data type is a definition of a set of values (for example, "all integers between 0 and 10"), and the allowable operations on those values; the meaning of the data; and the way values of that type can be stored. Some types are primitive - built-in to the language, with no visible internal structure - e.g. Boolean; others are composite - constructed from one or more other types (of either kind) - e.g. lists, arrays, structures, unions. Object-oriented programming extends this with classes which encapsulate both the structure of a type and the operations that can be performed on it. Some languages provide strong typing, others allow implicit type conversion and/or explicit type conversion. http://en.wikipedia.org/wiki/Data_type http://foldoc.org/data+type http://www.princeton.edu/~achaney/tmve/wiki100k/docs/Data_type.html QUDT Datatype Date Time encodings are logical encodings for expressing date/time quantities as strings by applying unambiguous formatting and parsing rules. Date Time String Encoding Type A <em>Decimal Prefix</em> is a prefix for multiples of units that are powers of 10. Decimal Prefix A Dimensionless Unit is a quantity for which all the exponents of the factors corresponding to the base quantities in its quantity dimension are zero. Dimensionless Unit Discipline 1 1 An encoding is a rule or algorithm that is used to convert data from a native, or unspecified form into a specific form that satisfies the encoding rules. Examples of encodings include character encodings, such as UTF-8. Encoding 1 1 1 <p>This class is for all enumerated and/or coded values. For example, it contains the dimension objects that are the basis elements in some abstract vector space associated with a quantity kind system. Another use is for the base dimensions for quantity systems. Each quantity kind system that defines a base set has a corresponding ordered enumeration whose elements are the dimension objects for the base quantity kinds. The order of the dimensions in the enumeration determines the canonical order of the basis elements in the corresponding abstract vector space.</p> <p>An enumeration is a set of literals from which a single value is selected. Each literal can have a tag as an integer within a standard encoding appropriate to the range of integer values. Consistency of enumeration types will allow them, and the enumerated values, to be referred to unambiguously either through symbolic name or encoding. Enumerated values are also controlled vocabularies and as such need to be standardized. Without this consistency enumeration literals can be stated differently and result in data conflicts and misinterpretations.</p> <p>The tags are a set of positive whole numbers, not necessarily contiguous and having no numerical significance, each corresponding to the associated literal identifier. An order attribute can also be given on the enumeration elements. An enumeration can itself be a member of an enumeration. This allows enumerations to be enumerated in a selection. Enumerations are also subclasses of Scalar Datatype. This allows them to be used as the reference of a datatype specification.</p> http://en.wikipedia.org/wiki/Enumeration Enumerated Value 1 1 1 Enumeration scale 1 1 1 1 1 1 1 Figure A "Encoding" with the following instance(s): "Double Precision Encoding", "Single Precision Real Encoding". Floating Point Encoding The encoding scheme for integer types Integer Encoding https://en.wikipedia.org/wiki/Level_of_measurement <p>The interval type allows for the degree of difference between items, but not the ratio between them. Examples include temperature with the Celsius scale, which has two defined points (the freezing and boiling point of water at specific conditions) and then separated into 100 intervals, date when measured from an arbitrary epoch (such as AD), percentage such as a percentage return on a stock,[16] location in Cartesian coordinates, and direction measured in degrees from true or magnetic north. Ratios are not meaningful since 20 °C cannot be said to be "twice as hot" as 10 °C, nor can multiplication/division be carried out between any two dates directly. However, ratios of differences can be expressed; for example, one difference can be twice another. Interval type variables are sometimes also called "scaled variables", but the formal mathematical term is an affine space (in this case an affine line).</p> <p>Characteristics: median, percentile &amp; Monotonic increasing (order (&lt;) &amp; totally ordered set</p> median, percentile & Monotonic increasing (order (<)) & totally ordered set Interval scale Logarithmic units are abstract mathematical units that can be used to express any quantities (physical or mathematical) that are defined on a logarithmic scale, that is, as being proportional to the value of a logarithm function. Examples of logarithmic units include common units of information and entropy, such as the bit, and the byte, as well as units of relative signal strength magnitude such as the decibel. Logarithmic Unit Maths Function Type National Institute of Standards and Technology (NIST) Special Publication 811 Comments on some quantities and their units NIST SP~811 Comment https://en.wikipedia.org/wiki/Level_of_measurement A nominal scale differentiates between items or subjects based only on their names or (meta-)categories and other qualitative classifications they belong to; thus dichotomous data involves the construction of classifications as well as the classification of items. Discovery of an exception to a classification can be viewed as progress. Numbers may be used to represent the variables but the numbers do not have numerical value or relationship: For example, a Globally unique identifier. Examples of these classifications include gender, nationality, ethnicity, language, genre, style, biological species, and form. In a university one could also use hall of affiliation as an example. Nominal scale Numeric union 1 Describes how a data or information structure is ordered. Ordered type 1 https://en.wikipedia.org/wiki/Level_of_measurement The ordinal type allows for rank order (1st, 2nd, 3rd, etc.) by which data can be sorted, but still does not allow for relative degree of difference between them. Examples include, on one hand, dichotomous data with dichotomous (or dichotomized) values such as 'sick' vs. 'healthy' when measuring health, 'guilty' vs. 'innocent' when making judgments in courts, 'wrong/false' vs. 'right/true' when measuring truth value, and, on the other hand, non-dichotomous data consisting of a spectrum of values, such as 'completely agree', 'mostly agree', 'mostly disagree', 'completely disagree' when measuring opinion. Ordinal scale 0 Organization 1 1 1 Plane Angle Unit 0 0 1 Prefix 1 1 1 1 1 1 <p><em>Quantifiable</em> ascribes to some thing the capability of being measured, observed, or counted.</p> Quantifiable 0 0 0 0 0 0 0 1 1 1 1 1 1 http://www.electropedia.org/iev/iev.nsf/display?openform&ievref=112-01-04 A <b>Quantity Kind</b> is any observable property that can be measured and quantified numerically. Familiar examples include physical properties such as length, mass, time, force, energy, power, electric charge, etc. Less familiar examples include currency, interest rate, price to earning ratio, and information capacity. Quantity Kind 1 1 1 1 1 1 1 1 1 1 http://en.wikipedia.org/wiki/Dimensional_analysis http://web.mit.edu/2.25/www/pdf/DA_unified.pdf <p class="lm-para">A <em>Quantity Kind Dimension Vector</em> describes the dimensionality of a quantity kind in the context of a system of units. In the SI system of units, the dimensions of a quantity kind are expressed as a product of the basic physical dimensions mass (\(M\)), length (\(L\)), time (\(T\)) current (\(I\)), amount of substance (\(N\)), luminous intensity (\(J\)) and absolute temperature (\(\theta\)) as \(dim \, Q = L^{\alpha} \, M^{\beta} \, T^{\gamma} \, I ^{\delta} \, \theta ^{\epsilon} \, N^{\eta} \, J ^{\nu}\).</p> <p class="lm-para">The rational powers of the dimensional exponents, \(\alpha, \, \beta, \, \gamma, \, \delta, \, \epsilon, \, \eta, \, \nu\), are positive, negative, or zero.</p> <p class="lm-para">For example, the dimension of the physical quantity kind \(\it{speed}\) is \(\boxed{length/time}\), \(L/T\) or \(LT^{-1}\), and the dimension of the physical quantity kind force is \(\boxed{mass \times acceleration}\) or \(\boxed{mass \times (length/time)/time}\), \(ML/T^2\) or \(MLT^{-2}\) respectively.</p> Quantity Kind Dimension Vector A <em>CGS Dimension Vector</em> is used to specify the dimensions for a C.G.S. quantity kind. CGS Dimension vector A <em>CGS EMU Dimension Vector</em> is used to specify the dimensions for EMU C.G.S. quantity kind. CGS EMU Dimension vector A <em>CGS ESU Dimension Vector</em> is used to specify the dimensions for ESU C.G.S. quantity kind. CGS ESU Dimension vector A <em>CGS GAUSS Dimension Vector</em> is used to specify the dimensions for Gaussioan C.G.S. quantity kind. CGS GAUSS Dimension vector A <em>CGS LH Dimension Vector</em> is used to specify the dimensions for Lorentz-Heaviside C.G.S. quantity kind. CGS LH Dimension vector ISO Dimension vector Imperial dimension vector Quantity Kind Dimension vector (SI) \(\textit{Quantity Type}\) is an enumeration of quanity kinds. It specializes \(\boxed{dtype:EnumeratedValue}\) by constrinaing \(\boxed{dtype:value}\) to instances of \(\boxed{qudt:QuantityKind}\). Quantity type 1 1 A <i>Quantity Value</i> expresses the magnitude and kind of a quantity and is given by the product of a numerical value <code>n</code> and a unit of measure <code>U</code>. The number multiplying the unit is referred to as the numerical value of the quantity expressed in that unit. Refer to <a href="http://physics.nist.gov/Pubs/SP811/sec07.html">NIST SP 811 section 7</a> for more on quantity values. Quantity value https://en.wikipedia.org/wiki/Level_of_measurement The ratio type takes its name from the fact that measurement is the estimation of the ratio between a magnitude of a continuous quantity and a unit magnitude of the same kind (Michell, 1997, 1999). A ratio scale possesses a meaningful (unique and non-arbitrary) zero value. Most measurement in the physical sciences and engineering is done on ratio scales. Examples include mass, length, duration, plane angle, energy and electric charge. In contrast to interval scales, ratios are now meaningful because having a non-arbitrary zero point makes it meaningful to say, for example, that one object has "twice the length" of another (= is "twice as long"). Very informally, many ratio scales can be described as specifying "how much" of something (i.e. an amount or magnitude) or "how many" (a count). The Kelvin temperature scale is a ratio scale because it has a unique, non-arbitrary zero point called absolute zero. Ratio scale 0 Rule Rule Type 1 1 1 1 1 1 1 1 Scalar data types are those that have a single value. The permissible values are defined over a domain that may be integers, float, character or boolean. Often a scalar data type is referred to as a primitive data type. Scalar Datatype 1 1 Scales (also called "scales of measurement" or "levels of measurement") are expressions that typically refer to the theory of scale types. Scale 1 Specifics whether a value should be signed or unsigned. Signedness type The solid angle subtended by a surface S is defined as the surface area of a unit sphere covered by the surface S's projection onto the sphere. A solid angle is related to the surface of a sphere in the same way an ordinary angle is related to the circumference of a circle. Since the total surface area of the unit sphere is 4*pi, the measure of solid angle will always be between 0 and 4*pi. Solid Angle Unit Statement A "Encoding" with the following instance(s): "UTF-16 String", "UTF-8 Encoding". String Encoding Type A "Structured Datatype", in contrast to scalar data types, is used to characterize classes of more complex data structures, such as linked or indexed lists, trees, ordered trees, and multi-dimensional file formats. Structured Data Type Symbol 0 1 A system of quantity kinds is a set of one or more quantity kinds together with a set of zero or more algebraic equations that define relationships between quantity kinds in the set. In the physical sciences, the equations relating quantity kinds are typically physical laws and definitional relations, and constants of proportionality. Examples include Newton’s First Law of Motion, Coulomb’s Law, and the definition of velocity as the instantaneous change in position. In almost all cases, the system identifies a subset of base quantity kinds. The base set is chosen so that all other quantity kinds of interest can be derived from the base quantity kinds and the algebraic equations. If the unit system is explicitly associated with a quantity kind system, then the unit system must define at least one unit for each quantity kind. From a scientific point of view, the division of quantities into base quantities and derived quantities is a matter of convention. System of Quantity Kinds http://dbpedia.org/resource/Category:Systems_of_units http://www.ieeeghn.org/wiki/index.php/System_of_Measurement_Units A system of units is a set of units which are chosen as the reference scales for some set of quantity kinds together with the definitions of each unit. Units may be defined by experimental observation or by proportion to another unit not included in the system. If the unit system is explicitly associated with a quantity kind system, then the unit system must define at least one unit for each quantity kind. System of Units Transform type Transform type 1 1 1 0 0 0 0 1 1 1 A unit of measure, or unit, is a particular quantity value that has been chosen as a scale for measuring other quantities the same kind (more generally of equivalent dimension). For example, the meter is a quantity of length that has been rigorously defined and standardized by the BIPM (International Board of Weights and Measures). Any measurement of the length can be expressed as a number multiplied by the unit meter. More formally, the value of a physical quantity Q with respect to a unit (U) is expressed as the scalar multiple of a real number (n) and U, as \(Q = nU\). http://dbpedia.org/resource/Category:Units_of_measure http://www.allmeasures.com/Fullconversion.asp Unit 1 User Quantity Kind 0 0 0 dtype:CodeList A codelist is a controlled vocabulary of terms that are used to represent permissible values of a variable in information systems. The representaiton of codes in "dtype" has been influenced by CCTS and UBL. Codelist dtype:CompositeCodeList A composite codelist is a codelist made up of other codelists. It does not introduce any new codes. Composite Code List 1 dtype:DerivedCodeList A derived codelist is a sublist of another codelist. The members that it has must be members of the source list. Derived Code List 0 1 1 1 1 1 dtype:EnumeratedValue The base class for datatypes that have values that are restriced to a set of literals or tokens. The members of the restriction may themselve be restriced by facets that apply to scalar data types. DTYPE Enumerated value dtype:Enumeration A type that serves as a container for the enumerated values of an enumeration. This enables the enumeration itself to be referenceable. One need for this is in determing the default value of an enumeration , another need is in the management of sub-enumerations and composite enumerations. DTYPE Enumeration dtype:SimpleCodeList A simple codelist is one made up only of enumerated values. Simple Code List 1 1 dtype:ValueReference A value reference is a pointer to an Enumerated Value. The original position of the value can be overridden by the position attribute. Value Reference vaem:Aspect Aspect is used to distinguish among sets of features of a domain or subject area. The term is borrowed from "aspect-oriented" programming, where it is used to separate concerns. An ontology may be characterized by this dimension so as to parition features that are orthogonal. For example, in a systems ontology there may be aspects for "structure", "function", "behavior" and "interface" or "interoperability". A viewpoint can be distinguished by "aspects". For example the "information viewpoint" of an application can be partitioned into separate graphs for the "security", "operational" and"data retention" aspects. Aspect Dimension VAEM Governed Object class is a placeholder for concepts that are fully defined by the voag:GovernedObject concept hierarchy for building a catalog of ontologies and graphs vaem:Dimension A dimension identifies a separation of concens that serves as a way to categorize an ontology graph. In VAEM, the notion of "Dimension" is partitioned into "Aspect", "Discipline", "Domain" and "Viewpoint". Domain vaem:Discipline A discipline is a specific area of work or study. Examples of disciplines in the engineering domain are electrical engineering, mechanical engineering and, in the financial domain, risk assessment, investment analysis. In VAEM, discipline is used as a dimension for characterizing an ontology graph Discipline Dimension vaem:Domain A domain is a subject area of interest. Examples of domains are "enterprise", "process", "organization" and "system". In VAEM, "Domain" is used as a dimension for characterizing an ontology graph Domain Dimension 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 vaem:GraphMetaData "vaem:GraphMetaData" defines basic metadata for the registration and publishing of a graph. For specificaiton of governance the vocabulary "VOAG" may be used. Graph Metadata 1 1 vaem:GraphRole GraphRole is used to characterize how a graph of resources participates in an ontology set. For example, a graph can be a schema, vocabulary, dataset, script, or ruleset Graph role 1 1 1 vaem:Party A "Party" is a generalization for an actor that may be realized as a person, organizaiton or named role. Party vaem:Viewpoint Viewpoint is used to denote how a set of resources, or an individual resource, is relevant to a context of use. The term "viewpoint" is adopted from the ISO RM-ODP specifications and its more recent use in enterprise architecture descriptions. The RM-ODP introducesd the concept of viewpoint to describe a system from a particular set of concerns. RM-ODP defines five viewpoints. Together they provide a complete description of a system: enterprise viewpoint, information viewpoint, computational viewpoint, engineering viewpoint, and technology viewpoint. In VAEM, "Viewpoint" is used as a dimension for characterizing an ontology graph. The viewpoints of an ontology may not always correpsond directly to those of a system but the idea of describing a subject area of interest from distinct viewpoints is still relevant. A viewpoint can be further distinguished by "aspects". For example the "information viewpoint" of an application can be partitioned into separate graphs for the "security", "operational" and"data retention" aspects. ViewpointDimension rdf:List rdf:Statement rdfs:Class rdfs:Datatype rdfs:Resource owl:Ontology owl:Thing skos:Collection Collection A meaningful collection of concepts. Labelled collections can be used where you would like a set of concepts to be displayed under a 'node label' in the hierarchy. skos:Concept Concept An idea or notion; a unit of thought. skos:ConceptScheme Concept Scheme A set of concepts, optionally including statements about semantic relationships between those concepts. Thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', and other types of controlled vocabulary are all examples of concept schemes. Concept schemes are also embedded in glossaries and terminologies. A concept scheme may be defined to include concepts from different sources. skos:OrderedCollection Ordered Collection An ordered collection of concepts, where both the grouping and the ordering are meaningful. Ordered collections can be used where you would like a set of concepts to be displayed in a specific order, and optionally under a 'node label'. big Big Endian 1 Bit Encoding 1 Boolean Encoding countable A set of numbers is called countably infinite if there is a way to enumerate them. Formally this is done with a bijection function that associates each number in the set with exactly one of the positive integers. The set of all fractions is also countably infinite. In other words, any set \(X\) that has the same cardinality as the set of the natural numbers, or \(| X | \; = \; | \mathbb N | \; = \; \aleph0\), is said to be a countably infinite set. http://www.math.vanderbilt.edu/~schectex/courses/infinity.pdf Countably Infinite Cardinality Type finite Any set \(X\) with cardinality less than that of the natural numbers, or \(| X | \\; < \; | \\mathbb N | \), is said to be a finite set. Finite Cardinality Type uncountable Any set with cardinality greater than that of the natural numbers, or \(| X | \; > \; | \mathbb N | \), for example \(| R| \; = \; c \; > |\mathbb N |\), is said to be uncountable. Uncountable Cardinality Type In mathematics, the cardinality of a set is a measure of the number of elements of the set. For example, the set 'A = {2, 4, 6}' contains 3 elements, and therefore 'A' has a cardinality of 3. There are two approaches to cardinality – one which compares sets directly using bijections and injections, and another which uses cardinal numbers. 1 7 bits of 1 octet Char Encoding http://dbpedia.org/resource/Category:SI_derived_units 64 Single Precision Real Encoding In computing, endianness is the ordering used to represent some kind of data as a sequence of smaller units. Typical cases are the order in which integer values are stored as bytes in computer memory (relative to a given memory addressing scheme) and the transmission order over a network or other medium. When specifically talking about bytes, endianness is also referred to simply as byte order. Most computer processors simply store integers as sequences of bytes, so that, conceptually, the encoded value can be obtained by simple concatenation. For an 'n-byte' integer value this allows 'n!' (n factorial) possible representations (one for each byte permutation). The two most common of them are: increasing numeric significance with increasing memory addresses, known as little-endian, and its opposite, called big-endian. http://dbpedia.org/resource/Enumeration 32 IEEE 754 1985 Real Encoding [0-9]{4}[0-9]{2}[0-9]{2}T[0-9]{2}[0-9]{2}[0-9]{2}.[0-9]+Z [0-9]{4}[0-9]{2}[0-9]{2}T[0-9]{2}[0-9]{2}[0-9]{2}Z ISO 8601 UTC Date Time - Basic Format little Little Endian 8 Long Unsigned Integer Encoding 1 OCTET Encoding partial Partial ordered structure. Partially Ordered http://dbpedia.org/resource/Physical_constant http://dbpedia.org/resource/Quantity signed Signed Scales, or scales of measurement (or categorization) provide ways of quantifying measurements, values and other enumerated values according to a normative frame of reference. Four different types of scales are typically used. These are interval, nominal, ordinal and ratio scales. 2 Short Signed Integer Encoding 2 Short Unsigned Integer Encoding 4 Signed Integer Encoding 32 Single Precision Real Encoding total Totally ordered structure. Totally Ordered true true unsigned Unsigned UTF-16 String 8 UTF-8 Encoding unordered Unordered structure. Unordered 4 Unsigned Integer Encoding Wikipedia true Used to provide an annotation for an informative reference. true true true A field code is a generic property for representing unique codes that make up other identifers. For example each QuantityKind class caries a domain code as its field code. true true Used to relate a class to one or more graphs where vocabularies for the class are defined. true true true true true true QUDT Schema Catalog Entry The ontology "dtype" provides a specification of simple data types such as enumerations and codelists. These are needed in support of the conversion of XML Schemas and UML Models to OWL. The purpose of "dtype" is to provide a foundation for expressing rich data types. These data types are typically needed when dealing with OWL representations of data structures derived from XML Schema. DTYPE http://www.linkedmodel.org/schema/dtype dtype TopQuadrant 1.1 Ralph Hodgson Datatype schema Datatype Ontology 2011-05-29 2014-06-28 Datatype Ontology Created with TopBraid Composer http://www.linkedmodel.org/schema/dtype# dtype COLLECTION A "vaem:CollectionGraph" is a graph that aggregates other graphs using "owl:imports" statements Collection graph CONSTRAINTS A "vaem:ConstraintsGraph" is a graph that holds SPIN constraints Constraints graph CONTROLLERS Controllers graph CURATION A "vaem:CurationGraph" is a graph to hold metadata that is needed to describe, govern and provision another graph. A curation graph will likely use VOAG and VAEM for this purpose. The property "vaem:curationGraph" is used to link to the graph (or graphs) being curated Curation graph DATA Data graph DOC Documentation graph FUNCTIONS Functions graph Specifies the schema for quantities, units and dimensions. Types are defined in other schemas. https://qudt.org/doc/2023/10/DOC_SCHEMA-QUDT-v2.1.html http://qudt.org/schema/qudt/ qudt qudt.org https://qudt.org/doc/2023/09/DOC_SCHEMA-QUDT-v2.1.html 2.1 http://qudt.org/2.1/schema/qudt Daniel Mekonnen David Price Jack Hodges James E. Masters Simon J D Cox Steve Ray 2011-04-20 Ralph Hodgson <p class="lm-para">The QUDT, or "Quantity, Unit, Dimension and Type" schema defines the base classes properties, and restrictions used for modeling physical quantities, units of measure, and their dimensions in various measurement systems. The goal of the QUDT ontology is to provide a unified model of, measurable quantities, units for measuring different kinds of quantities, the numerical values of quantities in different units of measure and the data structures and data types used to store and manipulate these objects in software.</p> <p class="lm-para">Except for unit prefixes, all units are specified in separate vocabularies. Descriptions are provided in both HTML and LaTeX formats. A quantity is a measure of an observable phenomenon, that, when associated with something, becomes a property of that thing; a particular object, event, or physical system. </p> <p class="lm-para">A quantity has meaning in the context of a measurement (i.e. the thing measured, the measured value, the accuracy of measurement, etc.) whereas the underlying quantity kind is independent of any particular measurement. Thus, length is a quantity kind while the height of a rocket is a specific quantity of length; its magnitude that may be expressed in meters, feet, inches, etc. Or, as stated at Wikipedia, in the language of measurement, quantities are quantifiable aspects of the world, such as time, distance, velocity, mass, momentum, energy, and weight, and units are used to describe their measure. Many of these quantities are related to each other by various physical laws, and as a result the units of some of the quantities can be expressed as products (or ratios) of powers of other units (e.g., momentum is mass times velocity and velocity is measured in distance divided by time).</p> 2023-10-19T10:34:34.948-04:00 This product includes all or a portion of the UCUM table, UCUM codes, and UCUM definitions or is derived from it, subject to a license from Regenstrief Institute, Inc. and The UCUM Organization. Your use of the UCUM table, UCUM codes, UCUM definitions also is subject to this license, a copy of which is available at ​http://unitsofmeasure.org. The current complete UCUM table, UCUM Specification are available for download at ​http://unitsofmeasure.org. The UCUM table and UCUM codes are copyright © 1995-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. THE UCUM TABLE (IN ALL FORMATS), UCUM DEFINITIONS, AND SPECIFICATION ARE PROVIDED 'AS IS.' ANY EXPRESS OR IMPLIED WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. The QUDT Ontologies are issued under a Creative Commons Attribution 4.0 International License (CC BY 4.0), available at https://creativecommons.org/licenses/by/4.0/. Attribution should be made to QUDT.org QUDT QUDT Schema - Version 2.1.32 http://unitsofmeasure.org/trac http://www.bipm.org/en/publications/si-brochure http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf https://books.google.com/books?id=pIlCAAAAIAAJ&dq=dimensional+analysis&hl=en https://www.nist.gov/physical-measurement-laboratory/special-publication-811 qudt Quantities, Units, Dimensions and Types (QUDT) Schema - Version 2.1.32 https://qudt.org/linkedmodels.org/assets/lib/lm/images/logos/qudt_logo-300x110.png QUDT Schema - Version 2.1.32 VAEM stands for "Vocabulary for Attaching Essential Metadata". What VAEM regards as essential metadata is data about dates and times, confidentiality, and other characterisitic qualifiers of the ontology, but also references to where a ontology is documented and where to find ontology registration for governance, attribution and provenance. VAEM makes use of some properties from the DC terms vocabulary using the namespace prefix "dct". VAEM is OWL-DL compliant. The purpose of VAEM is to provide, by import, a foundation for commonly needed resources for metadata on an ontology. http://www.linkedmodel.org/doc/2014/SCHEMA_vaem-v2.0 VAEM http://www.linkedmodel.org/schema/vaem# vaem TopQuadrant, Inc. http://linkedmodel.org/doc/vaem/1.2/ http://www.linkedmodel.org/2.0/schema/SCHEMA_vaem-v2.0.rdf 2.0 Vocabulary for Attaching Essential Metadata (VAEM) - Version 2.0 http://www.linkedmodel.org/2.0/schema/SCHEMA_vaem-v2.0.ttl VAEM stands for "Vocabulary for Attaching Essential Metadata". What VAEM regards as essential metadata is data about dates and times, confidentiality, and other characterisitic qualifiers of the ontology, but also references to where a ontology is documented and where to find ontology registration for governance, attribution and provenance. VAEM makes use of some properties from the DC terms vocabulary using the namespace prefix "dct". VAEM is OWL-DL compliant. 2011-04-20 2014-07-26 VAEM Version 2.0 Metadata http://linkedmodel.org/lib/lm/images/logos/TopBraid-RDM-Graph-Logo.png VAEM is issued under a Creative Commons Attribution Share Alike 3.0 United States License. Attribution should be made to TopQuadrant, Inc. VAEM Schema Version 2.0 Metadata LINKSET A "vaem:LinkSetGraph" is a graph that holds statements that specify links between resources Link Set graph MAPPINGS A graph that specifies a transformation of a graph into another graph or graphs. Invariably this is a SPINMap graph using SPARQL Rules (SPIN) to express the transforms. Mapping graph PROXY Proxy graph QUDT is a non-profit organization that governs the QUDT ontologies. qudt.org http://www.qudt.org QUDT RULES Rules Graph SCHEMA Schema graph SCRIPT Script graph TopQuadrant, Inc. http:/www.topquadrant.com TopQuadrant TRANSFORMS Transforms graph VIEWS View graph VOCAB An RDF/OWL Graph that is a controlled set of instances. Vocabulary graph 1 1 1 1 1 1 1 [\x21,\x23-\x27,\x2a,\x2c,\x30-\x3c,\x3e-\x5a,\x5c,\x5e-\x7a,\x7c,\x7e]+ [\x21,\x23-\x27,\x2a,\x2c,\x30-\x3c,\x3e-\x5a,\x5c,\x5e-\x60,\x7c,\x7e]+ [\x21-\x7e]+ [\x21-\x60,\x7b-\x7e]+ 1 0 1 0 0 1 1 1 1 1 0 description QUDT Schema - Version 2.1.32 All units relating to specification of angles. Angle unit An aspect is an abstract type class that defines properties that can be reused. QUDT Aspect In mathematics, the cardinality of a set is a measure of the number of elements of the set. For example, the set \(A = {2, 4, 6}\) contains 3 elements, and therefore \(A\) has a cardinality of 3. There are two approaches to cardinality – one which compares sets directly using bijections and injections, and another which uses cardinal numbers. http://en.wikipedia.org/wiki/Cardinal_number http://en.wikipedia.org/wiki/Cardinality Cardinality Type A DerivedUnit is a type specification for units that are derived from other units. Derived Unit http://en.wikipedia.org/wiki/Endianness Endian Type Enumerated Quantity http://en.wikipedia.org/wiki/Enumerated_type http://en.wikipedia.org/wiki/Enumeration <p>An enumeration is a set of literals from which a single value is selected. Each literal can have a tag as an integer within a standard encoding appropriate to the range of integer values. Consistency of enumeration types will allow them, and the enumerated values, to be referred to unambiguously either through symbolic name or encoding. Enumerated values are also controlled vocabularies and as such need to be standardized. Without this consistency enumeration literals can be stated differently and result in data conflicts and misinterpretations.</p> <p>The tags are a set of positive whole numbers, not necessarily contiguous and having no numerical significance, each corresponding to the associated literal identifier. An order attribute can also be given on the enumeration elements. An enumeration can itself be a member of an enumeration. This allows enumerations to be enumerated in a selection. Enumerations are also subclasses of <em>Scalar Datatype</em>. This allows them to be used as the reference of a datatype specification.</p> Enumeration A type of string in which some characters may be wrapped with '\(' and '\) characters for LaTeX rendering. Latex String A physical constant is a physical quantity that is generally believed to be both universal in nature and constant in time. It can be contrasted with a mathematical constant, which is a fixed numerical value but does not directly involve any physical measurement. There are many physical constants in science, some of the most widely recognized being the speed of light in vacuum c, Newton's gravitational constant G, Planck's constant h, the electric permittivity of free space ε0, and the elementary charge e. Physical constants can take many dimensional forms, or may be dimensionless depending on the system of quantities and units used. Physical Constant <p class="lm-para">A <b>quantity</b> is the measurement of an observable property of a particular object, event, or physical system. A quantity is always associated with the context of measurement (i.e. the thing measured, the measured value, the accuracy of measurement, etc.) whereas the underlying <b>quantity kind</b> is independent of any particular measurement. Thus, length is a quantity kind while the height of a rocket is a specific quantity of length; its magnitude that may be expressed in meters, feet, inches, etc. Examples of physical quantities include physical constants, such as the speed of light in a vacuum, Planck's constant, the electric permittivity of free space, and the fine structure constant. </p> <p class="lm-para">In other words, quantities are quantifiable aspects of the world, such as the duration of a movie, the distance between two points, velocity of a car, the pressure of the atmosphere, and a person's weight; and units are used to describe their numerical measure. <p class="lm-para">Many <b>quantity kinds</b> are related to each other by various physical laws, and as a result, the associated units of some quantity kinds can be expressed as products (or ratios) of powers of other quantity kinds (e.g., momentum is mass times velocity and velocity is defined as distance divided by time). In this way, some quantities can be calculated from other measured quantities using their associations to the quantity kinds in these expressions. These quantity kind relationships are also discussed in dimensional analysis. Those that cannot be so expressed can be regarded as "fundamental" in this sense.</p> <p class="lm-para">A quantity is distinguished from a "quantity kind" in that the former carries a value and the latter is a type specifier.</p> Quantity Scale type Lexical pattern for the case-insensitive version of UCUM code case-insensitive UCUM code Lexical pattern for the terminal symbols in the case-insensitive version of UCUM code case-insensitive UCUM term https://ucum.org/ucum.html Lexical pattern for the case-sensitive version of UCUM code case-sensitive UCUM code https://ucum.org/ucum.html Lexical pattern for the terminal symbols in the case-sensitive version of UCUM code case-sensitive UCUM terminal An aspect class that holds properties that provide external knowledge and specifications of a given resource. Verifiable This property relates a unit of measure with a unit system that does not define the unit, but allows its use within the system. An allowed unit must be convertible to some dimensionally eqiuvalent unit that is defined by the system. allowed unit of system This property relates a unit of measure with a unit system that may or may not define the unit, but within which the unit is compatible. applicable system bounded citation A code is a string that uniquely identifies a QUDT concept. The use of this property has been deprecated. code A coherent unit of measurement for a unit system is a defined unit that may be expressed as a product of powers of the system's base units with the proportionality factor of one. A system of units is coherent with respect to a system of quantities and equations if the system of units is chosen in such a way that the equations between numerical values have exactly the same form (including the numerical factors) as the corresponding equations between the quantities. For example, the 'newton' and the 'joule'. These two are, respectively, the force that causes one kilogram to be accelerated at 1 metre per second per second, and the work done by 1 newton acting over 1 metre. Being coherent refers to this consistent use of 1. In the old c.g.s. system , with its base units the centimetre and the gram, the corresponding coherent units were the dyne and the erg, respectively the force that causes 1 gram to be accelerated at 1 centimetre per second per second, and the work done by 1 dyne acting over 1 centimetre. So \(1 newton = 10^5\,dyne\), \(1 joule = 10^7\,erg\), making each of the four compatible in a decimal sense within its respective other system, but not coherent therein. is coherent unit of system derived quantity kind of system element type field code This deprecated property was intended to relate a quantity kind to its generalization. generalization guidance A coherent unit of measurement for a unit system is a defined unit that may be expressed as a product of powers of the system's base units with the proportionality factor of one. has non-coherent unit This property relates a system of units with a unit of measure that is either a) defined by the system, or b) accepted for use by the system and is convertible to a unit of equivalent dimension that is defined by the system. Systems of units may distinguish between base and derived units. Base units are the units which measure the base quantities for the corresponding system of quantities. The base units are used to define units for all other quantities as products of powers of the base units. Such units are called derived units for the system. has unit has vocabulary iec-61360 code is base quantity kind of system `qudt:isQuantityKindOf` was a strict inverse of `qudt:hasQuantityKind` but is now deprecated. is quantity kind of numeric value rationale rdfs datatype This deprecated property originally related a quantity kind to its specialization(s). For example, linear velocity and angular velocity are both specializations of velocity. specialization <em>ucumCode</em> associates a QUDT unit with a UCUM case-insensitive code. ucum case-insensitive code <em>ucumCode</em> associates a QUDT unit with with a UCUM case-sensitive code. ucum case-sensitive code <p><em>ucumCode</em> associates a QUDT unit with its UCUM code (case-sensitive). </p><p>In SHACL the values are derived from specific ucum properties using 'sh:values'.</p> https://ucum.org/ucum.html ucum code The UDUNITS package supports units of physical quantities. Its C library provides for arithmetic manipulation of units and for conversion of numeric values between compatible units. The package contains an extensive unit database, which is in XML format and user-extendable. The package also contains a command-line utility for investigating units and converting values. https://www.unidata.ucar.edu/software/udunits/ udunits code The UN/CEFACT Recommendation 20 provides three character alphabetic and alphanumeric codes for representing units of measurement for length, area, volume/capacity, mass (weight), time, and other quantities used in international trade. The codes are intended for use in manual and/or automated systems for the exchange of information between participants in international trade. https://service.unece.org/trade/uncefact/vocabulary/rec20/ https://unece.org/trade/documents/2021/06/uncefact-rec20-0 unece common code A reference to the unit of measure of a quantity (variable or constant) of interest. unit A property to relate an observable thing with a value of any kind value A datatype that is the union of numeric xsd data types. "numericUnion" is equivalent to the xsd specification that uses an xsd:union of memberTypes="xsd:decimal xsd:double xsd:float xsd:integer". value union dtype:numericUnion A datatype that is the union of numeric xsd data types. "numericUnion" is equivalent to the xsd specification that uses an xsd:union of memberTypes="xsd:decimal xsd:double xsd:float xsd:integer". numeric union The property "vaem:idString" is intended for general use as a means to specifiy a unique reference to something. This is a data property with a string range and is a sub-property of "vame:id" The property "vaem:ownedBy" is a general property that in some cases could have scalar values or may refer to some concept of "Party". For this reason, the type of this property is set as "rdf:Property" and the property is rangeless. There are two sub-properties of "vaem:ownedBy", namely "vaem:owner" for string values and "vaem:owningParty" for referencing a party. Ownership applies to those ontologies that are proprietary The property "vaem:owningParty" is used to refer to some concept of "Party" and is a sub-property of "vaem:ownedBy" rdf:HTML xsd:anySimpleType xsd:string Dave Beckett Nikki Rogers Participants in W3C's Semantic Web Deployment Working Group. Alistair Miles Sean Bechhofer An RDF vocabulary for describing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', other types of controlled vocabulary, and also concept schemes embedded in glossaries and terminologies. SKOS Vocabulary Broader concepts are typically rendered as parents in a concept hierarchy (tree). has broader Relates a concept to a concept that is more general in meaning. By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.