Re: Identifiers with context

Am 23.02.23 um 15:04 schrieb Mikael Pesonen:
> Hi, we are mapping non RDF data to RDF. There are entities that have 
> identifying codes, for example 1.1, 1.2, 2.1  and external organization 
> (lets name it "org1") is maintaining the codes.
> 
> Using predicate dcterms:identifier the most straightforward way would be 
> to use literals:
> 
> :entity1 dcterms:identifier "1.1" .

"Comment: Recommended practice is to identify the resource by means of a string conforming to an identification system. Examples include International Standard Book Number (ISBN), Digital Object Identifier (DOI), and Uniform Resource Name (URN). Persistent identifiers should be provided as HTTP URIs." [1]

> However we would like to add context to the identifier, that is where 
> identifer codes come from. There are two ways that come into mind:
> 
> 1) Custom namespace in URI
> 
> :entity1 dcterms:identifier <https://www.our-company.com/ns/org1/1.1>
> 
> 2) Dedicated resource:
> 
> :entity1 dcterms:identifier [ rdfs:value "1.1"; dc:source "org1" ]

> 
> Which one would you prefer? Or is there a third, better way?

go with 1) - it's simple, elegant and conforms to what dcterms:identifier[1] describes. 

> I don't want to use the code directly to name the resource:
> <https://www.our-company.com/ns/org1/1.1> rdfs:label "Some entity"


[1]https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/identifier

-- 
Pascal Christoph, M.A.
Hochschulbibliothekszentrum NRW (hbz)
Offene Infrastruktur | https://lobid.org/team/pc