Re: Ontologies ready to be published on the W3C server

Thanks Phil,

No worries, I don't think there isn't anything else urgent about the
publication of the ontology documents,  I wouldn't want you to double your
work on this, considering also the fact that we might need to update
slightly the documents in response to public comments.


I'll come back to you about the other URLs in that namespace:

GET https://www.w3.org/ns/sosa/Observation should 303 redirect to
https://www.w3.org/ns/sosa/ (currently it serves sosa with 200 OK)
GET https://www.w3.org/ns/ssn/Observation and
https://www.w3.org/ns/ssn/qsbrqzerg  should reply 404 (currently they both
serve SSN with 200 OK)


I'll also come back to you about the Content-Disposition headers, which to
me could be very useful for user experience (and not only for the SSN
ontologies):

Ex:
 - when I ask my browser to save the ssn ontology in Turtle, it chooses to
download it with name "téléchargement" (might be "download" for you if you
use chrome) --> it would be better user experience to have it named
"ssn.ttl"  (Content-Disposition: file=)
 - when I access the prov ontology with Accept: application/rdf+xml (resp.
text/turtle), my browser automatically names the document "prov" -->
"prov.rdf" (resp. "prov.ttl") would be better.


Good luck with the Proposal submissions !
Best,
Maxime

Le ven. 21 avr. 2017 à 11:55, Phil Archer <phila@w3.org> a écrit :

> Maxime, I'll ask about the 303 thing - I see your point.
>
> Meanwhile I've fixed the 403 problem in the relevant directories. I'll
> add the other serialisations when I get a minute but right now I'm up
> against Proposal submission deadlines (along with a lot of other
> Europeans!)
>
> Phil
>
> On 20/04/2017 22:17, Maxime Lefrançois wrote:
> > Hi Phil,
> >
> > thank you, that's already excellent, sosa, ssn,ssn-dul, ssnx, are loaded
> > properly (at least) by Protégé and vowl.
> >
> > about the 303 redirection to the index.html, my understanding was that
> 303
> > can mean "I redirect you to another resource that describes what you're
> > looking for".
> > I won't fight about this, it's already great the aforementioned files are
> > available at their URLs.
> >
> > I just pushed the .rdf versions of sosa, ssn, ssnx, ssn-dul, in the same
> > folder. Sorry for not having generated them before.
> >
> > Best,
> > Maxime
> >
> >
> > Le jeu. 20 avr. 2017 à 22:30, Phil Archer <phila@w3.org> a écrit :
> >
> >> Hi Maxime, pls see inline below.
> >>
> >> On 18/04/2017 15:28, Maxime Lefrançois wrote:
> >>> Dear Phil, all,
> >>>
> >>> The ontologies developed by the SSN subgroup are ready to be published
> on
> >>> the W3C for wide review. They are:
> >>>
> >>> - SOSA: http://w3c.github.io/sdw/ssn/integrated/sosa.ttl ->
> >>> http://www.w3.org/ns/sosa/
> >>
> >> Done
> >>
> >>> - SOSA: http://w3c.github.io/sdw/ssn/integrated/ssn.ttl ->
> >>> http://www.w3.org/ns/ssn/
> >>
> >> Done
> >>
> >>> - SSNX: http://w3c.github.io/sdw/ssn/integrated/ssnx.ttl ->
> >>> https://www.w3.org/2017/01/ssn-ssnx/
> >>
> >> Done, with the ttl file and a generated .owl file served through conneg.
> >>
> >>
> >>> - SSN-DUL: http://w3c.github.io/sdw/ssn/integrated/ssn-dul.ttl ->
> >>> https://www.w3.org/ns/ssn/dul/
> >>
> >> Done
> >>
> >>> - SOSA-O&M: http://w3c.github.io/sdw/ssn/rdf/sosa-om-mapping.ttl ->
> >>> https://www.w3.org/ns/sosa/om
> >>> - http://w3c.github.io/sdw/ssn/rdf/sosa-oboe-mapping.ttl ->
> >>> https://www.w3.org/ns/sosa/oboe
> >>> - http://w3c.github.io/sdw/ssn/rdf/sosa-prov-mapping.ttl ->
> >>> https://www.w3.org/ns/sosa-prov
> >>
> >> I have also done these but there's a problem that I can't figure out and
> >> have asked our webmaster for help. If you navigate to the actual files
> >> (which for weird W3C reasons are called Overview.ttl, not index.ttl)
> >> you'll see them. But knock off the filename and you get a 403. No idea
> >> why - hence the call for help, but it's the kind of thing our webmaster
> >> (Denis) will have fixed in a trice.
> >>
> >>
> >>
> >>>
> >>> Document
> >>>
> >>
> https://github.com/w3c/sdw/blob/gh-pages/ssn/integrated/proposed-server-specification.md
> >>> proposes
> >>> some functional specifications for serving them on the W3C server. All
> >> the
> >>> subtleties proposed in this document would make these ontologies
> >> published
> >>> in conformance with the best practices, and more.
> >>
> >> Hmmm... no, sorry. We don't do 303s from the namespace to the TR doc.
> >> They're different resources, not just different serialisations of omne
> >> resource.
> >>
> >> The /ns space doc is the ontology definition file, nothing else. The /TR
> >> doc is the Technical Report that includes all the front matter,
> >> explanations, diagrams, references etc. If you want an HTML doc at the
> >> namespace, OK, that's good, but it should just be the definitions. But
> >> you can get away with something much simpler, see
> >> https://www.w3.org/ns/oa, https://www.w3.org/ns/dcat etc.
> >>
> >> I'll let you know when the 403s are fixed.
> >>
> >> Do you think it's worth generating RDF/XML serialisations of the TTL
> >> files? Not a big job but it's not one I've done so far.
> >>
> >> Cheers
> >>
> >> Phil
> >>
> >>>
> >>> Best,
> >>> Maxime
> >>>
> >>
> >> --
> >>
> >>
> >> Phil Archer
> >> Data Strategist, W3C
> >> http://www.w3.org/
> >>
> >> http://philarcher.org
> >> +44 (0)7887 767755 <+44%207887%20767755> <+44%207887%20767755>
> >> @philarcher1
> >>
> >
>
> --
>
>
> Phil Archer
> Data Strategist, W3C
> http://www.w3.org/
>
> http://philarcher.org
> +44 (0)7887 767755 <+44%207887%20767755>
> @philarcher1
>