Re: WebID-JSON-LD Spec

On 11/8/23 1:09 PM, Nathan Rixham wrote:
> I keep coming back to:
>
> *Overview*
> WebID defines a <uri> that, when */dereferenced/*, should yield an RDF 
> response asserting that <uri> is a webid:Agent, confirming it as a 
> valid WebID.
>
> *Sub-specifications*
> WebID also introduces an open-ended list of sub-specifications. For 
> each valid RDF response type, a corresponding webid-{type} 
> implementation can be developed. These implementations are constrained 
> to require only the specific RDF response type they are designed for.
>
> *Dereference*: In the context of this specification, "dereference" 
> signifies the process of resolving a Uniform Resource Identifier (URI) 
> to access the web resource it represents. This procedure typically 
> involves initiating an HTTP request to the URI and retrieving the 
> associated representation or information, which may include an RDF 
> response in the case of WebID. In essence, "dereferencing" pertains to 
> the act of accessing the web resource specified by the given 
> URI. Note: For HTTP requests this may involve HTTP status code 303.
>
> Optionally just remove RDF too
>
> *Overview*
> WebID defines a <uri> that, when dereferenced, should yield a response 
> asserting that <uri> is a webid:Agent, confirming it as a valid WebID.


A WebID is an HTTP URI that *unambiguously* names an Agent.

That sentence embodies what a WebID has always been. It is simple and 
too the point, despite actually being "deceptively simple" courtesy of 
HTTP-based naming.


>
> *Sub-specifications*
> WebID also introduces an open-ended list of sub-specifications. For 
> each valid response type, a corresponding webid-{type} implementation 
> can be developed. These implementations are constrained to require 
> only the specific response type they are designed for.


A WebID is loosely bound to a variety of profile document types 
associated with what can be seen as WebID Profile Document Type 
specifications.


>
> *Dereference*
> In the context of this specification, "dereference" signifies the 
> process of resolving a Uniform Resource Identifier (URI) to access the 
> web resource it represents. This procedure typically involves 
> initiating an HTTP request to the URI and retrieving the associated 
> representation or information. In essence, "dereferencing" pertains to 
> the act of accessing the web resource specified by the given URI.


A WebID resolves to a WebID Profile Document.

Note on resolution:

This can be achieved using any of the following approaches:

1. Implicit resolution -- whereby simply adding a "#" fragment 
identifier to the WebID Profile Document URL *component* of a WebID does 
the trick

2. Explicit resolution -- by way of content negotiation

This is what a WebID and its associated WebID Profile Document Types 
have always been about.

My only difference with my late buddy Henry Story lay in the matter of 
tightly coupling a WebID to a WebID Profile Document Type. Initially, 
that was RDF/XML and then it evolved to RDF-Turtle -- neither being 
appropriate for a spec aimed at broad adoption; due to the fundamental 
need for proper loose-coupling.

Today, users and apps are producing WebIDs and WebID-Profile documents 
at an alarming rate. A spec that doesn't understand and appreciate this 
fact will not reach any useful point of adoption -- IMHO.


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