W3C home > Mailing lists > Public > public-rdf-wg@w3.org > August 2012

Re: JSON-LD terminology

From: Andy Seaborne <andy.seaborne@epimorphics.com>
Date: Thu, 30 Aug 2012 18:58:13 +0100
Message-ID: <503FA9B5.7070902@epimorphics.com>
To: public-rdf-wg@w3.org
Richard's first comment included:
> I think that this discussion belongs onto the WG mailing list and
> shouldn't just be buried in the issue tracker, so I'm posting the
> message here too.


I received offlist email:

On 30/08/12 18:32, Markus Lanthaler wrote:
> I've created a timestamped editor's draft for the syntax and the
 > API spec at
 > @cygri <https://github.com/cygri>, @afs <https://github.com/afs> does
 > this address all the concerns you raised as part of this issue so
 > that I can close it?
 > Reply to this email directly or view it on GitHub
 > <https://github.com/json-ld/json-ld.org/issues/47#issuecomment-8167501>.

What are the changes within these two document that are relevant to this 
discussion? (And why does it now span two documents?)  I'm not sure what 
you're asking me about - checking two large docs isn't viable.

I do see (ISSUE 47 note):

Note that this definition is provisional, and may be reverted to 
something closer to the original depending on community feedback.

so nothing has actually been decided yet?


JSON-LD allows properties to be BNodes, while RDF does not. When used as 
just JSON-LD, this is not unreasonable; it only becomes an issue (and 
could raise an exception) when transformed to RDF.

but also:
An edge must be labeled with an absolute IRI, within the JSON-LD syntax, 
this label is called a property.

I like the note spelling out that linked data does not have to be 
JSON-LD.  Are notes going to be in the final document?

Received on Thursday, 30 August 2012 17:58:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:04:20 UTC