An annotation property that can be freely used on any kind of resource. The range of the property is "xsd:string"
A "vaem:LinkSetGraph" is a graph that holds statements that specify links between resources
As it name implies, a way to attach an annotation about a "todo" task
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
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 "_".
has license type
The property "vaem:hasLicenseType" points to an entry in the VOAG ontology for licenses
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.
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".
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.
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
The property "vaem:latestPublishedVersion"is a URL to documentation for the latest version of a graph.
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"
A boolean flag to state that a value is invalid with respect to its type.
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.
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
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
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
Aproperty for constructing composite data structures
The property "vaem:logo" is a reference to an image that is used for publishing the ontology"
The property "vaem:revision" is a property intended for general use as the name implies.
The property "vaem:hasDimension" is used categorize an ontology. In VAEM, the property is used to characterize an ontology graph.
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
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
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.
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.
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.
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.
A property for specifying a derivation relationship.
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.
A property for expressing an encoded value. The range has been set to "xsd:anySimpleType" to allow for a variety of scalar datatypes.
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.
VAEM is issued under a Creative Commons Attribution Share Alike 3.0 United States License. Attribution should be made to TopQuadrant, Inc.
Vocabulary for Attaching Essential Metadata (VAEM) - Version 2.0
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.
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.
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:abbreviation" provides a common way to define a commonly used abbreviation on a resource
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
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
A description of a justification for some other assertion or value
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"
A derived codelist is a sublist of another codelist. The members that it has must be members of the source list.
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
The property "vaem:owningParty" is used to refer to some concept of "Party" and is a sub-property of "vaem:ownedBy"
A "Party" is a generalization for an actor that may be realized as a person, organizaiton or named role.
The property "vaem:rdfxmlFileURL" is used to provide a link to the location of the ontology's RDF/XML file
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
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".
An RDF/OWL Graph that is a controlled set of instances.
A general purpose property for holding string literals.
An indirection pointer for relating a slot in am occurrence data structure, such as "dtype:ValueReference" with another resource.
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
A simple codelist is one made up only of enumerated values.
The property "vaem:usesNonImportedResource" is used to express dependencies on resources from graphs that are not imported
A composite codelist is a codelist made up of other codelists. It does not introduce any new codes.
The property "vaem:intent" is used to outline a statement of purpose. This typically expresses one or more desired outcomes
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
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
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"
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.
"vaem:GraphMetaData" defines basic metadata for the registration and publishing of a graph. For specificaiton of governance the vocabulary "VOAG" may be used.
A value reference is a pointer to an Enumerated Value. The original position of the value can be overridden by the position attribute.
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.
The property "hasMetadata" is used to reference a metadata information structure.
The property "vaem:turtleFileURL" is used to provide a link to the location of the ontology's turtle file
The property "vaem:url" is intended for general use as the name implies. The range of the property is set as an XSD URI
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
The property "vaem:previousPublishedVersion"is a URL to documentation for the previous version of a graph.
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
A property for specifying how member elements make up a data structure.
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
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.
A "vaem:CollectionGraph" is a graph that aggregates other graphs using "owl:imports" statements
An annotation used to reference a graph that elaborates (adds properties and axioms to) a resource
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
The property "vaem:acronym" provides a common way to define a commonly used abbreviation on a resource
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
A "vaem:ConstraintsGraph" is a graph that holds SPIN constraints