[openbiblio-dev] Feedback on my BibJSON record

Mark MacGillivray mark at cottagelabs.com
Sat Feb 23 15:40:37 UTC 2013


On Sat, Feb 23, 2013 at 3:26 PM, Karen Coyle <kcoyle at kcoyle.net> wrote:

> Mark, none of this is a motivation to not include a list of the terms in
> use. In fact, I know that Jim Pittman had such a list. For anyone starting
> to use bibjson, it is helpful to see such a list, not just a few very short
> examples. I find the example page woefully inadequate as the sole
> documentation.
>

A list of the terms in use can be added, anyone who wishes to supply such a
list with examples of where they are being used should do so. I did not
mean to suggest this could not be done.

As I mentioned I am currently using "citation" quite a lot in another
project, so was going to suggest adding that to the bibjson.org page as a
useful key under which to list citations. That project is not at the stage
of releasing anything where such usage can actually be seen, though, so I
had not done so yet. However, now that I have brought it up, I propose
adding "citation" to the examples.

Or is the idea of proposing additions too onerous? Would people prefer we
just stick anything onto the web page when asked, without proposal or
linking to evidence of use?

Mark





>
> kc
>
>
> On 2/23/13 7:01 AM, Mark MacGillivray wrote:
>
>> In answer to a number of queries over the recent few emails:
>>
>> The bibjson.org <http://bibjson.org> site is a list of the examples we
>>
>> have seen in use to date. If we gain consensus on a particular usage, we
>> can add it to the list. For example, I am currently using
>> "citation":[{...}] on another project, so would probably soon suggest we
>> add that to the bibjson.org <http://bibjson.org> page.
>>
>>
>> As regards dc:creator, the initial approach of bibjson growing from
>> bibtex promotes that we use "author":[{...}] lists, and similarly
>> "editor":[{...}] lists.
>>
>> For author name strings, following again from the bibtex examples
>> bibjson came from, the author.name <http://author.name> field is
>>
>> expected to be of the form "MacGillivray Mark" as most people tend to
>> search by last name first so it is easily supported. There are also
>> examples of the use of specific firstname and lastname keys in addition
>> to or instead of the full "name" key.
>>
>> For JSON-LD, all the linked data requirements that came up were
>> answerable by the use of JSON-LD and bibjson combined, so we stated that
>> on the web page. We did not provide any further example because there
>> were no such examples at the time. If there are some now, we could add
>> them.
>>
>> Similarly, there is no schema for bibjson because there were no examples
>> of anyone using one at the time.
>>
>> The reason there are no examples of how to do things that had not been
>> done is - at least from my personal perspective - that there is little
>> point over-complicating things with examples of how to do stuff that
>> people may never actually do in practice. I personally have not yet been
>> presented with a use case that required me either to have a JSON-LD
>> representation or a schema, so I did not waste time creating things I
>> did not need.
>>
>> However, that said, where anyone does have examples of usage of such
>> things, and therefore can provide such examples along with a description
>> of the use cases they support, we should add them to the bibjson.org
>> <http://bibjson.org> page. If anyone needs to create a schema, we could
>>
>> put that up too.
>>
>> Mark
>>
>>
>>
>>
>>
>>
>>
>> On Sat, Feb 23, 2013 at 8:16 AM, Sylvain Hellegouarch
>> <sylvain.hellegouarch at gmail.**com <sylvain.hellegouarch at gmail.com><mailto:
>> sylvain.hellegouarch@**gmail.com <sylvain.hellegouarch at gmail.com>>>
>>
>> wrote:
>>
>>     Hi Tom,
>>
>>     2013/2/23 Tom Johnson <johnson.tom at gmail.com
>>     <mailto:johnson.tom at gmail.com>**>
>>
>>
>>         If you are starting from BibJSON, JSON-LD "support" is as simple
>>         as creating a context document mapping tokens to the desired
>>         URIs. What the context document looks like depends mostly on
>>         which vocabularies/terms you want in your graph. I'm guessing
>>         this is the reason it was decided not to include an example in
>>         the documentation.
>>
>>         I did some work on JSON-LD and BibJSON, published in the most
>>         recent Code4Lib Journal. http://journal.code4lib.org/**
>> articles/7949 <http://journal.code4lib.org/articles/7949>
>>
>>         Is there is interest in an example context document and some
>>         guidance documentation?
>>
>>         Sylvian: do you have a use case for the linked data?
>>
>>
>>
>>     As of now, it's neither a requirement nor a priority so I'm happy
>>     enough concentrating already on having clean standalone BibJSON
>> records.
>>     --
>>     - Sylvain
>>     http://twitter.com/lawouach
>>     http://www.defuze.org
>>
>>     ______________________________**_________________
>>     openbiblio-dev mailing list
>>     openbiblio-dev at lists.okfn.org <mailto:openbiblio-dev at lists.**okfn.org<openbiblio-dev at lists.okfn.org>
>> >
>>
>>     http://lists.okfn.org/mailman/**listinfo/openbiblio-dev<http://lists.okfn.org/mailman/listinfo/openbiblio-dev>
>>     Unsubscribe: http://lists.okfn.org/mailman/**options/openbiblio-dev<http://lists.okfn.org/mailman/options/openbiblio-dev>
>>
>>
>>
>>
>> ______________________________**_________________
>> openbiblio-dev mailing list
>> openbiblio-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/**listinfo/openbiblio-dev<http://lists.okfn.org/mailman/listinfo/openbiblio-dev>
>> Unsubscribe: http://lists.okfn.org/mailman/**options/openbiblio-dev<http://lists.okfn.org/mailman/options/openbiblio-dev>
>>
>>
> --
> Karen Coyle
> kcoyle at kcoyle.net http://kcoyle.net
> ph: 1-510-540-7596
> m: 1-510-435-8234
> skype: kcoylenet
>
> ______________________________**_________________
> openbiblio-dev mailing list
> openbiblio-dev at lists.okfn.org
> http://lists.okfn.org/mailman/**listinfo/openbiblio-dev<http://lists.okfn.org/mailman/listinfo/openbiblio-dev>
> Unsubscribe: http://lists.okfn.org/mailman/**options/openbiblio-dev<http://lists.okfn.org/mailman/options/openbiblio-dev>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/openbiblio-dev/attachments/20130223/28d9eb1d/attachment.html>


More information about the openbiblio-dev mailing list