Re: WebID default serialization for WebID 2.x

On Wed, Jan 26, 2022 at 2:41 PM Jonas Smedegaard <jonas@jones.dk> wrote:
>
> Quoting Martynas Jusevičius (2022-01-26 13:50:57)
> > > > 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.
>
> Yes, lots of things are possible, in non-default cases.

Non-default? That is the default behavior if you let conneg do its job.

> > 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.
>
> WebID is not an architecture.  It fits into other specs integrating with
> an architecture, and _those_ specs may suggest (MAY) or recommend
> (SHOULD) or mandate (MUST) certain behavious related to that
> integration.  E.g. a nuclear power plant might specify that if requested
> something that cannot be provided then do not serve anything else nor
> throw an error, but INITIATE SCRAM: https://en.wikipedia.org/wiki/Scram
>

You don't seem to be answering, so I'm losing interest.

>
> > And I'm also still interested in hearing what happens when HTML is
> > requested in case of #1.
>
> Conneg is specified only as optional, not mandatory, in core WebID spec,
> and consequently for the *default* case (i.e. where only MUSTs are
> covered and therefore conneg is totally ignored) any conneg constraints
> are totally ignored and specification says Turtle format MUST be
> supported so Turtle format will get delivered.

Again, is this an answer? Are you really saying you're OK to break
WebID documents in web browsers by mandating that Turtle (or JSON-LD)
is returned no matter what?

Here's my suggestion on how to formulate the constraint: "Provided
with an Accept request that prefers text/turtle (it is assigned the
highest q value), the server MUST return text/turtle".
- servers that only can return Turtle will (ignore the header and) return Turtle
- servers that support conneg will return Turtle because conneg will do its job
Is that acceptable?

>
>
>  - 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 13:55:52 UTC