Bibliographic span specification conflates URIs (identifiers) and URLs (locators)

[ronaldtse]

• URIs are identifiers and not necessarily resolvable (and we should not assume whether they are or not, it is the job of the editor).
• URLs are location links and are resolvable.

The current implementation of bibliographic spans in fact conflates between identifiers and locators. ISO 690 differentiates them because it is necessary to in the rendering

• DOIs are identifiers, rendered typically as doi: xxx/yyy. There are also ORCIDs and others.
• For accessible URLs, they are rendered typically as Available at: https://xxx.

In order to encode location, we do:

* [[[mozilla,Mozilla Web XR]]],
span:organization[Mozilla],
span:title[Fundamentals of Web XR]
span:url[https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API/Fundamentals]

Not span:uri.

The following encoding:

* [[[edge_mesh,Edge Mesh]]],
...
doi: span:uri.doi[10.1109/ACCESS.2017.2739804].

Should list DOI as an identifier instead of a URI (something like this):

doi: span:identifier.doi[10.1109/ACCESS.2017.2739804].

In any case we're looking to differentiate the Identifier and the Locator. I believe there are many such instances that we may need to flesh out, and this ticket shouldn't be actioned until we can specify them.

Relevant document at: https://github.com/metanorma/SWF-Corpus_and_IEEEP2874-D2

[opoudjis]

Hasn't been actioned for two years. The vaguery of

I believe there are many such instances that we may need to flesh out, and this ticket shouldn't be actioned until we can specify them.

means it will never be actioned. The distinction is W3C pedantry, and changing span:uri to span:url after two years, and breaking all existing markup that has used span:uri from hyperlinking, is something I won't allow.

There is no action on me (apart from breaking span:uri, which I am not prepared to do), so I am unassigning myself until there is.