Re: (human) identity fabric (agents concepts linked)

Sorry, re: clarifications,

What did it do back in ~2011/2 when I first installed it? (Vs. now?). I can
pull the dates, but you likely have them in your licensing server??  I was
trying to do a POC via building a heritage capability as an initial
usecase, at the time.... (supporting a Hysterical/ historical society)...

Does it have more functionality since then?  I assumed the answer was "yes"
particularly given the status of "web payments" (pre credentials), way back
then (before I ended up on the lists, something, I didn't consider would
ever happen in my life, at the time)...

Limitations linked to creating a knowledge banking framework. I started
concepts in 2000 ("information bank" or ibank) which progressed to
"knowledge banking" circa 2011/2012 after doing some work "updating" old
work, from mid 2010 (indigenous application started 2009/10)..

I think you're first "dataspaces" demo was 2007???  V.interested in
"temporal web" / provenance solutions....

Dignity enhancing web (vs. web slavery, or worse).

Timothy Holborn.

On Sat, 15 May 2021, 5:07 am Kingsley Idehen, <kidehen@openlinksw.com>
wrote:

> On 5/14/21 1:07 PM, Timothy Holborn wrote:
>
> Overall; the underlying intent; was to create complex AUTH / Endification
> / Identification fabric capabilities; that could in-turn, support complex
> (hyper-private) semantics, that could only be brought about
> post-technological growth; with support of political will...  i"m not sure
> that' going to happen (in the western world, first or at all); but,  i
> wanted to make a note that the examples provided by openlink software
> (virtuoso) or Project Hydra (samvera nowadays?) didn't have enough
> functionality back in 2011/2; as such, i sought to improve it, to support -
> human beings, unto 'rule of law', for a moral economy, etc...
>
>
> Hi Timothy,
>
> To be clear:
>
> OpenLink Virtuoso <https://virtuoso.openlinksw.com> is a platform that
> includes a multi-protocol authentication layer. One of the many supported
> protocols is WebID-TLS. We also support NetID-TLS which is basically
> WebID-TLS decoupled from http: scheme URIs e.g., it supports ldap: scheme
> URIs.
>
> Authorization wise, our technology is driven 100% by RDF
> sentences/statements (informed by terms from relevant ontologies).
>
> I don't see limitations in RDF that aren't surmounted by the use of SPARQL
> as a Rules Language (like Datalog back in the day) re authorization via
> access controls.
>
> With the clarifications above outlined, what limitation are you speaking
> about?
>
> --
> 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
>
>