Re: UniProt RDF as JSON-LD please test and give feedback,

Jerven:
I putter around on the JSON-LD playground: I was just looking for some
"big" examples. These look very rich, thanks! Also it's great that you've
already set up the CORS headers for the content and context so that we can
tinker with your stuff easily.

Here's the smaller one, 9606, in the playground, with some of Markus'
suggestions shown as a secondary context:
http://tinyurl.com/nurherz

I notice that with the P77967 example, at line 1572, where you start to
define the annotations, you begin repeating "@id" and "@graph" attributes
in the root object.  I assume that each of these annotation pairs is
supposed to be wrapped in {}, pointing to the subgraphs you were talking
about.

I tried that out, and it looks good, but I can't post a link here, as the
web server won't accept it.

Thanks again!


On Wed, Mar 19, 2014 at 1:17 PM, Markus Lanthaler
<markus.lanthaler@gmx.net>wrote:

> 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
>
>
>