Re: Need for a WebID FAQ

Few Thoughts,

Traditionally, with WebID - there's the published docs about WebID URIs
(inc. FOAF) and then there is the various WebID AUTH methods, such as
WebID-TLS, WebID-RSA and i assume somewhere WebID-OIDC  (with
WebID-WebAuthn on the way?)

Perhaps also - there could be a lack of documentation about three things,

1. WebID's that may not use foaf (ie: twitter.com/webcivics /
linkedin.com/in/ubiquitous ) and that are not 'semantically enabled' or
'rww / solid' enabled?

To the best of my recollection - a WebID is a URI that describes an Agent.
Some URIs (ie graph.facebook.com/myuri ) may 'speak' RDF, others may not.

2. Intelligent Agents / WebID - where the WebID may produce dynamic records
in a manner that interoperable supports the needs of agents in a dynamic
manner....

or perhaps the latter conflates Solid-WebID related functions, to something
that may be considered solid-smartAgents or some such thing?

3.  With respect to 'privacy enhanced design', is it not true that a
service provider may generate URIs that provide permissive access, but that
do not otherwise identify the intended beneficiaries of that link unless
authenticated?  ie:  a generated WebID that's used to manage the relations
between two agents, or an agent and a class of other agent/s.

Noting: https://www.rogerclarke.com/ID/IdModel-1002.html  ( Figure 1: An
Entity-Relationship Model of Identity ) Perhaps this may be considered
something along the lines of 'endifiers'?

Am i correct in thinking traditional RWW / Solid WebIDs are not dynamic in
nature? Yet that also - from a standards point of view, perhaps this
doesn't matter?

A related issue may also be the specificity of FOAF noting WebOfThings in
particular: https://w3c.github.io/wot-thing-description/  and
consequentially,

a ponderance as to whether a 'web id agent' in terms of 'solid' may indeed
need to be clarified?  and if so, what are the implications...

FWIW - there's a great deal of implicit knowledge, and in my observations -
people seem to 'glaze over the top' of RDF, which in-turn becomes a greater
barrier than the time currently required to figure out what it's about,
once the importance of it is better understood to the agent engaged in a
nuanced 'role of the observer' tech qualification process..

Timo.

On Tue, 5 Mar 2019 at 05:16, Kingsley Idehen <kidehen@openlinksw.com> wrote:

> All,
>
> Recent discussions in this forum demonstrate a clear need for a more
> dynamic FAQ system.
>
> Here are some suggestions:
>
> [1]
>
> https://docs.google.com/spreadsheets/d/1pVsDK9TGVjLGYcrJpk0hsrDun4a-zwOyQqloTxIpRi4/edit?usp=sharing
> -- A Google Spreadsheet where content is transformed into RDF and
> published as 5-Star Linked Data (I'll handle publication)
>
> [2]  https://kidehen3.solid.openlinksw.com:8445/public/CoolStuff/faqs/
> -- Data Space from a  Solid Pod
>
> For the Google Spreadsheet, access is granted by way of request.
>
> For the solid pod, access is granted by providing me with your WebID via
> reply to this post .
>
> --
> 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
>
>
>