– DRAFT –
Linked Web Storage

introductions

jacoscaz: I'm Jacopo Scazzosi. Here as IE. Some of you may know me from WebID CG. I was the last chair before closing. I'm working on quadstore. Also some dependencies on Comunica. Here interested in what's going on, and specifically how this would apply in IoT, and how Solid would apply there. Where I've been focusing on 5-6 years. Based in Milan.

announcements

ericP: noting no updates from the room

Minutes process

ericP: Ideally we have a scribe list and we rotate.
… There is protocol ( https://www.w3.org/2001/12/zakim-irc-bot.html )

<TallTed> w3c scribing documentation -- https://w3c.github.io/scribe2/scribedoc.html

ericP: {summarises common Zakim commands and interactions}

<ericP> IRC conventions

ericP: {scribes help to capture discussions, records actions and decisions}

<ericP> proposed: create a list of WG participants and rotate through the list to select the weekly scribe

<AZ> +1

<acoburn> +1

<jucanbe> +1

<hadrian> +1

<TallTed> +1

<eBremer> +1

<jeswr> +1

<csarven> +1

<jacoscaz> +1

<ryey> +1

RESOLUTION: create a list of WG participants and rotate through the list to select the weekly scribe

ACTION: acoburn to create scribe list

Use Cases Document

acoburn: {summarises queuing to speak}

TallTed: {adds to queue actions}

<ericP> next

TallTed: re PROPOSAL/RESOLUTION should have exactly the same text. If ACTIONS are emotes, they don't go into minutes. ???

<ericP> ack

<ericP> next

<Zakim> ericP, you wanted to say that it's important to say "to say"

ericP: W3C Process ??? every WG has a charter. Loosely identifies the objectives of the group. During the process of the specifciations, the WG clarifies the Success Criteria. Those closely line up with successful implementations.
… We'll write a test suite and probably test tooling that will verify ??? following tests correctly.
… That describes the specification and testing.
… But for principle decisions we start with Use Case documents
… For each Use Case (UC) there is a high level business case.
… Then technical analysis
… Typically at some point someone will group them into Requirements.
… So our job initially to write high level UCs and to create a recipe for what our Success Criteria are.
… This process will involve things perhaps too much. We can include things in the UC but we can reject because a bridge too far, or not a minimal viable product.
… So, simply writing something in the UC doesn't it has to be addressed
… We'll pick a couple of editors, and act as "coders" taking PRs or emails from proposals and sort of organise it to the conventions that are elsewhere in the document.

<TallTed> managing the queue is covered here -- https://www.w3.org/2001/12/zakim-irc-bot.html -- and `ack next` does what ericP wanted earlier

<ericP> csarven: two minor points:

<ericP> ... 1. [bookkeeping] we need to document what use cases we accept

<ericP> ... 2. we need to document which use cases we decided NOT to address and why, e.g. no one willing to implement)

ericP: Do we want to UC documents in the same repo?

acoburn: We have two repos. One for the protocol and the other for the UC document.

<acoburn> LWS Use Cases repository

ericP: There is one person volunteering to editor of UC?

acoburn: We're finalising that list now. Some UCs are coming in.

ericP: We'll send links out to the mailing list out when that initial document is created?

acoburn: Only after we collect the UCs and triage.
… Right now the process is that the UCs are submitted as issues.
… There is a PR for the UC template.
… Once that is merged, I think the UC submissions can follow a standard format

<TallTed> LWS Protocol repository

ericP: Anyone have documents that we should look at for UCs? e.g., slide 63 for Ted talk

<Zakim> acoburn, you wanted to say there were use cases from TPAC

acoburn: We had a meeting at TPAC2024 and there were some UCs proposed then. Just a reminder that those UCs will be submitted to this process.

minutes of TPAC 2024 Breakout Session: "Breaking Silos: A Collaborative Discussion on Use Cases for Linked Web Storage"

ACTION: acoburn to look for use cases recorded at the TPAC breakout section

ack

<ericP> csarven: will someone take an action to translate the use cases mentioned during the meeting to a format using the template?

csarven: Can you clarify whether someone will create the UCs from the TPAC meeting or we should do it?

acoburn: Now that we have a UC template, we can formulate them in a way that works for the TPAC UCs.

acoburn: We talked about among the chairs re meeting cadence.

Meeting Cadence

acoburn: Some context: in the WG charter, it says this group will meet every two weeks.
… I know we have two years and a lot of material to cover.
… It may be too infrequent.
… I'd like to propose that we meet weekly.

<acoburn> Proposed: The lws working group will meet weekly rather than every other week.

acoburn: Open discussion first or propose?

ericP: Propose is fine.

<ericP> +1

<timbl> +1

<jeswr> +1

<AZ> +1 for the reasons mentioned by Aaron, although it will make it difficult for me to attend each time

<eBremer> +1

csarven: +1 (provided there is some consideration on different days / timezones to consider)

<hadrian> +1

<acoburn> +1

<ryey> 0

<jacoscaz> +1

<jucanbe> +1

<ericP> csarven: some folks weren't able to meet during the last meeting and won't be able to in the future

<TallTed> +1

<ericP> csarven: if we have task forces or other minuted meetings, we might need different times

<Zakim> ericP, you wanted to give a history of variable meeting times

ericP: Some groups have tried rotating meeting times and have typically fallen back to just having a regular consistent time. The chaos meant less people showed. That may be not be the case but just saying. Re TF, they can certainly meet at their own times.
… If somebody can't make it they might be able to make it every other week.

<Zakim> timbl, you wanted to discuss timezones

timbl: Even having every other week means people forget or miss meeting. Every weeks is acceptable. Rotating has some probs.

<Zakim> TallTed, you wanted to suggest alternating meeting time

TallTed: Being involved in different groups, working with folks doing all of the above.
… Alternating times so people in Asia can meet.
… I strongly suggest using the W3C calendar. Subscribe to it. You'll at least see it and can send regrets or know the right time. That works most reliably.

<timbl> agree use the calendar.

<ericP> PROPOSED: next meeting in 1 week. will address future scheduling at that meeting

<acoburn> +1

<hadrian> +1

<TallTed> +1

<eBremer> +1

<timbl> +1

<AZ> +1

<jeswr> +1

<ryey> +1

<jacoscaz> +1