W3C home > Mailing lists > Public > public-perma-id@w3.org > September 2019

Re: question regarding w3id based purls

From: Daniel Garijo <dgarijo@fi.upm.es>
Date: Sat, 14 Sep 2019 10:11:37 -0700
Message-ID: <CAExK0De9tv5DT0bMtzQAWujBwVo5LxJr8=2YxY6EYofNxQ6hEQ@mail.gmail.com>
To: Nicholas Car <nicholas.car@surroundaustralia.com>
Cc: "Genuchten, Joep van" <joep.van.genuchten@alliander.com>, "public-perma-id@w3.org" <public-perma-id@w3.org>
Hi Joep,
why not having a single namespace with content negotiation for
documentation and definition?
Your w3id would be https://w3id.org/netbeheer/YourOntologyID
If you open it in your browser it would automatically redirect you to your
documentation URL. If you open it in Protege, it would redirect to the
TTL/RDF+XML file or other RDF serialization you choose to.

This is the way some W3C specs are built, see for example PROV:
https://www.w3.org/ns/prov
And we have many ontologies published in w3id following this pattern. See
for example
https://w3id.org/okn/o/sd (corresponding htaccess available here:
https://github.com/perma-id/w3id.org/blob/master/okn/o/sd/.htaccess).
Best,
Daniel


El vie., 13 sept. 2019 a las 23:21, Nicholas Car (<
nicholas.car@surroundaustralia.com>) escribió:

> Hi Joep,
>
> That seems like a sensible policy! To implement that, you would only need
> a single entry in w3id for netbeheer/ and then you could build a directory
> structure for def/, doc/ etc. with individual .htaccess files within them.
> Or a single large .htaccess file at the top level netbeheer/ which would be
> more complex but perhaps easier to maintain with all the entries in one
> place.
>
> By the way, the policy you’re working with seems similar to the Australian
> government URI policy which is described at
> http://www.linked.data.gov.au/governance. I’d be interested to see any
> Dutch policy documents for the national government uri strategy if you
> can find them please. I would like to compare them to ours.
>
> Thanks,
>
> Nick
> (Co-chair of the Australian Government Linked Data Working Group)
>
>
>
> —
> Nicholas Car
> Data Systems Architect
> SURROUND Australia
> 0477 560 177
> nicholas.car@surroundaustralia.com
>
> On 14 Sep 2019, at 12:15 am, Genuchten, Joep van <
> joep.van.genuchten@alliander.com> wrote:
>
> Hello,
>
>
>
> I have a question about how to best proceed in requesting purls on the
> w3id domain.
>
>
>
> We (a consortium of Dutch electricity and gas grid operators of which my
> organization, Alliander is one) would like to publish our ontologies on
> w3id conform the Dutch national government uri strategy.
>
>
>
> In a nutshell this would come down to a pattern like this:
>
> ·       W3id.org/netbeheer (netbeheer means ‘grid operation’) as a base
> domain
>
> ·       W3id.org/netbeheer/def/  would be the base domain for ontology
> files (in ttl/rdf xml etc), similar to the NS namespaces of the w3c
>
> ·       W3id.org/netbeheer/doc/  would be where documentation for the
> ontologies is published, similar to the TR namespaces of the w3c
>
> ·       W3id.org/netbeheer/def/KernObjecten#  would refer to a specific
> ontology file
> https://raw.githubusercontent.com/JoepvanGenuchten/ESM/master/KernObjecten.owl
>
>
>
> The last bullet is currently the only redirect for which I currently have
> an address. Is it possible to built this structure in this way even if not
> all higher levels have a redirect?
>
>
>
> Thank you for your help,
>
>
>
> Joep van Genuchten
>
> Data Architect, Alliander
>
>
>
>
Received on Saturday, 14 September 2019 17:12:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:43 UTC