Re: WebID default serialization for WebID 2.x

On 1/21/22 10:01 AM, Martynas Jusevičius wrote:
> Hi,
>
> IMO the authoritative document in this area is the Architecture of the
> World Wide Web. Section "3.2.2. Fragment identifiers and content
> negotiation":
> https://www.w3.org/TR/webarch/#def-coneg

Hi Martynas,

Yes, but that doesn't imply that content-negotiation has anything to do 
with WebID or Linked Data principles.

The key thing here is not to inadvertently conflate issues.

We just want to name Agents unambiguously, and describe them using 
documents comprising machine-readable structured data that leverages 
RDF. That's it.

The moment we move the bar by seeking some mandatory content-type 
everything falls apart, at the spec level. I've fought tirelessly over 
this matter for years re W3C specs, but with moderate success (i.e., 
these days you do tend to see JSON-LD and RDF-Turtle as SHOULDs).

Naturally, within an organization, a technical spec for a solution based 
on WebID could be such that the following are mandated:

1. Use Content-Negotiation to handle Content-Type variety re WebID-TLS 
protocol handler

2. Support Multiple Content-Types when generating WebID-Profile documents

3. Support a broad range of WebID-Profile docs e.g., even pure JSON docs 
(by handling JSON to RDF transformation)

WebID is in its current state due to conflation. That's why we've moved 
on to NetID as a superset based on what's outlined above i.e., we 
(OpenLink) take responsibility for handling different content-types re 
any TLS Handshake extension associated with WebID- or NetID-TLS protocols.


Kingsley

>
> On Fri, Jan 21, 2022 at 2:38 PM Sebastian Hellmann
> <hellmann@informatik.uni-leipzig.de> wrote:
>> Hi Martynas,
>>
>> On 21.01.22 14:11, Martynas Jusevičius wrote:
>>> Agents should use content negotiation to retrieve the most appropriate
>>> RDF format. WebID documents are not different from Linked Data in
>>> general in that respect.
>> Content negotiation is a cool method to deliver different formats. I
>> have a question for this one actually. Is there some official document
>> that describes the relation between content negotiation and linked data?
>> It isn't mentioned here:
>> https://www.w3.org/DesignIssues/LinkedData.html  and otherwise I only
>> know this one: https://www.w3.org/TR/cooluris/    . LDP mentions it in
>> 4.3.2 HTTP GET  . They also follow an approach, where only Turtle and
>> JSON-LD are a MUST and also define Turtle as the default. Any other
>> document that is relevant and official here?
>>
>> We recently started to put our WebIDs on github.io:
>> https://kurzum.github.io/webid.ttl  (sufficient security for
>> non-critical services). Not sure, github.io even allows content
>> negotiation. It is quite obvious that each additional MUST requirement
>> in the WebID spec or any WebID spec will add a barrier towards adoption.
>> Not sure, if there are strong use cases for the content negotiation MUST.
>>
>> I found it quite practical, that you can just put a file on a web server
>> (in this case github.io ) to serve as webid.
>>
>> Anyhow, I see that the "Wallet Connect" login in Crypto became quite
>> adopted with hundred of wallet implementations, so maybe a similar
>> technology like WebID (probably based on pure JSON) will be developed
>> and widely adopted from this side.
>>
>> -- Sebastian
>>

-- 
Regards,

Kingsley Idehen 
Founder & CEO
OpenLink Software
Home Page: http://www.openlinksw.com
Community Support: https://community.openlinksw.com
Weblogs (Blogs):
Company Blog: https://medium.com/openlink-software-blog
Virtuoso Blog: https://medium.com/virtuoso-blog
Data Access Drivers Blog: https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers

Personal Weblogs (Blogs):
Medium Blog: https://medium.com/@kidehen
Legacy Blogs: http://www.openlinksw.com/blog/~kidehen/
               http://kidehen.blogspot.com

Profile Pages:
Pinterest: https://www.pinterest.com/kidehen/
Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen
Twitter: https://twitter.com/kidehen
Google+: https://plus.google.com/+KingsleyIdehen/about
LinkedIn: http://www.linkedin.com/in/kidehen

Web Identities (WebID):
Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i
         : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this