- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Wed, 19 Mar 2014 18:17:49 +0100
- To: <public-linked-json@w3.org>
- Cc: "'Jerven Bolleman'" <jerven.bolleman@isb-sib.ch>
Hi Jerven, That's great news. > This is now public, but not yet announced. One can see an example here > http://www.uniprot.org/uniprot/P77967.jsonld and a simpler one > http://www.uniprot.org/taxonomy/9606.jsonld Your context is at http://www.uniprot.org/contextjsonld (dot missing before "jsonld"?) and is served as text/html. You should serve it as application/ld+json. In general, I would suggest to avoid compact IRIs (rdfs:seeAlso) and use simple terms (seeAlso) instead. For things like rdfs:seeAlso you should also set @type to @id in order to get rid of all the @id-objects.. you would end up with a simple array of strings. On the other hand, you wouldn't need the type-coercion of booleans if you would use real booleans in the data: "up:reviewed": "true" --> "up:reviewed": true > It is very similar to our other RDF serializations, except for evidence > tagging (provenance of an annotation). In the RDF/XML & Turtle this is > done with reification and in JSON-LD with graphs. I would be interested in hearing why you made that decision. > I would be very happy if you all could have a quick look at it and let > me know if there are any bugs in it. > Then I can put it in the news and have it announced for the next > UniProt release as a public format. HTH, Markus -- Markus Lanthaler @markuslanthaler
Received on Wednesday, 19 March 2014 17:18:25 UTC