- From: Martynas Jusevičius <martynas@atomgraph.com>
- Date: Wed, 26 Jan 2022 10:45:21 +0100
- To: Jonas Smedegaard <jonas@jones.dk>
- Cc: Jacopo Scazzosi <jacopo@scazzosi.com>, Henry Story <henry.story@gmail.com>, Kingsley Idehen <kidehen@openlinksw.com>, public-webid <public-webid@w3.org>
Why do you interpret "MUST provide Turtle" in a way that precludes conneg? With conneg, send the right header and Turtle will be provided. Send a different header and "other serialization formats" might be provided. If we follow interpretation #1 (Turtle returned absent any Accept header), what will happen when you open such a WebID document in a web browser? You get Turtle? That would be absolute nonsense, as WebIDs can have HTML representations. I'm pretty sure TimBL would agree -- maybe we should try to get his feedback on this thread. On Wed, Jan 26, 2022 at 10:38 AM Jonas Smedegaard <jonas@jones.dk> wrote: > > Quoting Martynas Jusevičius (2022-01-26 10:08:38) > > What does "Turtle required" even mean? > > 1. without any Accept request header, a WebID profile document MUST > > always return Content-Type: text/turtle? > > 2. with an Accept: text/turtle request header, a WebID profile > > document MUST always return Content-Type: text/turtle? > > 1. > > Also, requesting agent MUST always be able to parse Turtle, even if > always requesting something else. > > > Try search <https://www.w3.org/2005/Incubator/webid/spec/identity/> for > the word "turtle"... > > Quoting from > <https://www.w3.org/2005/Incubator/webid/spec/identity/#introduction>: > > > A WebID Profile Document is a Web resource that MUST be available as > > text/turtle [turtle], but MAY be available in other RDF serialization > > formats (e.g. [RDFA-CORE]) if requested through content negotiation. > > > Quoting from > <https://www.w3.org/2005/Incubator/webid/spec/identity/#terminology>: > > > The server MUST provide a text/turtle [turtle] representation of the > > requested profile. > > Quoting from > <https://www.w3.org/2005/Incubator/webid/spec/identity/#publishing-the-webid-profile-document>: > > > WebID requires that servers MUST at least be able to provide Turtle > > representation of profile documents, but other serialization formats > > of the graph are allowed, provided that agents are able to parse that > > serialization and obtain the graph automatically. > > > Quoting from > <https://www.w3.org/2005/Incubator/webid/spec/identity/#processing-the-webid-profile>: > > > The Agent requesting the WebID document MUST be able to parse > > documents in Turtle [turtle], but MAY also be able to parse documents > > in RDF/XML [RDF-SYNTAX-GRAMMAR] and RDFa [RDFA-CORE]. > > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private
Received on Wednesday, 26 January 2022 09:45:46 UTC