I've started this thread, a sub-thread of the identifier discussion, to focus on the suggestion that BIBFRAME identifiers (non-http identifiers) be expressed as URIs (non-http URIs)
Yes, non-http URIs can often be turned into http URIs. I am excluding http in this discussion.)
Actually one person offered the stronger suggestion that the identifiers all be expressed as URNs.
No URN form but can be expressed by another scheme.
An example is LCCN. It cannot be represented as a URN, but can be represented as an ‘info:’ URI. I am assuming that the answer here is to represent it as an ‘info:’ URI, I just want to confirm that everyone agrees. This would apply as well to ark, pmid and others.
more than one (non http) URI form.
While there are no subspaces common to:
There is quite a body of literature that claims that this or that identifier, in the ‘info’ table, but not in the ‘urn’ table, is expressible as a URN. These include sici, doi, and hdl, and perhaps others. I am assuming that the rule here would be to express these as ‘info:’ URIs, and never as URNs.
No URI form
I am hoping that there is unanimous consensus that an identifier whose scheme is not listed in the URN registry should never be expressed as a URN.
But there are quite a number of these, including Ismn, isrc, istc, iswc, legalDeposit, musicPublisherNumber, publisherNumber, stockNumber, strn, systemNumber, and several more. Getting these registered as URN subspaces is not a practical idea. (And those of you who have registered URN spaces know what a painful process it is.) I have a radical suggestion: re-open the info: registry (Jeff?) and register the single space ‘bibframe:’ and structure it’s definition as we want it. For example: “info:bibframe\publisherNumber\ 256A090”.