- From: Martynas Jusevičius <martynas@atomgraph.com>
- Date: Fri, 21 Jan 2022 14:11:14 +0100
- To: Melvin Carvalho <melvincarvalho@gmail.com>
- Cc: public-webid <public-webid@w3.org>
Received on Friday, 21 January 2022 13:12:39 UTC
I disagree. Agents should use content negotiation to retrieve the most appropriate RDF format. WebID documents are not different from Linked Dat in general in that respect. What is your issue with the conneg approach? Martynas On Fri, 21 Jan 2022 at 13.20, Melvin Carvalho <melvincarvalho@gmail.com> wrote: > There was a thread in August 2021 regarding the webid default > serialisation, that seems to have stalled, in the github area > > Given that WebID 1.0 is still in use, I propose that we have a 1.x branch > that continues to support those using it > > For future implementations, I propose that WebID 2.x: > > 1. Has a default serialization (MUST in the spec) -- this can be a point > of debate > 2. What the default serialization should be for future versions > > I call for a major version upgrade so that existing implementations can > continue to work, and because there are potential breaking changes > > Given that (2) follows from (1) it would be good to solve (2) and get the > opinion of the group > > What is view of the group on what should be the default serialization of a > webid? > > My vote: JSON(-LD) as default, including structured data islands which > are part of the JSON-LD 1.1 spec > > Other opinions welcome! >
Received on Friday, 21 January 2022 13:12:39 UTC