DRK KG: How to create meaningful identifiers for Theaters, Events, Plays, etc.

[rohitadeshmukh13]

Description

• While instantiating the culture domain specific entities such as Theaters, Events, Plays, we would need to assign them with identifiers.
• Example:

  # Theater instance
  @prefix drkr: <https://w3id.org/drk/resources/>
  ...
  drkr:DE_Staatstheater_Augsburg
  a drko:PerformingArtsTheater ;
  schema:name "Staatstheater Augsburg" ;
  ...

• In this example, drkr:DE_Staatstheater_Augsburg, i.e., https://w3id.org/drk/resources/DE_Staatstheater_Augsburg is used an an identifier. It would be desirable to replace DE_Staatstheater_Augsburg in this identifier with something more meaningful.
• It would be desirable to use meaningful identifiers that are machine-readable as well as human-readable and understandable.

Example

• Custom scheme for naming sensor observations in Smart Building domain: Namespace + country_code : site : apartment no. : deviceID : measured property
• Example: https://bimerr.example.com/resource/pl:budimex:7:12:temperature

Action items

• Are there any existing Standards / Naming Conventions? If not, should we design a new naming scheme?

Issue resolution

• This issue can potentially be resolved by adding the resulting naming scheme to the README and conveying it to the DRK Infrastructure team.

[rohitadeshmukh13]

GND Knowledge Graph It seems that the GND Knowledge Graph uses simple numerical identifiers for entities and instances. Examples: Identifier for Theater concept: https://d-nb.info/gnd/4059702-7 Identifier for Theater instance (Staatstheater Augsburg): https://d-nb.info/gnd/1170044093

NFDI4Culture Knowledge Graph It seems that the NFDI4Culture Knowledge Graph uses simple alphanumeric identifiers (The letter "E" followed by some numbers) for instances. Examples: Persistent Identifier for a Book: https://nfdi4culture.de/id/E4464 Persistent Identifier for an Organization: https://nfdi4culture.de/id/E1849