-interest-in-marc-hash-json/
Houghton,Andrew wrote:
From: Houghton,Andrew
Sent: Saturday, March 06, 2010 06:59 PM
To: Code for Libraries
Subject: RE: [CODE4LIB] Q: XML2JSON converter
Depending on how much time I get next week I'll talk with the developer
network folks to see what I need
06:59 PM
To: Code for Libraries
Subject: RE: [CODE4LIB] Q: XML2JSON converter
Depending on how much time I get next week I'll talk with the developer
network folks to see what I need to do to put a specification under
their infrastructure
I finished documenting our existing use
:
From: Houghton,Andrew
Sent: Saturday, March 06, 2010 06:59 PM
To: Code for Libraries
Subject: RE: [CODE4LIB] Q: XML2JSON converter
Depending on how much time I get next week I'll talk with the developer
network folks to see what I need to do to put a specification under
for transfer accross the wire, I prefer Bill's approach.
http://robotlibrarian.billdueber.com/new-interest-in-marc-hash-json/
Houghton,Andrew wrote:
From: Houghton,Andrew
Sent: Saturday, March 06, 2010 06:59 PM
To: Code for Libraries
Subject: RE: [CODE4LIB] Q: XML2JSON converter
Depending
On 03/15/2010 06:22 PM, Houghton,Andrew wrote:
Secondly, Bill's specification looses semantics from ISO 2709, as I
previously pointed out. His specification clumps control and data
fields into one property named fields. According to ISO 2709, control
and data fields have different semantics.
Bill's format would allow there to be a control field and a data field
with the same tag, however, so it's all good either way.
Ere Maijala wrote:
On 03/15/2010 06:22 PM, Houghton,Andrew wrote:
Secondly, Bill's specification looses semantics from ISO 2709, as I
previously pointed out. His
the wire, I prefer Bill's approach.
http://robotlibrarian.billdueber.com/new-interest-in-marc-hash-json/
Houghton,Andrew wrote:
From: Houghton,Andrew
Sent: Saturday, March 06, 2010 06:59 PM
To: Code for Libraries
Subject: RE: [CODE4LIB] Q: XML2JSON converter
Depending on how much time I get next week
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Jonathan Rochkind
Sent: Monday, March 15, 2010 11:53 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter [MARC-JSON]
I would just ask why you didn't use Bill Dueber's already existing
proto
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Bill Dueber
Sent: Monday, March 15, 2010 12:19 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter [MARC-JSON]
I would like to see ind1 and ind2 get their own fields, though, for
easier
use
, Mar 15, 2010 at 11:22 AM, Houghton,Andrew hough...@oclc.org wrote:
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Jonathan Rochkind
Sent: Monday, March 15, 2010 11:53 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter [MARC-JSON]
I
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Bill Dueber
Sent: Monday, March 15, 2010 12:40 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter [MARC-JSON]
On the one hand, I'm all for following specs. But on the other...should
we
On 3/6/10 6:59 PM, Houghton,Andrew wrote:
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Bill Dueber
Sent: Saturday, March 06, 2010 05:11 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter
Anyway, hopefully, it won't be a huge surprise that I
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Benjamin Young
Sent: Monday, March 08, 2010 09:32 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter
Rather than using a newline-delimited format (the whole of which would
not together
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Bill Dueber
Sent: Friday, March 05, 2010 08:48 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter
On Fri, Mar 5, 2010 at 6:25 PM, Houghton,Andrew hough...@oclc.org
wrote:
OK, I will bite
On Sat, Mar 6, 2010 at 1:57 PM, Houghton,Andrew hough...@oclc.org wrote:
A way to fix this issue is to say that use cases #1 and #2 conform to
media type application/json and use case #3 conforms to a new media type
say: application/marc+json. This new application/marc+json media type now
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Bill Dueber
Sent: Saturday, March 06, 2010 05:11 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter
Anyway, hopefully, it won't be a huge surprise that I don't disagree
with any of the quote
Godmar Back wrote:
Hi,
Can anybody recommend an open source XML2JSON converter in PhP or
Python (or potentially other languages, including XSLT stylesheets)?
Ideally, it should implement one of the common JSON conventions, such
as Google's JSON convention for GData [1], but anything that
On Fri, Mar 5, 2010 at 3:59 AM, Ulrich Schaefer ulrich.schae...@dfki.dewrote:
Hi,
try this: http://code.google.com/p/xml2json-xslt/
I should have mentioned that I already tried everything I could find after
googling - this stylesheet doesn't meet the requirements, not by far. It
drops
Internet Archive seems to have a copy of that:
http://web.archive.org/web/20071013052842/badgerfish.ning.com/file.php?format=srcpath=lib/BadgerFish.php
as well as several versions of the site:
http://web.archive.org/web/*/http://badgerfish.ning.com
Kevin
On Fri, Mar 5, 2010 at 8:15 AM,
On 3/5/10 8:15 AM, Godmar Back wrote:
On Fri, Mar 5, 2010 at 3:59 AM, Ulrich Schaeferulrich.schae...@dfki.dewrote:
Hi,
try this: http://code.google.com/p/xml2json-xslt/
I should have mentioned that I already tried everything I could find after
googling - this stylesheet doesn't
You can find it here, although I wouldn't get too excited: http://bit.ly/acROxH
You could also fish for more info by badgering its creator at
http://www.sklar.com/page/section/contact.
Cary
On Fri, Mar 5, 2010 at 5:15 AM, Godmar Back god...@gmail.com wrote:
On Fri, Mar 5, 2010 at 3:59 AM,
have you tried this?
http://www.bramstein.com/projects/xsltjson/
http://github.com/bramstein/xsltjson
using the parameter |use-rayfish=true seems to preserve everything but
namespaces but then there is a parameter to preserve namespaces as well.|
Mark
On 3/5/2010 12:54 AM, Godmar Back
On Fri, 5 Mar 2010, Godmar Back wrote:
On Fri, Mar 5, 2010 at 3:59 AM, Ulrich Schaefer ulrich.schae...@dfki.dewrote:
Hi,
try this: http://code.google.com/p/xml2json-xslt/
I should have mentioned that I already tried everything I could find after
googling - this stylesheet doesn't meet the
If PHP/python isn't a hard requirement, I think this would be fairly
simple to do in perl using a combination of the XML::Simple [1] and
JSON::XS [2] modules.
In fact it's so simple, here's the code:
#!/usr/bin/perl
use JSON::XS;
use XML::Simple;
use strict;
my $filename = shift @ARGV;
my
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Benjamin Young
Sent: Friday, March 05, 2010 09:26 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter
If you're looking at putting MARC into JSON, there was some discussion
of that during
On Fri, Mar 5, 2010 at 12:01 PM, Houghton,Andrew hough...@oclc.org wrote:
Too bad I didn't attend code4lib. OCLC Research has created a version of
MARC in JSON and will probably release FAST concepts in MARC binary,
MARC-XML and our MARC-JSON format among other formats. I'm wondering
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Bill Dueber
Sent: Friday, March 05, 2010 12:30 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter
On Fri, Mar 5, 2010 at 12:01 PM, Houghton,Andrew hough...@oclc.org
wrote:
Too bad I
On Fri, Mar 5, 2010 at 1:10 PM, Houghton,Andrew hough...@oclc.org wrote:
I decided to stick closer to a MARC-XML type definition since its would be
easier to explain how the two specifications are related, rather than take a
more radical approach in producing a specification less familiar.
On 3/5/10 1:10 PM, Houghton,Andrew wrote:
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Bill Dueber
Sent: Friday, March 05, 2010 12:30 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter
On Fri, Mar 5, 2010 at 12:01 PM, Houghton,Andrewhough
On Fri, Mar 5, 2010 at 1:10 PM, Houghton,Andrew hough...@oclc.org wrote:
I certainly would be will to work with LC on creating a MARC-JSON
specification as I did in creating the MARC-XML specification.
Quite frankly, I think I (and I imagine others) would much rather see
a more open,
On Fri, Mar 5, 2010 at 2:06 PM, Benjamin Young byo...@bigbluehat.com wrote:
A CouchDB friend of mine just pointed me to the BibJSON format by the
Bibliographic Knowledge Network:
http://www.bibkn.org/bibjson/index.html
Might be worth looking through for future collaboration/transformation
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Bill Dueber
Sent: Friday, March 05, 2010 01:59 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter
On Fri, Mar 5, 2010 at 1:10 PM, Houghton,Andrew hough...@oclc.org
wrote:
I decided
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Benjamin Young
Sent: Friday, March 05, 2010 02:06 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter
A CouchDB friend of mine just pointed me to the BibJSON format by the
Bibliographic
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Ross Singer
Sent: Friday, March 05, 2010 02:32 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter
On Fri, Mar 5, 2010 at 1:10 PM, Houghton,Andrew hough...@oclc.org
wrote:
I certainly
On 3/5/10 2:46 PM, Ross Singer wrote:
On Fri, Mar 5, 2010 at 2:06 PM, Benjamin Youngbyo...@bigbluehat.com wrote:
A CouchDB friend of mine just pointed me to the BibJSON format by the
Bibliographic Knowledge Network:
http://www.bibkn.org/bibjson/index.html
Might be worth looking through
On Fri, Mar 5, 2010 at 3:14 PM, Houghton,Andrew hough...@oclc.org wrote:
As you point out JSON streaming doesn't work with all clients and I am
hesitent to build on anything that all clients cannot accept. I think part
of the issue here is proper API design. Sending tens of megabytes back
-Original Message-
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf
Of
Bill Dueber
I really do understand the desire to make this parallel to marc-xml,
but
there's a seem between the two technologies that makes that a
problematic
approach.
As a confession, here
On 3/5/10 3:45 PM, Bill Dueber wrote:
On Fri, Mar 5, 2010 at 3:14 PM, Houghton,Andrewhough...@oclc.org wrote:
As you point out JSON streaming doesn't work with all clients and I am
hesitent to build on anything that all clients cannot accept. I think part
of the issue here is proper API
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Bill Dueber
Sent: Friday, March 05, 2010 03:45 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter
I guess my concern here is that the specification, as you're describing
it, is closing off
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Benjamin Young
Sent: Friday, March 05, 2010 04:24 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter
For my part, I'd like to explore the options of putting MARC data into
CouchDB (which
On Fri, Mar 5, 2010 at 4:38 PM, Houghton,Andrew hough...@oclc.org wrote:
Maybe I have been mislead or misunderstood JSON streaming.
This is my central point. I'm actually saying that JSON streaming is painful
and rare enough that it should be avoided as a requirement for working with
any new
On Fri, Mar 5, 2010 at 6:25 PM, Houghton,Andrew hough...@oclc.org wrote:
OK, I will bite, you stated:
1. That large datasets are a problem.
2. That streaming APIs are a pain to deal with.
3. That tool sets have memory constraints.
So how do you propose to process large JSON datasets that:
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Ross Singer
Sent: Friday, March 05, 2010 09:18 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: XML2JSON converter
I actually just wrote the same exact email as Bill (although probably
not as polite -- I
43 matches
Mail list logo
