- From: Simon Cox via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 Feb 2021 06:22:35 +0000
- To: public-sdwig@w3.org
When ssn-ext was published as a W3C Draft we decided to put the new terms in the existing SOSA namespace - see explanation here: https://www.w3.org/TR/vocab-ssn-ext/#namespaces This is because the intention is for these terms to get rolled into the main vocabulary, in due course, so better for them to be used with their intended URIs than change them later or have a vocabulary composed of multiple namespaces, though I acknowledge that SSN already does this. I also acknowledge that almost any choice will be confusing to someone (and there is misleading statement in Paragraph 3 of the Status section, which betrays the fact that there have been various opinions about this and confusion remains!). Namespaces are a tricky thing. I used to mint new namespaces frequently, but my feeling now is that the W3C vocabularies have been a bit too precious about namespaces, and the result is a confusing proliferation which has not gone down well in the marketplace. Compare with Schema.org which is a single namespace, and OBO in which the main ontologies are in a single namespace (though OBO fakes it with a prefix on the local name). This is not a deal-breaker for me, however, as I think there is a downside on every choice. -- GitHub Notification of comment by dr-shorthair Please view or discuss this issue at https://github.com/w3c/sdw/issues/1245#issuecomment-770603256 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 1 February 2021 06:22:36 UTC