Switch DPV namespace IRI to use slash instead of hash?

Hi,

I'd like to propose that the DPV group consider switching the DPV namespace
IRI to use a trailing slash instead of a hash, i.e., using
https://w3id.org/dpv/ instead of the current ttps://w3id.org/dpv#

I'm guessing that DPV probably just chose to use a hash because it tends to
be more common (and has been typical for W3C vocabs), but there are pro's
and con's to either choice (as explained briefly in "2.2 Hash versus slash
URIs" of this paper <https://arxiv.org/pdf/2003.13084.pdf>, but the paper
doesn't recommend one over the other).

Personally I consider that using slashes is 'more correct', since it's the
only option that allows both 'getting all vocab metadata in a single
request' (i.e., just dereference the namespace IRI itself), and 'getting
just the metadata for an individual vocab term'.

It certainly seems much more correct to me that clicking on
https://qudt.org/schema/qudt/CurrencyUnit in my browser returns only
information on QUDT's definition of a 'CurrentUnit' (try it yourself!), or
simply executing "curl https://qudt.org/schema/qudt/CurrencyUnit -H
"Accept: text/turtle"" gives me back *only* the relevant triples in Turtle
(Turtle is actually the default, so the `Accept:` header isn't even
necessary).

The same is demonstrated nicely with any term from Schema.org. If they'd
made the mistake of using hashes, then simply looking up what a '
https://schema.org#Person' was would return information for all 2,300+
terms in Schema.org, which is simply not what was requested or intended at
all.

Yes, it can be a bit more work for the server hosting vocabs to support
both options, but adopting slashes now at least makes providing that
flexibility possible later, whereas continuing to use a hash makes it
impossible forever!

Major vocabs like Schema.org, Gist, QUDT, FOAF, BIBO, ODRL, SAREF, SOSA,
SSN, etc. all use slashes, so it's certainly not uncommon, and in fact I
understand that the Gist community
<https://www.semanticarts.com/gist/> (recommended
by Oracle
<https://www.ateam-oracle.com/post/knowledge-graph-modeling-governance-project-scope>)
discussed this very question back in 2019, and after careful consideration
and discussion, it was decided to flip from using hash to use slash
instead. (*Note*: I did reach out to the gist community to ask if they have
a public record of the discussions they had that led to them switching from
hash to slash (see here <https://github.com/semanticarts/gist/issues/725>),
but unfortunately they don't seem to have a record at all!).

So I think DPV should very seriously consider adopting the slash instead of
hash too.

Cheers,

Pat.

*Pat McBennett*, Technical Architect

Contact  | patm@inrupt.com

Connect | WebID <http://pmcb55.inrupt.net/profile/card#me>, GitHub
<https://github.com/pmcb55>

Explore  | www.inrupt.com

-- 
This e-mail, and any attachments thereto, is intended only for use by the 
addressee(s) named herein and may contain legally privileged, confidential 
and/or proprietary information. If you are not the intended recipient of 
this e-mail (or the person responsible for delivering this document to the 
intended recipient), please do not disseminate, distribute, print or copy 
this e-mail, or any attachment thereto. If you have received this e-mail in 
error, please respond to the individual sending the message, and 
permanently delete the email.