Open DavidFichtmueller opened 2 months ago
OK yes that could be useful, adding this property. When ingesting and mapping data from standards which don't include this property, is it a correct assumption that any identifier that starts with http
we could mark as resolvable?
We have now combined the need to describe "resolvable" and "persistent" in a new term ods:GupriLevel
that can describe different "GUPRI" levels of an identifier with a controlled vocabulary. Examples: "LocallyUniqueStable", "GloballyUniqueStablePersistentResolvable"
in a new term
ods:GupriLevel
that can describe
Sorry, this might be a bit late, but I just noticed that this element should be called ods:GUPRILevel , to be consistent with the capitalization convention, see also #178 .
Term Name
ods:isIDResolvable
Digital Object Name
DigitalSpecimen: Identifier
Feedback
Suggestion to create a new term about whether an ID actually resolves to any kind of meaningful resource about the item it is identifying. This would be a boolean flag and is useful in conjunction with dcterms:format.