Open Bibliography and Open Bibliographic Data » outputs http://openbiblio.net Open Bibliographic Data Working Group of the Open Knowledge Foundation Tue, 08 May 2018 15:46:25 +0000 en-US hourly 1 http://wordpress.org/?v=4.3.1 Comparative Serialisation of RDF in JSON http://openbiblio.net/2011/05/04/comparative-serialisation-of-rdf-in-json/ http://openbiblio.net/2011/05/04/comparative-serialisation-of-rdf-in-json/#comments Wed, 04 May 2011 17:59:13 +0000 http://openbiblio.net/?p=1022 Continue reading ]]> This is a comparison of RDF-JSON and JSON-LD for serialising bibliographic RDF data. Given that we are also working
with BibServer we have taken a BibJSON document as our source data for
comparison. The objective was to both understand these two JSON
serialisations of RDF and also to look at the BibJSON profile to see how it
fits into such a framework.

Due to limitations of the display of large plain-text code snippets on the site, we have placed the actual content in this text file which you should refer to as we go along.

We used a BibJSON document, which comes from the examples on the
BibJSON homepage.

When converting this into the two RDF serialisations we invent a namespace

http://www.bibkn.org/bibjson/terms/

This namespace provisionally holds all predicates/keys that are used by BibJSON
and are not immediately clearly available in another ontology. These terms should
not under any circumstances be considered definitive or final, only indicative.

Now consider the RDF-JSON serialisation

Some key things to note about this serialisation:

  • There is no explicit shortening of URIs for predicates into CURIEs,
    all URIs are instead presented in full.
  • The subject of each predicate is a JSON object with up to 4 keys (value,
    type, datatype, lang). This means that it is not easy for the human
    eye to pick out the value of a particular predicate.
  • Of the two RDF serialisations, this is by far the most verbose
  • It is relatively difficult for a human to read and write

Compare this with the equivalent JSON-LD serialisation:

Some things to note about this serialisation:

  • It has a clear treatment of namespaces
  • It may be slightly inaccurate, as there are some parts of its specification
    which are ambiguous – feedback welcome
  • The object values cannot be taken as the value of the predicate,
    as they may contain datatype and/or language information in them, or may
    be surrounded by angled brackets.
  • It is relatively easy for a human to read and write

Both serialisations are capable of representing the same data, although JSON-LD
is far more terse and therefore easier to read and write. It is not, however,
possible to reliably treat JSON-LD as a pure list of key-value pairs in non-RDF
aware environments, as it includes RDF type and language semantics in the literal
values of objects. RDF-JSON does not suffer from this same issue within the object
literals, but in return its notation is more complex.

A serious lacking in RDF-JSON is explicit handling of CURIEs and namespaces,
and it could benefit from adopting the conventions laid out in JSON-LD – this
may bring the choice of which serialisation to use down to preference rather
than relying on any significant technical differences.

Each of the formats also comfortably represents BibJSON, and with the extensive lists of predicates provided in that specification it would be straightforward enough to do a full and proper treatment of BibJSON through one of these routes.

]]>
http://openbiblio.net/2011/05/04/comparative-serialisation-of-rdf-in-json/feed/ 1
Data Triage Notes http://openbiblio.net/2010/09/22/data-triage-notes/ http://openbiblio.net/2010/09/22/data-triage-notes/#comments Wed, 22 Sep 2010 16:10:17 +0000 http://openbiblio.net/?p=248 Continue reading ]]> I’ve begun to write up my experiences and notes on the triage of the datasets I am processing for the JISC Open Bibliography and Citation projects, in a way that others might make sense of them.

You can find the WIP writeup here: http://knowledgeforge.net/pdw/trac/wiki/datatriage

This will include links to the source datasets and any subsequent curated data as I am able to put them up online.

]]>
http://openbiblio.net/2010/09/22/data-triage-notes/feed/ 1
JISC OpenBiblography: Aims, Objectives and Final Outputs http://openbiblio.net/2010/07/15/jisc-openbiblography-aims-objectives-and-final-outputs/ http://openbiblio.net/2010/07/15/jisc-openbiblography-aims-objectives-and-final-outputs/#comments Thu, 15 Jul 2010 09:07:01 +0000 http://openbiblio.net/?p=108 Continue reading ]]> This project will publish a substantial corpus of bibliographic metadata as Linked Open Data, using existing semantic web tools, standards (RDF, SPARQL), linked data patterns and accepted Open ontologies (FoaF, Bibo, DC, etc).

The data will be from two distinct sources: traditional library catalogues (Cambridge University Library and the British Library) and ToCs from a scientific publisher, the IUCr. None of the material is currently available as LOD, furthermore the outputs can be guaranteed to be open (unlike many existing data efforts, linked or otherwise).

Key strategies are

  • transformation of current publishers’ model to create Open Bibliography as part of their future business, and
  • the immediate and continuing engagement of the scholarly community.

Deliverables include a maintained and growing bibliography on the IUCr site and engagements with other like-minded publishers such as PLoS as well as the code for theĀ  software used to create the Linked Data versions of the aforementioned sources.

]]>
http://openbiblio.net/2010/07/15/jisc-openbiblography-aims-objectives-and-final-outputs/feed/ 1