Prefixing the identifier with `url:` is not recommended

[brendanny]

tl;dr I don't think having url: breaks anything, but it's unnecessary and redundant.

• se create-draft for SE books uses a <dc:identifier> of the format url:https://standardebooks.org/ebooks/<ebook>

• epub34 references dcterms for the dc metadata

• dcterms' comments on identifier are: [emphasis mine]

  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.

• The definition of URI used by dcterms is:

  The set of identifiers constructed according to the generic syntax for Uniform Resource Identifiers as specified by the Internet Engineering Task Force. ... See http://www.ietf.org/rfc/rfc3986.txt

• According to RFC 3986, Appendix C:

  The prefix "URL:" (with or without a trailing space) was formerly recommended as a way to help distinguish a URI from other bracketed designators, though it is not commonly used in practice and is no longer recommended.

  • The examples in 1.1.2 Examples do not prefix http or any transport.

[brendanny]

This also affects SEMoS 9.2.1

[brendanny]

Also, in epub34, a note in the dc-identifier section encourages to "use absolute-URL strings for identifiers whenever possible"

[acabal]

Good idea but this will be a lot of work. Not only does the corpus and toolset need to be updated, but the website code as well. Everything will have to be released all at once. Someone is going to have to volunteer to do that.

[brendanny]

I can put together PRs for tools, web, and manual. The corpus would need to be scripted by someone with commit access.

[acabal]

That's fine, I can script the corpus.

[brendanny]

Is there anything else I can help with to push this through? or just waiting for the time to coordinate it all?

[acabal]

I need to find time to do this. It will take a while.