- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Fri, 3 May 2013 10:28:55 +0200
- To: "'Robert Sanderson'" <azaroth42@gmail.com>, <public-linked-json@w3.org>
Hi Robert,
I just realized that you haven't got any response yet. Sorry about that.
> In two projects* I've run into a pattern which is perhaps a common
> issue that could benefit from being more broadly discussed.
>
> If there is an rdf:List resource that has identity of its own, perhaps
> with other statements about it, then it seems like rdf:first and
> rdf:rest need to be instantiated directly within the JSON rather
> simply as a JSON list.
That's correct.
> [...]
>
> Which pushes some of the RDF model in the face of the JSON developer
> that would be nice to avoid. Thus the question is whether something
> like:
>
> {
> "@id":"foo:mySequence",
> "@new-list-keyword-here": ["x:resource1", "x:resource2", ...]
> }
>
> might be more convenient? Unless I've just missed something like this
> in the documentation?
No, you are right. That isn't supported at the moment. I thought about
exactly the same more than a year ago:
https://github.com/json-ld/json-ld.org/issues/75
at that time we concluded that it is not a compelling enough use case and
would complicate the algorithms substantially. So summed up, this is not
something that will be supported in JSON-LD 1.0.
Cheers,
Markus
--
Markus Lanthaler
@markuslanthaler
Received on Friday, 3 May 2013 08:29:32 UTC