Iddan Aaronsohn
Iddan Aaronsohn
I think that once #24 would be resolved it'll be easier to implement using generic functions
I highly suggest Gatsby - it's been a blast to develop with it
It could have been great if @sargunv 's solution was part of the `ObjectDefinitionBlock` (`t`) API.
This behavior is weird. As far as I understand the API anything that can be compacted to a list representation should be compacted to a list representation. Maybe this fix...
Doesn't look good in JSON-LD Playground
Still looks wrong: ``` { "@graph": [ { "@id": "_:b5", "http://www.w3.org/1999/02/22-rdf-syntax-ns#first": "42", "http://www.w3.org/1999/02/22-rdf-syntax-ns#rest": { "@id": "_:b6" } }, { "@id": "_:b6", "http://www.w3.org/1999/02/22-rdf-syntax-ns#first": "43", "http://www.w3.org/1999/02/22-rdf-syntax-ns#rest": { "@list": [ "41" ] }...
What are the configurations you are using?
Cool. So is this the standard behaviour? If I get a JSON-LD document from a server and call `compact()` I'll get a list instead of `rdf:first` and `rdf:rest`? Why does...
So I'll refine my suggestion: I believe compact **should** do that. If I get RDF style list it should be normalized to a regular list.
Is there another way to communicate about list items with multiple documents that is supported JSON-LD? My goal is to be able to emit list items as separate documents.