Hello all,
As regards multiple JSON records in a single file, I have written
up a proposal here:
http://en.wikipedia.org/wiki/User:Baxter.brad/Drafts/JSON_Document_Streaming_Proposal
So this is sort of an RFC. I've added a proof-of-concept routine
that implements the proposal to this module (see
Hi,
On Thu, Feb 10, 2011 at 9:06 AM, Brad Baxter wrote:
> I had also thought about how to separate JSON records in a single file.
> Perhaps this has been solved already, but I haven't seen a reference
> to it. If it were YAML, you could simply put "\n---\n" between the JSON
> objects, and it wou
On Wed, Feb 9, 2011 at 5:29 PM, Galen Charlton wrote:
> The MARC::File::JSON module is consistent with other MARC::File::XXX
> modules that handle serializing and deserializing MARC::Record
> objects.
>
> MARC::Utils::MARC2Ini is an interesting concept, but it wouldn't take
> much work to recast i
Hi,
2011/2/10 Frédéric DEMIANS :
>> [2]
>> http://dilettantes.code4lib.org/blog/2010/09/a-proposal-to-serialize-marc-in-json/
>> [3] http://www.oclc.org/developer/groups/marc-json-format-specification
>> [4]
>> http://robotlibrarian.billdueber.com/marc-hash-a-proposed-format-for-jsonyamlwhatever-c
Le 18/01/2011 00:59, Galen Charlton a écrit :
> [2]
http://dilettantes.code4lib.org/blog/2010/09/a-proposal-to-serialize-marc-in-json/
> [3] http://www.oclc.org/developer/groups/marc-json-format-specification
> [4]
http://robotlibrarian.billdueber.com/marc-hash-a-proposed-format-for-jsonyamlwh
Hi,
On Wed, Feb 9, 2011 at 12:58 PM, Brad Baxter wrote:
> I'm not sure what your interface for MARC-in-JSON in
> MARC::Record will look like, so maybe this is in conflict
> with that -- or maybe not.
Conflict? I wouldn't think so, but perhaps superfluous in the case of
MARC-
, and the third, to and from an Ini file string.
I'm not sure what your interface for MARC-in-JSON in
MARC::Record will look like, so maybe this is in conflict
with that -- or maybe not.
Anyway, my reasoning is to provide more than one way
to represent MARC data outside of the usual, but stil
Le 18/01/2011 16:15, Smith,Devon a écrit :
>
> But other than that, 6 of one, half dozen of another ...
For non english natives like me:
http://www.goenglish.com/SixOfOneAHalfDozenOfTheOther.asp
ok, got it ;-)
--
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel
On Tue, Jan 18, 2011 at 09:09:59AM -0500, Galen Charlton wrote:
> Hi,
>
> On Tue, Jan 18, 2011 at 9:06 AM, Paul Hoffman wrote:
> > IMO this belongs in a separate module, not in MARC::Batch or
> > MARC::Record. Small pieces, loosely joined!
>
> MARC::Record and MARC::Batch are frameworks that in
On Tue, Jan 18, 2011 at 10:43 AM, Galen Charlton wrote:
> Hi,
>
> On Tue, Jan 18, 2011 at 10:15 AM, Smith,Devon wrote:
>> I think it's a mistake to get hung up on the leader being "next to" the
>> fields or the indicators being "next to" the subfields. The leader and
>> indicators aren't really d
Hi,
On Tue, Jan 18, 2011 at 10:15 AM, Smith,Devon wrote:
> I think it's a mistake to get hung up on the leader being "next to" the
> fields or the indicators being "next to" the subfields. The leader and
> indicators aren't really different than fields and subfields. They were
> given special tre
On 1/18/11 10:15 AM, "Smith,Devon" wrote:
But other than that, 6 of one, half dozen of another ...
Agreed. I don't see where any of these are a ton better than others, with the
caveat that there's already code in ruby-marc, marc4j, and PHP's FIle_MARC for
the marc-in-json and some of us are us
-Original Message-
From: Dueber, William [mailto:dueb...@umich.edu]
Sent: Tuesday, January 18, 2011 9:57 AM
To: Brad Baxter; Galen Charlton
Cc: perl4lib
Subject: Re: MARC-in-JSON in MARC::Record
I like the fact that it's slightly less verbose, but am put off by the
fact that it mixes differ
I like the fact that it's slightly less verbose, but am put off by the fact
that it mixes different semantic entities in the same arrays. The leader is
"next to" the fields; the indicators are "next to" the subfields. E.g., in the
variable field:
{ "010" :
[
{ "ind1": " " },
{ "i
On Tue, Jan 18, 2011 at 9:14 AM, Brad Baxter wrote:
> that those algorithms might be the basis for a similar JSON library.
I meant, javascript library.
When I wrote Data::Pairs (http://search.cpan.org/dist/Data-Pairs/), I had
JSONified MARC in mind. To my mind, a data structure that is a "Pairs
of Pairs"[2] would faithfully represent a MARC record, including preserving
the orders of fields/subfields.
Below is the short example from [1] displayed
Hi,
On Tue, Jan 18, 2011 at 9:06 AM, Paul Hoffman wrote:
> IMO this belongs in a separate module, not in MARC::Batch or
> MARC::Record. Small pieces, loosely joined!
MARC::Record and MARC::Batch are frameworks that invoke
MARC::File::USMARC (and MARC::File::JSON and MARC::File::XML). It is
alr
On Tue, Jan 18, 2011 at 08:01:53AM -0500, Galen Charlton wrote:
> Hi,
>
> On Mon, Jan 17, 2011 at 9:30 PM, Dueber, William wrote:
> > Note that as of this point, the marc-in-json spec goes as high as the
> > Record object. A set of records could be represented by, say, the obvious
> > JSON-array
Hi,
On Mon, Jan 17, 2011 at 9:30 PM, Dueber, William wrote:
> Note that as of this point, the marc-in-json spec goes as high as the
> Record object. A set of records could be represented by, say, the obvious
> JSON-array of Record objects (which may necessitate a JSON pull-parser if
> you’ve got
As the author of one of the proposed JSON serialization strategies, let me
recommend that we let my proposal - known as "marc-hash" -- disappear quietly
into the ether :-)
I propose we get behind the MARC-in-JSON structure ([2]; also see [5]). It's
clean and as concise as it can be given what f
Hi,
I've pushed a branch called marc-json [1] implementing MARC-in-JSON
support for MARC::Record. Besides hooking it up with MARC::Batch, at
this point I'd like to know if there are any real-world cases where
anybody has had occasion or desire to emit or handle JSONified MARC
with the Perl librar
21 matches
Mail list logo
