search

API4KBs / api4kbs

API for Knowledge Based Platforms - Core Specifications
MIT License
8 stars 4 forks source link

Fix namespace prefixes #36

Closed RalphBln closed 8 years ago

RalphBln commented 8 years ago

From Elisa's mail:

I would recommend the following, with the knowledge that these prefixes tend to stick and be long lived:

Terminology -- api4kp-term Classifiers -- api4kp-cls Events -- api4kp-evt Operations -- api4kp-op OperationClassifiers -- api4kp-opcls Proficiencies -- api4kp-prf Tries -- api4kp-tr

The standard prefix for the OMG's specification metadata ontology is "sm". The standard prefix for the DOL ontology is "dol". The standard prefix for the SKOS ontology is "skos".

Where there is only one ontology associated with a specification, we use the specification abbreviation per the OMG for the prefix, but in lower case. Where there are multiple ontologies, such as in this case and as in FIBO, we use a formula such as

-- So, here we have "api4kp" as the lower case version of the specification abbreviation, and then an abbreviation for each of the ontologies within the spec, hyphen-separated.
RalphBln commented 8 years ago

Closed with ef4549182e01b00d962bfd19a2e99ced25473d2f. (Harmonized namespace endings while I was at it. Now every ontology IRI has a trailing slash).