Re: Quick Question on FWPD

On 09/05/2025 11:34, Melvin Carvalho wrote:
>
>
> st 19. 3. 2025 v 9:40 odesílatel Pierre-Antoine Champin 
> <pierre-antoine@w3.org> napsal:
>
>
>     On 19/03/2025 08:56, Melvin Carvalho wrote:
>>
>>
>>     st 19. 3. 2025 v 8:49 odesílatel Pierre-Antoine Champin
>>     <pierre-antoine@w3.org> napsal:
>>
>>         Hi Melvin, Wonsuk,
>>
>>         time flies, doesn'it! 😅
>>
>>         The answer is simply that we are a little late on out
>>         charter: we are still focusing on the Use Case documents, and
>>         have not published any draft for the specification itself.
>>         You haven't missed anything :)
>>
>>         For future reference: all publications of the WG (including
>>         drafts) will be listed here:
>>         https://www.w3.org/groups/wg/lws/publications/
>>         and this list is maintained automatically, so you can rely on
>>         it being up-to-date.
>>
>>
>>     Thanks, Pierre.
>>
>>     Would you be able to share a sentence or two on what it might
>>     look like?
>
>     The group has not discussed any specifics yet, so I'd rather not
>     make any prediction, sorry.
>
>
> Just noticed we’re a third of the way through the WG—any thoughts on 
> when a FPWD might land?
I'm afraid not.
>
> The use case doc is rich (maybe too rich!). In the Social WG we picked 
> a smaller slice to start with, which helped keep momentum. Could that 
> work here too?
It is the picking a smaller slice that we are still working on.
>
> Would be lovely to have something public before the halfway mark. 
> Helps those of us building stuff align a bit.

It would :) Working on it, but can't make any promise.

   pa

>
> Cheers,
> Melvin
>
>>
>>     I don’t expect you to be held to anything, but I’d really
>>     appreciate getting a sense of the direction it’s heading in. As
>>     an app developer, this would help me future-proof my implementations.
>>
>>     I’m familiar with Solid, remotestorage, and unhosted apps, though
>>     I know less about the Fedora side of things.
>>
>>     In short, what abstractions or generalizations should a Solid app
>>     developer anticipate when working with LWS?
>>
>>     If I had to guess, it would be designed for client-side
>>     (unhosted) apps, supporting a range of identity and
>>     authentication systems (including but not limited to WebID),
>>     multiple data formats (including RDF, and possibly JSON?), and a
>>     set of access control plugins.
>>
>>     Obviously, the FPWD will clarify things, but even a rough sense
>>     of direction—whether subjective or opinionated (with the usual
>>     disclaimers)—would be very helpful for those of us following from
>>     a distance.
>>
>>     Best,
>>     Melvin
>>
>>           best
>>
>>         On 18/03/2025 02:46, 이원석 wrote:
>>>         Hi. Melvin and all.
>>>         Thanks to Melvin to raise this issue. I also have same
>>>         question for the group.
>>>         I hope to be prepared the base document for this work.
>>>         Thanks!
>>>
>>>         Kind regards,
>>>         Wonsuk.
>>>
>>>
>>>         -----Original Message-----
>>>         From: "Melvin Carvalho" <melvincarvalho@gmail.com>
>>>         <mailto:melvincarvalho@gmail.com>
>>>         To: <public-lws-wg@w3.org> <mailto:public-lws-wg@w3.org>;
>>>         Cc:
>>>         Sent: 2025-03-18 (화) 09:13:13 (UTC+09:00)
>>>         Subject: Quick Question on FWPD
>>>
>>>         Hi All,
>>>
>>>         I saw in the Linked Web Storage Charter that the FWPD was
>>>         expected around March 11, 2025. Just wondering—has it been
>>>         published yet, or has the timeline shifted?
>>>
>>>         If it's not ready yet, is there an overview available that
>>>         explains how the different storage approaches fit together
>>>         under one umbrella? As an app developer, I'd love to align
>>>         my work with the direction this group is taking, and a bit
>>>         of guidance would be really helpful.
>>>
>>>         Appreciate any insights!
>>>
>>>         Thanks,
>>>         Melvin
>>>