JSON-LD streaming document still mandating buffering the full file

[Tpt]

JSON-LD content often use the layout following layout

{
   "@context": {...},
   "@graph": [...]
}

where @graph content should be in the default graph whereas in

{
   "@context": {...},
   "@graph": [...],
   "foo": "bar"
}

@graph content is in the named graph.

If I understand properly the JSON-LD streaming document, the parser have to buffer the full file to check if there is no @id or other key at the end of the file (in my example foo).

Am I correct in this interpretation?. If yes would it be worth it to make a new version of the JSON-LD streaming document that would mandate that the @graph key is always the last?

[rubensworks]

Hmm, we didn't consider this case indeed.
Adding @graph as 4th element in the required key ordering seems like a good approach to me.

I'm not actively following the JSON-LD WG at the moment, but I believe the specs are open to changes like this atm to sync with the RDF-star WG, or they should open up soon.

[gkellogg]

I believe that with the current charter, we can publish updates to Notes, such as this.