- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Tue, 18 May 2021 00:46:44 +0200
- To: Kingsley Idehen <kidehen@openlinksw.com>
- Cc: public-rww <public-rww@w3.org>
- Message-ID: <CAKaEYh+3_DgrCJ+cJX+jfpHjqFDkVz+Nbjp51z+Qn_VMV0K3uw@mail.gmail.com>
On Mon, 17 May 2021 at 15:40, 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. > So this group is almost 10 years old, and at the start there was some back and forth about defining RWW We came I think to a clear and simple definition which was: "Using standards to read and write to the web" So LDP is a valid candidate, tho not the only candidate. I believe timbl has said somwhere its an attempt to webize the file system, or perhaps to rdf-ize it Something like WebDAV is a perfectly good standard for reading and writing. Limited in many ways, but can be useful. There's more, perhaps we should collect them in the wiki. Just to note that the file: space is also part of the web, so writing to a file is an important action, especially from the browser Kingsley's breakdown of indenity / identifiers / authn / authz / storage imo is a great way to break it down. The other thing I like is what Kingsley describes as the EAV model for declarative data. But I think we are still missing time in the equation. By time I dont mean really versioning, tho that's part of it. I mean more of state that can change in time, robustly and resiliently. The RWW is still IMHO an unfinished project, in that it does sort-of-useful things, but the use cases are not to date hugely compelling. My feeling lately is that the ephemeral nature of the web is one reason for this and underdeveloped standards, so it's perhaps a gap we can close, if people want to work on such a thing ... > > The Web is simply a document network constructed from hyperlinks > (specifically HTTP URIs) that denote: > > 1. Entities of type Document > 1. Identity > 2. Identification > 3. Authentication > 4. Authorization > 5. Storage > 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 > > >
Received on Monday, 17 May 2021 22:47:34 UTC