Do RDF URIs have a trailing slash or not?
Bug #671924 reported by
Erik Hetzner
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Open Library |
In Progress
|
Undecided
|
Unassigned |
Bug Description
Sometimes a slash trails a URI, sometimes it doesn't. Here is an example:
In the RDF at:
http://
the URI used is:
http://
It links to manifestations, which have URIs like:
http://
But when I retrieve:
http://
the URI used there is:
http://
This makes it difficult to do automated parsing based on the URIs.
Thank you for working of this project.
If I may vote, I'd vote to not use trailing slashes. IMHO a trailing slash looks strange, because if the URI as an identifier of a Work or Edition is the same as the URI for the HTML representation of its description, how can one assert things about either things?
How about: URI of a Work, Edition or Author has no trailing slash, URIs of their (default) HTML descriptions do have a trailing slash and descriptions in other formats have a file type extension at the end like they do now (.rdf, .json)?