Re: Towards Solid Lite

On 11/2/23 12:13 PM, Melvin Carvalho wrote:
>
>
> čt 2. 11. 2023 v 15:49 odesílatel Kingsley Idehen 
> <kidehen@openlinksw.com> napsal:
>
>     Hi David,
>
>     On 11/2/23 9:25 AM, David Mason wrote:
>     > WebID. I don't think it's widely used and as-is maybe not
>     appropriate
>     > to a contemporary solution, though I understand its emphasis on
>     linked
>     > data.
>
>     A WebID is an identifier used to name the subject of a profile
>     document.
>     It is first an foremost an identifier for naming agents.
>
>     WebID-TLS is one of many protocols that can be used to authenticate
>     credentials expressed in a profile document to which a WebID resolves.
>
>     Resolution can be implicit, courtesy of an "#" based fragment id
>     tacked
>     on to a profile page url or explicitly via content negotiation.
>
>     Unfortunately, WebID has been mired in the same terminology
>     conflation
>     woes that have afflicted RDF (and related matters) at large.
>
>     Increasingly, courtesy of Google's schema.org <http://schema.org>
>     push, many webpages ( HTML
>     docs) are simply evolving into profile documents i.e., this generally
>     misunderstood concept is quietly becoming mainstream -- even
>     though SEO
>     using Schema.org (i.e., Semantic SEO) is the prime driver.
>
>
> There is a principle of "modularity" at play here.


I would hope.


> WebID itself can be tied to many different authentication systems, and 
> put together like lego bricks.


Exactly.


> This was the original idea behind orthogonal specs in the web space.
>
> See the principle of design of the web:
>
> https://www.w3.org/DesignIssues/Principles.html
>
> "Its is not only necessary to make sure your own system is designed to 
> be made of modular parts. It is also necessary to realize that your 
> own system, no matter how big and wonderful it seems now, should 
> always be designed to be a part of another larger system."


Yes, that's what I mean whenever I use the phrase "loose coupling," 
which is facilitated by open standards.


>
> Another quote from Tim Berners-Lee I think sums it up nicely:
>
> "The way the Web spread was a piece at a time. So you could take html
> without taking http. So the failure of NEXT was a lesson, don’t try to
> sell it all at one time. Sell each piece on its own merits. Never
> insist that everybody take all. They will take all the pieces once
> they see how it fits together."
>
> I think it's an approach that can work well both with the web and with 
> Solid Lite.  So that Solid can spread in the same way that the 
> original web was spread, resulting in more choice for the end user.


Yes, but the abstraction layer itself (Solid Lite or Heavy) is the 
vehicle for facilitating loose coupling.

Client Side Components:

1. WebID -- an identifier
2. WebID Profile Document -- an HTML document, since is already an 
established Web component that's in ubiquitous use
3. Structured Data embedded in HTML doc -- this needs to be constructed 
using RDF where the recommended notations are JSON-LD, Microdata, or 
POSH (all of these are generally supported by development tools across 
Web Developer communities)
4. Authentication Protocols -- this is where it's been kinda murky, but 
there is a solid-auth library that does work well (re SSO) based on our 
own usage experience

Server Side Components:
1. Authentication Protocol Abstraction implementation -- authentication 
service providers implemented using the solid-auth API (this is akin to 
building ODBC or JDBC Drivers for their respective APIs used by clients 
for database interaction)2. ACL Ontology
3. ACL processor
4. Backend Storage via HTTP operations

Related

1. https://openlinksoftware.github.io/Data-Entry-Form-AuthV2 -- demo SPA 
that uses solid-auth library in the manner described above; you can use 
this app to create entity relationships across resource providers via 
their respective sparql endpoints (dbms tab) or document urls 
(filesystem tab)
2. https://github.com/OpenLinkSoftware/Data-Entry-Form-AuthV2 -- project 
repo

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