This ontology provides a set of basic metadata annotations for use in describing Object Management Group (OMG) specifications, standards, and documents. It was recommended for use by the OMG Architecture Board (AB) in OMG standard ontologies, vocabularies and other models at the March 2013 Reston meeting. The annotations defined herein extend properties defined in the Dublin Core Metadata Terms Vocabulary and in the W3C Simple Knowledge Organization System (SKOS) Vocabulary, and have been customized to support the OMG specification development process. Note that any of the original properties provided in Dublin Core and SKOS can be used in addition to the terms provided herein. However, any Dublin Core terms that are not explicitly defined as OWL annotation properties below must be so declared in the ontologies that use them.
Revisions are managed per the process outlined in the Policies and Procedures for OMG standards, with the intent to maintain backwards compatibility to the degree possible. The RDF/XML serialized OWL corresponding to the ODM/OWL model has been checked for syntactic errors and logical consistency with Protege 4 (http://protege.stanford.edu/), HermiT 1.3.8 (http://www.hermit-reasoner.com/) and Pellet 2.2 (http://clarkparsia.com/pellet/).
The ontology was revised in August 2014 to: (1) clean up the metadata about this ontology to reflect current usage (2) add support for OMG issue resolution detail to facilitate change management and automated specification generation (3) modify the approach to inclusion of licensing information in model metadata to reference an individual of type dct:LicenseDocument, contained in this metadata ontology, rather than requiring the text to be repeated in any ontology published by the OMG
The ontology was revised in July, 2013, as follows: (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing and specifically for the Financial Industry Business Ontology (FIBO) and other forthcoming OMG ontology specifications (2) to introduce the use of version-independent IRIs for all definitions internally as opposed to version-specific IRIs (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools (4) to extend the file-level metadata to allow for cases such as FIBO, where the specification includes family, specification, spcification version, module, and ontology level detail that should be documented via annotations (e.g., family level of FIBO, specification level of Foundations, module level such as Utilities, and ontology level including annotation vocabulary, business types, and relations) (5) to make other minor corrections in the metadata and definitions for clarification purposes
Copyright (c) 2012-2014 Adaptive Copyright (c) 2012-2014 Object Management Group, Inc. Copyright (c) 2012-2014 Thematix Partners LLC
specification family title (for example, Financial Industry Business Ontology)
specification family abbreviation or acronym
abbreviation or acronym for the specification family
URL where the specification family is published
a short textual description of the family of specifications
the full (complete) formal title of the specification, without abbreviations
official abbreviation or acronym for the specification and related electronic files
short name for the specification or module
a short, commonly used, or preferred name, for a given specification or module
URL for the specification directory on the OMG web site
a link to the latest published formal specification (document)
a short textual description for the specification
copyright statement for the specification version, content, or model/electronic file
a contributor that is an OMG member, identified member of the submission team, and filed the requisite LOI, responsible for the content of the specification or model
task force or working group responsible for the original RFP/RFC and specification adoption
an editor of the specification, which may include the primary contact organization, or RTF/FTF co-chair (organization), depending on where the specification is in the process
an organization or individual that has made a significant contribution to the specification
task force or working group responsible for this revision of the specification
specification or standard (range can be xsd:string, xsd:anyURI, or BibliographicCitation)
a normative reference or standard for the specification
informative reference, standard, or document
reference used as a primary, direct source for content in developing this specification or model (range can be a string, URI, or BibliographicCitation)
a bibliographic reference for and/or URL of any electronic files or documents (e.g., document version URL if applicable) on which this specification or model depends; if the model contains multiple modules, then dependencies should reflect those of the model in question
may appear more than once, as appropriate
technology area relevant to the specification, for example, analysis and design, business process modeling, information exchange and interoperability, middleware, etc.
topic or area of interest that this particular specification relates to, for example, real time, robotics
the version identifier for this version of the specification
a link to the immediately preceding OMG formal specification version
explicit URI where the specification version is published
the date this version of the specification was published
status of this version of the specification from a process perspective, including whether or not it has been formally adopted or superseded by a newer version
a link to the FTF or RTF report, if applicable
a link to a mailing list or web page where questions, discussion, and issues can be raised
module name, if distinct from the specification title
abbreviation or acronym for the module, if distinct from that of the specification
module version, if distinct from the specification version
a short title for the component or module
a short textual description of the module
name of the electronic document or file this metadata is associated with
file version, if distinct from the specification or module version
abbreviation or acronym for the file, such as a namespace prefix, if distinct from that of the specification
a short textual description of the model or file
a link to the immediately preceding version at the file level
OMG document number (for the document or file this metadata is associated with); note that a single OMG document number may be associated with many files, for example in the case of an archive containing all of the ontologies associated with a given FIBO specification
document URL (for the specific document or model file this metadata is associated with)
boolean value indicating whether or not the file is a normative component of a specification
indicates the content type, for example, MOF metamodel, UML profile, UML model, SBVR or RDF vocabulary, OWL or CL ontology
a link to the core language and/or specification of the model/electronic file, for example, UML, OWL, SysML, BPMN, including linking to the version of the language in question
serialization format for the file in terms of its MIME Type, such as xmi, rdf/xml, owl/xml, etc.
Author identifies an individual or organization that originated the model or specification (range can be a dct:Agent or string).
relates a 'master' or umbrella specification to specific versions of that specification, created through a finalization or revision process
relates a given version of a specification to the 'master' or original specification that it modifies
a reference to an authoritative source for provenance or substatiation purposes; The form of bibliographic citation may be specific to a domain, publication, or community, thus specific properties to define the details are not provided. FRBR, ISO 690, and others provide reasonable approaches if none is explicitly required for a specification.
An Issue is a report made to OMG of an error in an OMG Specification. An F/RTF Report lists the issues and comments received by the F/RTF against a specification, and the resolution, if any, for each comment (referred to by its Issue Number). For resolutions that involve changes to the models (machine readable artifacts) corresponding to the specification, an individual of type IssueResolution should be included in the administrative metadata for the version of the specification to which it applies, for each issue resolved, linking to the appropriate issue page in the OMG JIRA system where further information about the issue and how it was dealt with can be found.
MIME media type as defined by the IANA standard
Modularization of any engineering model involves principles of the model driven architecture methodology (MDA), including but not limited to separation of concerns, coherence, and establishing clear logical boundaries in order to increase reusability and maintainability. A module should be designed to reflect these principles, including a small number of models that have well-defined relationships with one another, that form a coherent and cohesive whole for some purpose, and that have clear boundaries or interfaces to other external modules.
an entity, such as an institution or an association, that has a collective goal and is linked to an external environment
an explicit set of requirements to be satisfied by a material, product, or service
a family of specifications, such as the OMG's Financial Industry Business Ontology (FIBO) or the Information Exchange Framework (IEF)
a formal revision of a given specification, produced through the efforts of a finalization or revision task force
the content type for the model or module, for example, MOF metamodel, UML profile, UML model, vocabulary, ontology, ruleset, etc. The actual content language for the module (for example, RDF Schema, OWL, or SBVR in the case of a vocabulary) should be specified using the contentLanguage annotation property. Valid values are specified as individuals.
The MIT License: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
license document representing the actual text of the MIT License