The PINK Annotation Schema strives to follow the guiding principles described in this section.
The PINK Annotation Schema never changes the semantics of existing terms defined externally (e.g. by W3C or DCAT-AP). However, the PINK Annotation Schema can:
pink:usageNote to an existing term (but should not add a vann:usageNote).ddoc:conformance relation that specifies whether the relation is “mandatory”, “recommended” or “optional” in PINK.
PINK will never change the conformance described in the DCAT-AP documentation to something weaker.The basic rule for such additions is that they can live hand-in-hand with similar annotations by other projects without creating confusion or inconsistencies.
For any other additional specifications of an existing term, a PINK-specific subclass or subproperty will be created.
Such subclasses/subproperties will normally keep the W3C name, but with the pink namespace (or the ddoc namespace if the concept is specific for the tripper data documentation).
The PINK Annotation Schema is by itself not a top-level ontology, but is strives to be easy to align with different top-level ontologies, like [EMMO] and [BFO]. However, the goal is only to be able to align with one top-level ontology at the time. Furthermore is the goal not to be able to create a fully consistent ontological framework when aligning to a top-level ontology, but to be able to create interoperability and connect to domain ontologies based on different top-level ontologies.
Since the PINK Annotation Schema is intended to be used within applied sciences and to connect SSbD to materials, it reuses useful parts from the conceptualisation of EMMO, which is an ontology exactly designed for materials and applied sciences. However, the reused parts conceptualisation is simplified as much as possible and limited to the needs of the PINK Annotation Schema. Examples of such reused conceptualisations include: