[openbiblio-dev] Tutorial on BibJSON

Karen Coyle kcoyle at kcoyle.net
Sat Dec 17 14:04:45 UTC 2011

I'm not exactly sure what it means to say that "some values are  
objects", but apart from that it might be good to describe these tiers  
in terms of functionality. The key/value pairs model works primarily  
in a closed system where all keys will be taken from the same schema.  
This model isn't extensible except as an addition to the base schema,  
which affects everyone using it. the advantage is that this uses very  
simple JSON, so the programs using it are ver simple. Using namespaces  
means that your data can mix in with data from other sources, and that  
someone creating data can add any key from any namespace that they  
need for their purposes. This makes the data integratable with other  
data and programs. It also means that you can grab data from someone  
using BIBO or DC directly, no translation required. The namespace form  
appears to complicate JSON somewhat, however, as I understand it.

Of course, none of this dictates what a user would see in a simple  
user interface - either for inputting data or displaying it. All of  
this key and/or namespace business can be hidden from them.


Quoting Mark MacGillivray <mark at odaesa.com>:

> hi peter,
> Jim and I have been discussing this a bit, and we are thinking there
> may be value in having a sort-of tier approach to bibjson.
> First tier would be - key/value pairs in JSON (as per
> http://bibserver.okfn.org/bibjson/overview)
> Second tier would be - some values are objects (such as author, journal)
> Third tier would be - using namespaces e.g. dc:contributor as keys
> However I do not think these tiers should be hierarchical - e.g.
> having namespaces is not necessarily "better" than not - it is just
> another example of how you might convey some information to others.
> The latest bibjson spec is at:
> http://bibserver.okfn.org/bibjson/specs/v0-82/
> On Sat, Dec 17, 2011 at 12:39 PM, Peter Murray-Rust <pm286 at cam.ac.uk> wrote:
>> I [*] would like to make a very simple video tutorial on BibJSON using
>> simple examples.
>> I'm looking a http://bibserver.okfn.org/bibjson/ and have found
>> http://bibserver.okfn.org/bibsoup/example/ but that has a link that points
>> recursively to itself.
>> Question - does the link need to point somewhere else. And is there a valid
>> entry at the end?
>> Then there is:
>> http://bibserver.okfn.org/bibjson/overview/
>> which has an example:
>>  {
>>     "citekey":"some identifier, unique in this collection",
>>     "type": "book",
>>     "title":"some title",
>>     "author": ["Mark MacGillivray","Jim Pitman"],
>>     "journal": "journal_name",
>>     "collection": "collection_name",
>>     "moreinfo":"some more information about this collection",
>>     "ns1:thing":"some thing",
>>     ...
>>   }
>> Question: do the names need namespacing? - currently only the bottom one is
>> namespaced. Is there an easy place to find common names?
>> There is also http://bibserver.okfn.org/bibjson/specs/v0-81/example/ which
>> seems consistent with the above
>> P.
>> [*] actually Professor OWL and otehrs in Animal Garden
>> --
>> Peter Murray-Rust
>> Reader in Molecular Informatics
>> Unilever Centre, Dep. Of Chemistry
>> University of Cambridge
>> CB2 1EW, UK
>> +44-1223-763069
>> _______________________________________________
>> openbiblio-dev mailing list
>> openbiblio-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/openbiblio-dev
> _______________________________________________
> openbiblio-dev mailing list
> openbiblio-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/openbiblio-dev

Karen Coyle
kcoyle at kcoyle.net http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet

More information about the openbiblio-dev mailing list