Re: Coherent (modern) definition of RWW

On Mon, 17 May 2021 at 23:28, Kingsley Idehen <kidehen@openlinksw.com>
wrote:

> On 5/17/21 10:27 AM, Jonas Smedegaard wrote:
> > Quoting Kingsley Idehen (2021-05-17 15:39:52)
> >> 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.
> >
> >>> 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
>
> Hi Jonas,
>
>
> > As I understand it, some of the hype around blockchain is that it
> > addresses some of the above - and some the criticism is that it does not
> > address all of them (other criticism is that price is too high).
>
>
> Yes!
>
> The biggest issue is that Blockains hook into networks that aren't
> cobbled together using URIs.
>

Yes!  The web is a web of relations, or a giant graph.  I've been using the
term timestamp server, as satoshis said in the first white paper "our
solution begins with a timestamp server".  Which facilitates a chain of
blocks, which is all a block chain is.


>
> If they get round to treating URIs as core infrastructure, it will
> become much more useful than it is right now.
>

By standarizing URIs between graphs and the formats for them, we enable one
set of functionality (e.g. temporal, sync, audit, elimination of race
conditions) in another (permissioned read write spaces with identity).
This is work we could look at in this group leading a temporal read write
web


>
> As Melvin often states:
>
> Most of blockchain initiatives ultimately boil down to "buy my token"
> schemes.
>

I'm not against selling tokens, provided that you are up front and clear
that, that is what you are doing

In this group we are committed to royalty-free standards and protocols.
Far too many of these tokens are a (hidden) tax at the protocol level for
state transitions of the time stamp server.  The so-called technology is
just a tease to get you locked in to a platform where the founders charge
royalties, often by stealth

Tokens are fine, in fact we could make our own tokens to fund various
projects or work streams in this group.  The protocols themselves, or the
internet scale timestamp servers, should be in the spirit of royalty-free


>
>
> >
> > Same/similar for Holochain and IPFS.
> >
> > I dearly hope that the Safe Network succeeds and reaches critical mass,
> > as it seems to me that it addresses all of the above 5 points, with a
> > cost directly tied to the operations themselves (the Safenet equivalent
> > of bitcoin "mining" is to contribute storage or bandwidth or validation
> > to the network): https://safenetwork.tech/faq/#what-is-the-safe-network
> >
> >
> >  - Jonas
> >
>
>
> --
> 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
>
>
>