– DRAFT –
Linked Web Storage

acoburn: agenda first point: introductions

Introductions and announcements

acoburn: anyone new that wants to introduce themselves?

Approving previous minutes

acoburn: next item: approving previous minutes

acoburn: we decided to approve minutes after a week if no objections, so: any objections?

<pchampin> FTR https://www.w3.org/2024/11/11-lws-minutes.html

acoburn: if no objections, we can move to the next item

Pending action items

acoburn: 3rd item: pending action items

acoburn: now we have a use case template in place

acoburn: we wanted to reach out to a couple of (TPAC) people to review the template

acoburn: that's progressing

acoburn: one of the issues is that there are a lot of places where the use cases are

<acoburn> TPAC use cases

acoburn: we want to move them all to a single location

acoburn: TPAC use cases are at https://docs.google.com/document/d/1sFZ0BozoLA3U7iROtu10tR7S05_OEOprS8Um9NZqZYw/edit?tab=t.0#heading=h.dzhfksak68xg

<acoburn> Use cases submissions (so far)

acoburn: the use case submissions are put in https://github.com/w3c/lws-ucs/issues

acoburn: there might be other locations, people talked about them, those are all fair game

timbl: do we have a homepage?

acoburn: I could suggest that we go into the next agenda item and really talk about the use cases

timbl: if it's eventually on the Web it should be fine, eg a homepage where we keep the use cases

acoburn: the goal of the end state is that all of the use cases are in a single document or in a set of documents

acoburn: easy to find, catalogued

acoburn: we'll use that list to organize and prioritize the working group

timbl: anyone coming into this working group should be able to find out what we're working on

timbl: as long as it's eventually on the Web

<pchampin> https://www.w3.org/groups/wg/lws/

pchampin: to respond to that: the working group home page is the W3C generated home page

pchampin: there's a menu with list of publications (currently empty), where we'll add the publication once it's ready

pchampin: also the repo is added, but the name probably isn't really clear (lws-ucs)

ACTION: pchampin to add links to the protocol and use-case repos in the summary on the WG's homepage

pchampin: action for me is the move the summary to the WG's homepage

acoburn: next topic: status of use cases

Use cases status

acoburn: hadrian, could you give a status?

hadrian: there was confusion with use cases vs user stories

hadrian: there is a new use case by csarven

hadrian: last week I was sick, this week I want to clean up a bit more

acoburn: any questions about where things stand on the use cases or the process to submit use cases?

acoburn: (no questions) OK, so as a reminder: we do really want use cases to come in

acoburn: anyone having use cases via your work or organizations: those things would give us a much stronger document and foundation to create the requirements

acoburn: and will eventually create a better protocol

acoburn: maybe we should discuss a timeframe for the use cases

<BenDM> +1

acoburn: we want to have a comprehensive list of use cases. That will take time, but we also want to get started with other things

acoburn: a suggestion for a possible timeframe for use cases: by the end of the year?

pchampin: for this kind of deadline: would you not accept any more new use cases in the new year, or would you still be open to accept new ones?

acoburn: I'd suggest: we continue to support use cases, but starting January 1, we'll start prioritizing use cases and work with them

acoburn: new use cases might have a higher bar to be prioritized, but we'd still be accepting them

BenDM: by the chosen deadline, do we aim to have a list of issues, or already a document that we can share?
… If people see some kind of finished document, this can give them ideas about more use-cases to add.

hadrian: I don't think we need a grace period, we don't start from scratch

hadrian: I don't think there'll come many surprises

hadrian: I think having a document is good way to have people start thinking

hadrian: I think we can have a first version of the document by the end of the year, and we can enrich

csarven: I think we should have sufficient announcements to enter use cases, also outside the working group

csarven: there's also the holidays, but I'm not objecting the the timeframe

csarven: the question is whether the use cases are being proposed as arbitrary use cases, to be within the scope of the group

csarven: or whether those use case will be also implemented by the proposers

csarven: so whether it's more hypothetical, or whether the proposers will also provide implementations

csarven: I'm less concerned about the specific, but more about taking a good sample, sufficiently backed

<ericP> I believe the request is to have a way for WG members and maybe the public at large to be able to view the proposed use cases before the (loose) deadline

<ericP> That list *could* be curated (e.g. de-duplicated, normalized)

pchampin: about the publication of the use case document as a Note: we can release early, release often

pchampin: it's common practice to set up an initial empty document, and have new releases every time something is pushed

pchampin: I wouldn't be afraid to publish often, perhaps unfinished, I expect people to prefer that, compared to (only) publishing something polished

hadrian: I agree with that process, I'll reach out to you and Aaron for the actual process tooling

hadrian: I agree with csarven's comment that we should announce the request for use cases broadly

hadrian: also, we should start gathering the requirements starting from January, that's the most important part

acoburn: next step: start broadcasting more aggressively the request for use cases

acoburn: for example: message to the public mailing list, if someone wants to do that, there welcome to, otherwise I'll do that

acoburn: (no takers) I'll do that

acoburn: hadrian, if you could send a message to the ??? group, that would be great

hadrian: will do

acoburn: are there other channels?

jacoscaz: there's communication happening on gitter

acoburn: could you reach out on the folks on gitter?

jacoscaz: yeah, I'll do that

ACTION: acoburn to reach out on LWS mailing list

ACTION: jacoscaz to reach out on Solid-related chat rooms on Gitter

BenDM: is there a limitation on where to reach about the use-cases? I could send it to people in Flanders.

acoburn: I don't think so, broadly speaking.

hadrian: with respect to reaching out, on the side of reaching broader: I was invited to the CCG in January, the W3C groups, and not only the ones we know that are interested in our work

hadrian: so I will reach out to the credentials group

<pchampin> https://www.w3.org/2024/09/linked-web-storage-wg-charter.html#coordination

hadrian: (before the end of the year)

pchampin: we have a (long) list of relevant W3C groups to coordinate with

acoburn: any other questions or topics related to the use cases document?

acoburn: any other questions or topics, not related to the use cases?

acoburn: then, we are done a bit early, any objections to ending early?

acoburn: thanks all!