Re: WebID default serialization for WebID 2.x

On 1/26/22 9:49 AM, Kingsley Idehen wrote:
> On 1/26/22 4:58 AM, Ruben Taelman wrote:
>> Hi all,
>>
>> I haven’t followed this thread from the start, so apologies if this has been brought up before.
>> But I would like to emphasise this point:
>
> Hi Ruben,
>
>
>>> what will happen when you open such a WebID document in a web
>>> browser? You get Turtle? That would be absolute nonsense, as WebIDs
>>> can have HTML representations.
>> I very much agree with this.
>>
>> My personal profile is hosted on a static file server as HTML with RDFa.
>> Therefore, I do not have the possibility to provide content negotiation on this server,
>> so I expect clients to be able to parse HTML and extract RDFa as RDF.
>> I think this is a pretty common setup on the Web, so I think it is crucial that the WebID spec is compatible with this.
>>
>> This means that (IMO), the WebID spec should not*require*  documents to be available in certain serializations.
>> Instead, clients fetching WebID documents should just be able to parse any standardized RDF serializations via content negotiation.
>
>
> Yes, this is the point being made about the MUST and SHOULD issues in 
> the current spec.
>
> Also note, as I've indicated in earlier posts, *content-negotiation is 
> an implementation detail* (client or server) that should never be in 
> any spec be it WebID, RDF,  or even the fundamentals of Linked Data 
> Principles.
>
> HTML is the dominant content-type on the Web. It also has a broadly 
> supported "best practice" for RDF deployment using Structured Data 
> Islands via the <script/> tag [1].
>
> Hopefully, we will arrive a notion of a WebID that denotes and Agent 
> and resolves to an HTML-based profile doc comprising Structured Data 
> Islands constructed using a variety of Structured Data Representation 
> notations.
>
> The Web has been designed for all of this since inception, broad 
> understanding and acceptance remains the challenge, IMHO.
>
> Links:
>
> [1] http://webdatacommons.org/structureddata/2021-12/stats/stats.html 
> -- Web Data Commons Report covering the growth of Structured Data 
> Islands deployed via HTML
>

Correction:

Yes, this is the point being made about the MUST and SHOULD issues in 
the current spec.

Also note, as I've indicated in earlier posts, *content-negotiation is 
an implementation detail* (client or server) that should never be in any 
spec be it WebID, RDF,  or even the fundamentals of Linked Data Principles.

HTML is the dominant content-type on the Web. It also has a broadly 
supported "best practice" for RDF deployment using Structured Data 
Islands via the <script/> tag [1].

Hopefully, examples will emerge comprising:

A WebID that denotes *an* Agent and resolves to an HTML-based profile 
doc comprising Structured Data Islands constructed using a variety of 
Structured Data Representation notations.

The Web has been designed for all of this since inception, broad 
understanding and acceptance remains the challenge, IMHO.

Links:

[1] http://webdatacommons.org/structureddata/2021-12/stats/stats.html -- 
Web Data Commons Report covering the growth of Structured Data Islands 
deployed via HTML


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