Re: marc in json

From: Ross Singer <rossfsinger_at_nyob>
Date: Thu, 1 Dec 2011 09:11:09 -0500
Ed, I think this would be great.  Obviously, there's zero
standardization around MARC/JSON (Andrew Houghton has come the
"closest" by writing up the most RFC-y proposal:

I generally fall more in the camp of "working code wins", though,
which, solely on the basis of MARC parser support, would put my
proposal in front.  In the end, I don't think it matters which style
is adopted; it's an interchange format, any one of them works (and
they all, including Bill Dueber's) has their pluses and minuses.  The
more important thing is that we pick -one- and go with it so we can
use it with some confidence.

While we're on the subject, if there are any other serializations of
MARC that people are legitimately interested in (TurboMARC, for
and wish ruby-marc supported, let me know.


On Thu, Dec 1, 2011 at 5:57 AM, Ed Summers <> wrote:
> Martin Czygan recently added JSON support to pymarc [1]. Before this
> gets rolled into a release I was wondering if it might make sense to
> bring the implementation in line with Ross Singer's proposed JSON
> serialization for MARC [2]. After quickly looking around it seems to
> be what got implemented in ruby-marc [3] and PHP's File_MARC [4]. It
> also looked like there was a MARC::Record branch [5] for doing
> something similar, but I'm not sure if that has been released yet.
> It seems like a no-brainer to bring it in line, but I thought I'd ask
> since I haven't been following the conversation closely.
> //Ed
> [1]
> [2]
> [3]
> [4]
> [5];a=shortlog;h=refs/heads/marc-json
Received on Thu Dec 01 2011 - 09:15:30 EST