As a advanced user,
I want to access and browse my LWS storage in a knowledge-graph-like style,
So that I can take advantage of the Linked Data nature of resources.

Preconditions:

What conditions must be in place or assumed before this use case can begin?

Trigger:

What (user or system) event or action initiates this use case?

Actors:

Describe the primary actor, and any other relevant actors involved in this use case

Distinction:

What unique challenges or distinguishing factors (like technical issues, user experience needs, workflow integration, etc.) are associated with this use case?

Contrary to a simple filesystem-like way (#97), knowledge-graph style requires additional considerations:

• How does it play with container and resource structure? In particular, what if a graph I have is huge but I do not like or cannot represent it as the container-resource style?
• How about SPARQL (or other query languages, if any)?

Scenario:

Describe an ideal or happy-case scenario where this use case would play out as intended.

• User can store arbitrary knowledge graph data directly into LWS, and fetch it back, efficiently
• User can fetch a partition of the stored knowledge graph data
• SPARQL is supported as well

Alternative case(s):

What alternative flows or variations should the system handle for this use case?

Subset of SPARQL is supported, or not supported at all.

Error scenario:

What unexpected issues or errors might arise, and how should the system handle them?

Acceptance Criteria:

What conditions or criteria must be met for this use case to be considered successfully handled? What limitations are acceptable?

References:

List any relevant resources or examples that could inform this use case, possibly from other domains or solutions.