- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Sep 2018 08:49:19 +0000
- To: public-dxwg-wg@w3.org
> I believe that the current policy is to use /ns/ URIs for rec-track vocabularies, and dated NSs for more informal products, from community groups, etc (@philarcher @draggett ?) Yes, `/ns/` is now preferred, and I don't think that there is a strict rule regarding community groups in practice. > In the SSN group we also have some derivative NSs such as http://www.w3.org/ns/ssn/systems/, http://www.w3.org/ns/sosa/sampling/, http://www.w3.org/ns/sosa/om#, http://www.w3.org/ns/sosa/prov/ though I'm not sure if any of those is directly dereferenceable (@tidoust ?) Yes, they are all directly dereferenceable. > How does the W3C allocate more than one namespace to an ont if it needs another for constraint definitions? As mentioned by @kcoyle, there is no strong process involved in the creation of namespace URIs that follow one of the allowed forms. The Webmaster will simply allocate the root namespace URIs. What happens within that namespace is up to the group that uses the namespace. For instance, once the group has allocated `http://www.w3.org/ns/foo`, it can create sub-namespaces such as `http://www.w3.org/ns/foo/bar`. A bit of love is required to make these sub-namespaces dereferenceable, but that's just a matter of putting the right files and redirection rules on W3C servers. -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/dxwg/issues/399#issuecomment-425367972 using your GitHub account
Received on Friday, 28 September 2018 08:49:21 UTC