Re: Note on RWW Group's Evolution and Principles

I have been lurking here feeling nostalgic about RWW, but not sure what to
do. I've been overwhelmed by the pressure to "make money", and everything I
do seems like a hobby because it is not done the right way. If I don't go
to school or take a well-understood job am I just goofing off? Surely there
is a way to do this.

I've been spending a bit of time with the FISSION.codes community this
year. They are working on decentralized compute with IPVM and decentralized
auth with UCANs.  I was also at the Internet Identity Workshop where I met
Arthur Brock from HoloChain that can be used for decentralized apps and saw
Daniel Buchner again who is working with TBD on decentralized web nodes (if
that is the name).

-Brent Shambaugh

GitHub: https://github.com/bshambaugh
Website: http://bshambaugh.org/
LinkedIN: https://www.linkedin.com/in/brent-shambaugh-9b91259
Skype: brent.shambaugh
Twitter: https://twitter.com/Brent_Shambaugh
WebID: http://bshambaugh.org/foaf.rdf#me


On Mon, Oct 30, 2023 at 12:47 AM Melvin Carvalho <melvincarvalho@gmail.com>
wrote:

> There wasnt much of a response to creating a Note about RWW Principles,
> and the group will go dormant in a few weeks, so I dont think we'll get
> time to do that.
>
> However, I put down a stub of some RWW principles in the wiki, feel free
> to edit it in the last weeks if you feel like it:
>
> https://www.w3.org/community/rww/wiki/Principles
>
> We also have the old github area in case anyone wants to pick up some
> ideas that have been explored over the years.
>
> https://github.com/rwwcg
>
> Best wishes
> Melvin
>
> po 2. 10. 2023 v 16:38 odesílatel Melvin Carvalho <
> melvincarvalho@gmail.com> napsal:
>
>> Hello Everyone,
>>
>> The RWW group embarked on its journey in 2011 with the vision of
>> utilizing standards to facilitate reading and writing on the web. Over the
>> years, we have delved into numerous ideas emanating from this foundational
>> principle. Several of these ideas have transitioned into new
>> standardizations like web acl, solid, patch updates, content addressable
>> identifier, among others.
>>
>> While the group has transitioned into a phase of reduced activity, it now
>> faces the prospect of closure. It's possible that the appetite for
>> embarking on new endeavors might be modest at this juncture, yet I
>> encourage anyone with fresh ideas to bring them forth.
>>
>> One aspect we haven't formally addressed is compiling a note that
>> encapsulates how all the pieces interconnect and narrates the group's
>> evolutionary journey. This includes the initial exploration of RESTful
>> reading and writing utilizing GET, POST, PUT, PATCH, and the subsequent
>> need for spam protection through access control. This pathway naturally led
>> us towards a standards-based identity system, and then ACLs, potentially
>> integrating roles and groups, tackling hierarchical dilemmas (such as
>> writing permissions to a sub-directory), authentication, login procedures,
>> and understanding HTTP response codes around 2xx and 4xx, along with
>> higher-level architectural principles.
>>
>> It might be enriching to collectively work on such a note. This endeavor
>> could serve multiple purposes - preserving the historical essence of the
>> group, aiding systems like Solid in understanding the guiding principles
>> that shaped their inception, and envisaging a future where new
>> specifications evolve from a well-articulated set of guiding principles.
>> This documentation could potentially enable future innovators to request
>> specifications based on Read Write Web Principles for specific use cases.
>>
>> I would be happy to hear thoughts on this idea.
>>
>> Best,
>>
>> Melvin
>>
>