Re: WebID default serialization for WebID 2.x

Quoting Martynas Jusevičius (2022-01-26 13:27:32)
> I saw your quotes but I'm not convinced. On the contrary, section "6. 
> Processing the WebID Profile" explicitly describes conneg behavior and 
> even has an example of the Accept header that makes Turtle 
> *preferred*: 
> https://www.w3.org/2005/Incubator/webid/spec/identity/#processing-the-webid-profile

That example describes a "preferred" behavior, not a "required" one.

The "default" behaviour is "when all else fails", i.e. skipping SHOULDs 
and following only MUSTs.

Section 6 also says this:

> The result of this processing should be a graph of RDF relations that 
> is queryable, as explained in the next section.

...but I can only interpret "next section" to be "Acknowledgments".

I guess those mentions of connneg is a leftover from before the 
decoupling of WebID-TLS.  That makes the most sense to me.  I am sure 
that it might make the most sense to others to maintain tight coupling - 
otherwise we wouldn't have this long email thread.


> 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?


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private