- From: Martynas Jusevičius <martynas@atomgraph.com>
- Date: Wed, 26 Jan 2022 13:50:57 +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>
I'll reply inline :) > > This exactly fits my interpretation #2: with an Accept: text/turtle > > request header, a WebID profile document MUST always return > > Content-Type: text/turtle > > So with your interpretation #2, what is served in the *default* > situation of *not* explicitly requesting Turtle? Normally that should be up to the server. In my logs I sometimes see that our clients and servers communicate in formats I didn't even know Jena supports, like binary RDF-Thrift. If a server has a Turtle serializer, it will satisfy the "MUST be able to provide text/turtle", period. The difference is regarding how this constraint is communicated: 1. by hardcoding it into the protocol specification 2. by doing conneg with an Accept header that prefers text/turtle (gives it highest q value) You seem to be advocating #1, but in what way does #2 not satisfy the same MUST constraint? Plus that #2 actually follows the WWW Architecture. And I'm also still interested in hearing what happens when HTML is requested in case of #1. > > > - 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 12:51:22 UTC