Re: Coherent (modern) definition of RWW

On Mon, 17 May 2021 at 17:45, Martynas Jusevičius <martynas@atomgraph.com>
wrote:

> LDP is a poor protocol period.
>
> Graph Store Protocol is more appropriate for RWW. After all, Linked
> Data can be looked at as a giant global table of quads.
>

Thanks Martynas

I've added GSP to our wiki with the text:

"Graph Store Protocol describes the use of HTTP operations for the purpose
of managing a collection of RDF graphs. This interface is an alternative to
the SPARQL 1.1 Update protocol."

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

I also added LDP, as the page has not had much love in a while.  Feel free
to improve it, if you like

The abstract of LDP is actually quite interesting:

"Linked Data Platform (LDP) defines a set of rules for HTTP operations on
web resources, some based on RDF, t*o provide an architecture for
read-write Linked Data on the web*" [emphasis mine]

The impression I get from folks is that the reaction to LDP is kind
luke-warm at best.  As an architecture, similar to webdav, it may be
missing some other pieces

Graph Store Protocol seems a valid thing to use.  I suppose it depends if
you want to use a file system, or set up a data store.  Both approaches
will need to be handled, I think


>
> On Mon, May 17, 2021 at 3:40 PM Kingsley Idehen <kidehen@openlinksw.com>
> wrote:
> >
> > On 5/17/21 8:44 AM, Timothy Holborn wrote:
> > > The concept of RWW started a long time ago.
> >
> >
> > Yes, it is as old as the World Wide Web (Web) itself.
> >
> > The Web is simply a document network constructed from hyperlinks
> > (specifically HTTP URIs) that denote:
> >
> > 1. Entities of type Document
> >
> > 2. Entity Relationship Types that are transitive in nature i.e.,
> > "links_to" relation .
> >
> > An unfortunate characteristic of the Web is that there isn't consensus
> > regarding:
> >
> > 1. Entity Identifiers
> > 2. Entity Types
> > 3. Entity Relationship Types e.g., what is the canonical "links_to"
> > relation and what is its identifier?
> >
> > So confusion reigns leaving opportunity for abuse and detrimental
> > exploitation as the world has experienced en masse re:
> >
> > 1. Quixotic state of Democracy
> >
> > 2. COVID-19 Pandemic
> >
> > 3. Misinformation and Fake News
> >
> >
> > >
> > > Question posed is;
> > >
> > > What's the modern (well referenced) definition?  (Incremental growth
> > > of past "definitions, etc.  Perhaps therein also, better clarity of
> > > previously assumed characteristics / constituencies, etc.)
> >
> >
> > A Read-Write Web is a hyperlink-based network that offers both read and
> > write capabilities to its users. Nothing has changed, bar increased
> > murkiness surrounding:
> >
> > 1. Identity
> > 2. Identification
> > 3. Authentication
> > 4. Authorization
> > 5. Storage
> >
> >
> > >
> > > A few substantial papers have been written on it, historically.
> >
> >
> > Yes, and they've achieve little if anything -- IMHO.
> >
> >
> > >
> > > So, What are some basic truths about the scope of works, and it's
> > > place in a broader ecosystem?
> > >
> > > To illustrate the deliberation / question: (as distinct to a "brand
> > > name" alternative framework; that may have differences),
> > >
> > > - RWW Builds upon LDP?
> >
> >
> > LDP is a poorly named RWW protocol.
> >
> >
> > > - concerns multi-agent use of web-cloud or web-server infrastructure?
> >
> >
> > Conceptually yes, but cannot work practically without clarity about
> > items 1-5 above. Unfortunately, these waters remain murky for political
> > rather than technical reasons -- IMHO.
> >
> >
> > > - Relates to the permissive use of software agents? (If so, how?)
> >
> >
> > See comment above.
> >
> >
> > > - is built upon HTTP(s/a/'X') agents?
> > >
> > > V2 supports
> > > - "tamper evident" provenance in (a yet to be determined) defined way?
> > > - supports informatics sources from decentralised agents (or:
> > > "blockchains")
> > > - temporal uniformity of semantic queries on a temporaral basis (or:
> > > decentralised temporal queries?)
> > >
> > > I thought I'd pose the points as a question rather than as a
> > > statement, in seeking to be constructive...
> >
> >
> > It boils down to solving the murkiness around items 1-5 above, IMHO.
> >
> >
> > Kingsley
> >
> > >
> > > Cheers,
> > >
> > > Timothy Holborn.
> > >
> > >
> > >
> > >
> >
> > --
> > 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
> >
> >
>
>