Re: WebID default serialization for WebID 2.x

On 1/26/22 1:53 AM, Henry Story wrote:
>
>> On 26. Jan 2022, at 00:58, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>>
>> On 1/25/22 6:08 PM, Nathan Rixham wrote:
>>> On Tue, Jan 25, 2022 at 10:58 PM Kingsley Idehen <kidehen@openlinksw.com> wrote:
>>> On 1/25/22 4:29 PM, Nathan Rixham wrote:
>>>> On Tue, Jan 25, 2022 at 9:23 PM Kingsley Idehen <kidehen@openlinksw.com> wrote:
>>>> On 1/25/22 1:28 PM, Nathan Rixham wrote:
>>>>> Would a fair definition of a valid WebId then be something like: A URI is a valid WebIdentifier if it dereferences to a valid WebId-Profile describing the URI with the minimum set of required properties (type, name, public_keys)?
>>>> A WebID is a resolvable identifier that denotes an agent. It resolves to a WebID Profile Document.
>>>>
>>>>   How do you know it's a WebID before you resolve it?
>>> Good question!
>>>
>>> By deciding the want to denote yourself using a given identifier, relative to your profile document.
>>>
>>> Let me rephrase, and suggest looking at it the other way around: given a random IRI <y> how do I know <y> is a webid / refers to an Agent, without first resolving it? and as a sub point, is a "valid" webid?
>>
>> You know it is a WebID because the spec says its is a URI that denotes an Agent. That's it, really :)
>>

Hi Henry,


> You used to know it’s a WebID because we had the cert ontology that related the WebID to a public Key.


That isn't how I recall it. Again, we don't want to conflate things 
since the following are distinct:

1. WebID
2. WebID-Profile Document
3. WebID-TLS Protocol -- which is informed by an Ontology


> The core purpose of having a WebID was to tie it into the WebID-TLS authentication scheme.


It is/was a puzzle-piece for solving a larger puzzle i.e., identity 
authenticity that scaled to both the Internet and Web.

The ultimate goal was that we could finally build solutions that 
loosely-coupled

1. Identity
2. Identification
3. Authentication
4. Authorization
5. Storage

Basically, the puzzle-pieces that enable a Read-Write Web (RWW) based on 
existing open standards.


Kingsley

>
> For me that authentication piece has now moved over to using the IETFS ”Signing HTTP Messages”.
> I have an implementation in Scala https://github.com/bblfish/httpSig that compiles to JS and Java
> and am working on the authentication part.
>
> Now WebID is still key in the Solid ecosystem as a way to tie together many different identifiers
> for agents, links to their apps, their stores, etc… So that community is a very important user of
> WebIDs with many deployed systems and apps. Changes would need to empirically work out how it chimes
> with what is deployed there.
>
> Henry
>   
>
>

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