Annotation Properties are used to hold the metadata required to manage Reference Data (RD) Classes, etc. (e.g. version identifiers). The Annotation Properties used in PLCS are based on the Dublin Core set of properties.

Use of Annotation Properties

The Dublin Core is an industry standard for data about Web resources managed by the Dublin Core Metadata Initiative (DCMI). Quoting from their Web site:

“The Dublin Core Metadata Initiative is an open forum engaged in the development of interoperable online metadata standards that support a broad range of purposes and business models. DCMI's activities include consensus-driven working groups, global workshops, conferences, standards liaison, and educational efforts to promote widespread acceptance of metadata standards and practices.”

Not all of the Dublin Core Elements and Terms are required for annotating PLCS Reference Data Classes. In OWL, these elements and terms are provided as OWL Annotation Properties. An annotation property does not affect the semantics of the Ontology, Class or Property. In the PLCS Reference Data Library (RDL) / Ontology, Annotation Properties are used as part of the process of managing the library itself.

In addition to the Dublin Core, the OWL language has built-in Annotation Properties that Reference Data developers can use.

For the purpose of managing the OASIS PLCS TC RD development process, a small number of TC-specific OWL Annotation Properties have also been defined.

The following matrix shows what OWL Annotation Properties and Dublin Core Elements and Terms to apply. The properties are hyperlinked to the Web and their formal definitions.

NOTE    The "dc" prefix denotes a Dublic Core Annotation Property.

Table 1 — Use of Annotation

rdfs:comment is The text definition of the RD Class

An rdfs:comment is a human readable text definition for an RD Class where more than one are allowed to support definitions in different natural languages.

rdfs:label is The name of the RD Class

An rdfs:label is a human readable name for an RD Class where more than one are allowed to support labels in different natural languages (e.g. 'Chat' in French and 'Cat' in English)

dc:OASIS_stage is The stage in the life cycle of the RDL / Ontology

The OASIS_stage is set to reflect the stage at which the RDL / Ontology has progressed within development and review process. Valid values are "Developer Draft", "Committee-Draft", "Public Review Draft" and "Committee Specification". An OASIS_stage occurs within an OWL versionInfo to manage the process of publishing RDLs (i.e. each version of an RD Class goes through these stages).

dc:OASIS_revision is The revision within a stage in the life cycle of the RDL / Ontology

The OASIS_revision is set to reflect changes that have occurred within the stage of the process and has valid values 0, 1, 2, 3, etc. For example, when a Class reaches "Committee Draft" stage the revision is set to '0' but if comments are raised and addressed then the revision is raised to '1' to reflect the fact that it has been changed since entering the "Committee Draft" stage. However, when the item moves to the next OASIS_stage the OASIS_revision is reset to '0'.

owl:versionInfo is The version of the RDL / Ontology

The OWL versionInfo is set to reflect the version of the RD Class. It starts with '1' and then increments to '2', etc. The versionInfo is set as soon as the RD Class enters the "Developer Draft" stage. The versionInfo for an RD Class within an Ontology is independent of the Ontology and only gets updated if changes occur to the definition of the RD Class. So, PLCS RDL versionInfo '2' Ontology may contain RD Classes at versionInfo '1'. In fact all the Classes might be at versionInfo '1' if none were changed between Ontology '1' and '2'. This would happen if Ontology '2' only contained new additional RD Classes.

dc:creator is The PLCS Modeller who created the RD Class

The Dublin Core term "creator" is the annotation to be used to define the person and organization who added the class to the RD Library. The form of the dc:creator value should be first name, last name, comma, and then organization name (e.g Rob Bodington, Eurostep).

dcterms:created is is the date creator added RD Class

The Dublin Core term "created" is the annotation to be used to define the date that the creator added the RD Class to his/her work space (e.g. YYYY-MM-DD).

dcterms:modified is date of most recent change to RD Class

The Dublin Core term "modified" is the annotation to be used to define the date of the most recent change to the Reference Data Class (e.g. YYYY-MM-DD).

dc:source is The original source of the RD Class

The Dublin Core term "source" is the annotation to be used to define any standard or organization that originally created the Class and is responsible for publishing it and controlling its development. A unique name for any dc:source must be agreed by the RDL / Ontology developers.

If the RD Class is entirely new, created by the PLCS modeller, then the dc:source should be set to read "PLCS RDL n" where "n" is the version of the PLCS Reference Data Library / Ontology in which the RD Class first appeared (e.g. PLCS RDL 1).

At the time of publication of each version of the PLCS RDL, any RD Class that does not have a dc:source set will have that value set with the applicable "PLCS RDL n" by default.

dcterms:dateAccepted is date Registered with PLCS

The Dublin Core term "dateAccepted" is the annotation to be used to define the date that the RD Class reached the Registered status in the PLCS RDL development process. The user is expected to set this date. (e.g. YYYY-MM-DD)

dc:issued is date of OASIS Publication of the specified version of the RD Class

The Dublin Core term "issued" is the annotation to be used to define the date that the Reference Data Class version was published as part of an official OASIS PLCS RDL version. This date is not changed if the item did not change between PLCS RDL version n.nn and n.nn+1.

This will be automatically set when a version of the PLCS RDL is published.

dc:language is the natural language

The Dublin Core term "language" is the annotation to be used to define the natural language in which a label, definition or comment is made (e.g. "en" for English).

The two letter codes specified in ISO 629-2 shall be used (http://www.loc.gov/standards/iso639-2/langcodes.html)

dc:publisher is OASIS PLCS TC

The Dublin Core term "publisher" is the annotation to be used to define that OASIS PLCS TC published the RDL / Ontology. This will be set automatically upon official OASIS publication of a version of the RDL.

dcterms:references is a reference to another standard or document

The Dublin Core term "references" is the annotation to be used to define any reference to another standard or document that appears as part of the definition of the RD item. (e.g. "ISO 10303-41").

dcterms:rightsHolder is IPR holder

The Dublin Core term "rightsHolder" is the annotation to be used to define who owns the Intellectual Property Rights, etc. related to an RD Class. It is used in conjunction with "rights".

dcelements:rights is IPR

The Dublin Core term "rights" is the annotation to be used to define the Intellectual Property Rights, etc. related to the RD Class. It is used in conjunction with "rightsHolder".

dc:subject is used for keywords and classification of RD Classes

The Dublin Core term "subject" is the annotation to be used to define the keywords or classifications codes (e.g. class of class) related to an RD Class. Each keyword or classification code should be created in separate instances of "subject". (e.g. "Aircraft maintenance")

dc:title is the title of an OWL Ontology / RDL

The Dublin Core term "title" is the annotation to be used to provide the title for part of an OWL Ontology / RDL that is contained in particualr OWL file.

References

Dublin Core Metadata Initiative(http://dublincore.org/)

DCMI Metadata Terms(http://dublincore.org/documents/dcmi-terms/)