With the need to capture, resolve, and reuse external identifiers in whatever context and for whatever data object, I suggest the following component with properties (borrowed from wikidata) that could be used much like managed attributes are used today. In theory, this would accommodate identifier schemes like ark, doi, handle, orcid, uri, urn, etc. The advantage here is a clean(er) separation of resolution & protocol (i.e. https, http, etc.) from the alpha-numeric portion of the identifier, though semantic web enthusiasts may disagree.
...whose view would then reconstruct a more human-friendly version, dependent on what elements are present in the lookup to the identifier registry, such as:
With the need to capture, resolve, and reuse external identifiers in whatever context and for whatever data object, I suggest the following component with properties (borrowed from wikidata) that could be used much like managed attributes are used today. In theory, this would accommodate identifier schemes like
ark,doi,handle,orcid,uri,urn, etc. The advantage here is a clean(er) separation of resolution & protocol (i.e. https, http, etc.) from the alpha-numeric portion of the identifier, though semantic web enthusiasts may disagree.ExternalIdentifierRegistry
And then, instances stored in each component (eg Agent), we have:
“namespace:identifier” (eg orcid:0000-0001-9508-1349)
...whose view would then reconstruct a more human-friendly version, dependent on what elements are present in the lookup to the identifier registry, such as: