Re: Coherent (modern) definition of RWW

On Wed, 19 May 2021 at 16:47, Kingsley Idehen <kidehen@openlinksw.com>
wrote:

> On 5/19/21 9:02 AM, Jonas Smedegaard wrote:
>
> Quoting Nathan Rixham (2021-05-19 14:37:51)
>
> On Wed, May 19, 2021 at 1:20 PM Jonas Smedegaard <jonas@jones.dk> <jonas@jones.dk> wrote:
>
>
> Quoting Melvin Carvalho (2021-05-19 13:14:37)
>
> On Tue, 18 May 2021 at 21:33, Kingsley Idehen <kidehen@openlinksw.com> <kidehen@openlinksw.com> wrote:
>
> The Super Set should always be the point of focus if
> interoperability is the goal. That's a classic route to more
> "AND" and less "OR" .
>
> +100 to this
> ...
> We should be inclusive of the many thousands (millions?) of
> developers that enjoy working with JSON(-LD)
>
> And also introduce them to the benefits of a more structures EAV
> model ie making merges cheap, enabling federation, allowing anyone
> to say anything about anything (ie decentralized features),
> discovery, follow your nose, indexing, allowing multiple things to
> exist in a document.
>
> And we can also learn from the tooling and network around JSON,
> how it makes parsing easy and ubiquitous, fast startup time, easy
> to work with arrays, easy to work with numbers
>
> Related to the above, Atomic Data seems an interesting concrete
> approach to use a subset of RDF optimized for lesser confusion for
> non-RDF developers: https://docs.atomicdata.dev/motivation.html
>
> Very nice, when multiple parties independently create the same thing,
> for years on end, then it's reasonable to assert they're on the right
> path, and encountering the same issues w/ the same clear solution.
>
> Are you saying that others have invented something similar to Atomic
> Data?  I'd be quite interested in learning more about that.
>
>
> Yes, as in Read-Write Linked Data technology which I think we've been
> doing for eons :)
>
> Most recently, we put some this work into higher level tools outside of
> Virtuoso and our OpenLink Data Spaces platforms such as:
>
> [1] The OpenLink Structured Data Sniffer (OSDS) for Chromium-based
> Browsers
> <https://chrome.google.com/webstore/detail/openlink-structured-data/egdaiaihbdoiibopledjahjaihbmjhdj?hl=en>
> -- which can process Linked Data deployed via URIs; transform JSON and CSV
> into Linked Data (5-Star variety); handled storage to File System or DBMS;
> deconstruct URIs and even offer SPARQL Edititing etc..
>
> [2] The OpenLink Structured Data Sniffer for Firefox
> <https://addons.mozilla.org/en-US/firefox/addon/openlink-structured-data-sniff/>
>
> There are also other RWW tools like Dokie.li [3] that work very well with
> OSDS e.g., inline editing of existing HTML docs that includes marking out
> relations using Nanotation (a little scheme I created for generating Linked
> Data from blocks of structured data embedded in text).
>
> [3] Dokie.li Extension for Chromium-based Browser
> <https://chrome.google.com/webstore/detail/dokieli/ddmhaonbhodhgkaljpjlglodncddalid?hl=en>
>
>
> For the time-challenged, here are some screencasts demonstrating aspects
> of these browser extensions:
>
> [1] Demonstrating the combined use of OSDS and Dokie.li
> <https://youtu.be/J-T_lMQZECQ>
>
> [2] Demonstrating OSDS and The OpenLink Structured Data Bot (OSDB)
> <https://youtu.be/1EgpVTlY05A> re "Search Action" discovery from RDF
> published via HTML using terms from the Schema.org vocabulary
>
> [3] My screencasts demo collection on YouTube
> <https://www.youtube.com/c/KingsleyIdehen/videos>
>

We have some links in our wiki:

https://www.w3.org/community/rww/wiki/ReadWrite_Protocols

Although there is some link rot and some of it has not been updated in many
years.  But, well, it's a wiki, so feel free to change it.  I've just
recovered my w3c password so I can help a bit, and perhaps add a new page
for a temporal read write web (both local and global)

This article, tho over 10 years old, is part of the motivation of the
group.  I think it has aged quite well

https://www.w3.org/DesignIssues/ReadWriteLinkedData.html

In particular noting:

"Outstanding issues
This article does not deal with the database-like storage APIs and
specifically with atomic transactions, or fine-grained access control."

Since then, web access control has been developed in this group to be
usable.  Not sure about atomic transactions, tho it is in some part related
to time.  The new thing now is (byzantine) fault tolerance, too ...

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