Re: Reviewing the Solid protocol

Thanks Melvin, I think you identified what I felt wrong about it at gut
level.

It's there as a package. Not, delivered as hey (hat-tip to Tim Bray),
here's a format, there's a protocol, over there an auth thing, here's one
example of 1000 use cases., do your own thing...

That might just be marketing, fine. I guess Android worked.

Suppose I am still digesting (and still haven't got it behaving on Apache).









On Mon, 20 Mar 2023 at 18:52, Tim Bray <tbray@textuality.com> wrote:

> At one point back in mid-2020 I tried to look seriously at Solid and just
> couldn't figure out "what is this and what does it do?" quickly enough, ran
> out of patience, and turned my attention elsewhere. Are things better now?
> I.e. is there a good intro that gets to the heart of the matter quickly?
>
> On Mon, Mar 20, 2023 at 10:45 AM Melvin Carvalho <melvincarvalho@gmail.com>
> wrote:
>
>>
>>
>> st 15. 3. 2023 v 4:32 odesílatel Danny Ayers <danny.ayers@gmail.com>
>> napsal:
>>
>>> It is in scope for TAG, the W3C and whatever. But the idea your version
>>> is the one. If you want to keep the W3C relatively independent, that
>>> doesn't work. If Microsoft and Apple have to drop their version of scripts,
>>> so should you.
>>>
>>
>> It's still about bringing the web to its full potential.  Solid is a
>> pretty good effort in that direction IMHO
>>
>> What does it do?
>>
>> - Adds a social element (started with FOAF)
>> - Adds authentication
>> - Adds persistent storage, towards a read write web
>> - Adds human and machine readable data
>> - Adds realtime updates
>> - Friendly to humans and agents
>>
>> What are the limitations:
>>
>> - Still a bit buggy
>> - Some UX issues
>> - Largely (but not soley) based on turtle, which is a small part of the
>> web
>> - Not 100% backwards compatible e.g. requires conneg and few on the web
>> do that
>> - Steep learning curve for new developers
>> - Lacks plain old JSON interop (personal observation)
>>
>> Not the only way of doing things, but definitely something interesting /
>> creative / innovative.  It also lends itself well to interoperability,
>> together with future and past innovations.
>>
>>
>>>
>>> On Sun, 24 Jul 2022 at 15:18, Tim Berners-Lee <timbl@w3.org> wrote:
>>>
>>>> Solid is a growing protocol/movement, and the tech parts of it — the
>>>> Solid Project — are basically a W3C Community group.
>>>>
>>>> Solid adds things which the web needed but hadn’t yet standardized,
>>>> including global single sign-in, standard access control, and a fast API
>>>> for data read-write between an app and a store (a Solid Pod).  By making
>>>> the API to the store universal, it means you don’t have to change the store
>>>> when you make a new app, which completely changes the architecture and
>>>> markets and business models which are possible. It also leaves individuals
>>>> empowered rather than exploited.
>>>>
>>>> Would it be reasonable for the TAG to review the architecture at a high
>>>> level, or review the protocol?  It would be useful to get a knowledge of
>>>> the Solid stack in neighboring parts of the technology.
>>>>
>>>> (A separate future question are the client-client interop specs which
>>>> are needed for interop between apps, such as contacts, chat, etc.)
>>>>
>>>> See https://solidproject.org/. https://solidproject.org/TR is where
>>>> the specs end up after their github-based proces.
>>>>
>>>> Best wishes
>>>>
>>>> Tim BL
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>> ----
>>>
>>> https://hyperdata.it <http://hyperdata.it/danja>
>>>
>>>

-- 
----

https://hyperdata.it <http://hyperdata.it/danja>