Re: Observations on WebID definition and specification

On 2/6/24 3:51 PM, Kingsley Idehen wrote:
>
>
> On 2/6/24 11:54 AM, Nathan Rixham wrote:
>> It's perhaps useful to remember the 2011 also 
>> https://www.w3.org/2005/Incubator/webid/spec/drafts/ED-webid-20111123/
>>
>> > The Server must publish the document in at least the XHTML+RDFa 1.1 
>> [XHTML-RDFA] serialization format or in RDF/XML [RDF-SYNTAX-GRAMMAR]. 
>> The document may be published in a number of other RDF serialization 
>> formats, such as N3 [N3] or Turtle [TURTLE]. Any serialisation must 
>> be transformable automatically and in a standard manner to an RDF 
>> Graph, using technologies such as GRDDL [GRDDL-PRIMER].
>>
>> MUST mediatype is the one contentious bit that always changes with 
>> time, and always will.
>
>
> Indeed, those of us who have consistently advocated for media-type 
> agnostic specifications (myself included) are not merely reflecting in 
> hindsight. Thanks for the reference to that older specification.
>
> For what it’s worth, the current debates surrounding the inclusion of 
> JSON-LD echo past discussions about incorporating Turtle alongside 
> RDF/XML, among others. Technical specifications should not serve as 
> branding tools. I STRONGLY doubt that TimBL would endorse such an 
> approach to spec creation.
>
> The integration of JSON-LD into the WebID specification was delayed 
> primarily because, until version 1.1—which was released years after 
> two variants of the WebID spec—it did not support relative URLs 
> <https://datatracker.ietf.org/doc/html/rfc1808>. This limitation was a 
> significant barrier because relative URLs are crucial to the open 
> standards and principles of Linked Data. Essentially, JSON-LD's 
> earlier versions presented a contradiction in its application of 
> Linked Data Principles through a JSON-based format.
>
> Currently, I would be quite surprised if TimBL had any reservations 
> about JSON-LD 1.1 being considered on par with RDF-Turtle in the 
> context of an updated WebID Spec. His concerns were justifiably 
> focused on the issue with relative URLs 
> <https://www.w3.org/DesignIssues/Relative.html>. I have even proposed 
> discussing this matter directly with him, should it prove to be the 
> last obstacle.
>
>
> Kingsley
>

Some references that I forgot to add to the reply above, that should 
also provide context for the *_surprising view_* about media-type 
agnosticism being in hindsight. Anyway, those links should do for now, 
with regards to some historic perspective. If more are needed e.g., the 
actual vote that lead to the current problem, I'll dig that up to (I 
know I dropped in one of the growing comment threads last month).

[1] https://lists.w3.org/Archives/Public/public-webid/2012Nov/0020.html 
-- WebID Definition Take 2
[2] 
https://lists.w3.org/Archives/Public/public-webid/2012Nov/thread.html#msg21 
-- Some History


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