Use case gathering?

[lrosenthol]

I have seen a number of possible use cases expressed in various repos, email threads, etc.

Given that we could use these to help us gather the specific set of requirements that any new specification/standard needs to support - perhaps we should start here.

[gkellogg]

This is a nice document summarizing some use cases and different formats: https://clue.engineering/2018/introducing-reactphp-ndjson.

[gkellogg]

Things that were raised in the meeting today:

• A stream can either be a single complete resource which can be processed entirely at a single go or an open stream in which new documents may be sent over time, such as a WebSocket.
• A stream may be used to convey components of a single dataset, which are too large to convey in a single document (SOLID Resource Containers were mentioned by @pchampin) or to collect otherwise unrelated documents.
• There could be a way to share a context across all documents in a stream, or require every document within the stream to be self-describing. JSON-LD allows an expansionContext to be set in the API, and in most cases via HTTP Link header.