Basic Storage Context

[hzbarcea]

Collection of use cases that provide the basic functionality of an LWS storage.

• [UC] General purpose data storage #107
• [UC] Uniquely identify storage globally #108
• [UC] One-to-many relationship between owning entity and storage(s) #109
• [UC] Ability to split or aggregate storages #110
• [UC] Storage hosting #111
• [UC] Storage portability from a provider to another #112
• [UC] Basic data sharing #113
• [UC] Entity Authentication #114
• [UC] Entity globally unique identity #115
• [UC] Selective access to data #116

Many issues are quite general. This is a helper issue to provide a context. Use cases will refer to this context and will define additional expectations, so that discussions are focused those additional points.

[michielbdejong]

The one I'm missing for data portability is client identification (in addition to agent identification).

[w3cbot]

This was discussed during the #lws meeting on 27 January 2025.

View the transcript

Basic storage context (w3c/lws-ucs#117)

<gb> Issue 117 Basic Storage Context (by hzbarcea) [needs-discussion]

hadrian: we can discuss the issue on basic storage context

ericP: need clarification
… do we split the UCs into ???

laurens: iti s best to have this kind of discussion asynchronously

<laurens> w3c/lws-ucs#110

<gb> Issue 110 [UC] Ability to split or aggregate storages (by hzbarcea) [usecase] [review]

ericP: the question was about whether to splitting pods

laurens: if you haven't additional issues to discuss now, we can continue asynchronously

laurens: maybe one issue of interest is 108

w3c/lws-ucs#108

<gb> Issue 108 [UC] Uniquely identify storage globally (by hzbarcea) [usecase] [uc-identity] [review]

laurens: I'm looking for solutiosn to this

hadrian: you can have part of URL that is globally unique

laurens: we don't need to discuss solutions yet but talk in terms of requirements

laurens: will leave comments to github issues

csarven: if I look at issue 112 for instance, with linked data glasses, I don't se an issue to meet the use case. UC's Acceptance Criteria would help to determine what might be needed on an atomic level. So, e.g., moving from one provider to another and what that might entail.
… but different people will see them in different ways

hadrian: in this issue, this is about being able to move to a different storage provider

laurens: what you said csarven is related to acceptance requirements

uvdsl: could hadrian add explanation to the issues
… maybe just a few bullet points so we can understand better

laurens: we can help in clarifying the issues

hadrian: commenting on the issues help in clarifying the UC or issue
… so please respond to the Github issues

---