Closed edwardanderson closed 3 years ago
Ah, maybe I simply apply an extra P2_has_type
to the Identifier and mint a thesaurus term for "Object Number". Simple as that?
A Type with names seems easy, and makes it easier to be consistent by reusing that Type with all your identifiers :)
Okay to close?
Thank you for the recommendations on implementing identifiers in yesterday's call (#421). I've been working on improving our own templates for identifiers and realised I am uncertain how (and where) to describe certain properties of an identifier's name.
For example, we would like to record that the identifier "SK-C-5" is the
"Object Number"@en
and"Objectnummer"@nl
of a painting. Are these names direct properties of the instance of the identifier, or does the identifier conform to some other CRM entity (representing the underlying field in the source system) with its own names and properties?With this pattern (above), it's necessary to make blank
Name
nodes for every occurrence of our "Object Number" identifier (a lot). Also, theseName
nodes aren't really specific to the particular instance of identifier. So instead, is there a pattern where the identifier nodeconforms_to
(or other) a class of identifier which is named only once (and could be further annotated)?