ember 18, 2010 at
6:00 PM (ET) Greenville, SC
Co-Chairs: Mike Amundsen & Benjamin Young
REST Fest 2010 (Sep 17th & 18th)
REST Fest is a community unconference event focused on the REST
architectural style and implementations. This year, REST Fest will
encourage developers who have dire
On 5/13/10 8:59 AM, Fernando Gómez wrote:
Any suggestions? Do other document oriented databases offer a better
solution for this?
Hey Fernando,
I'd suggest you checkout CouchDB. CouchDB uses JSON as it's document
format, provides advanced indexing (anywhere in the JSON docs) via
map/reduc
On 4/29/10 3:48 PM, Boheemen, Peter van wrote:
But all the flaws of XML can be traced back to SGML which is
why we now use JSON despite all of its limitations.
excuse me, but JSON is something completely different. It is an object notation
and in not at all usable to structure data.
Don't
On 4/29/10 12:32 PM, MJ Suhonos wrote:
What I hope for is that OpenURL 1.0 eventually takes a place alongside SGML as
a too-complex standard that directly paves the way for a universally adopted
foundational technology like XML. What I fear is that it takes a place
alongside MARC as an anachro
I vote (heh) for "d" which will look a lot like "c" anyway, but with
smatterings of owl:sameAs and Range-14 style 303's to keep things
interesting. :)
--
President
BigBlueHat
P: 864.232.9553
W: http://www.bigbluehat.com/
http://www.linkedin.com/in/benjaminyoung
On 4/29/10 2:01 PM, Jakob Voss
At #ldow2010 on Tuesday there was a presentation on "semantic" Twitter
via TwitLogic:
http://twitlogic.fortytwo.net/
You can download the full paper if you're really curious:
http://events.linkeddata.org/ldow2010/papers/ldow2010_paper16.pdf
Twitter Annotations system was mentioned at the end as
ngful on the JSON side (as attributes and such make a
1-to-1 conversion complicated--though there have been attempts at
general conversion scripts).
Once a JSON output format for MARC is done, then converting from MARCXML
to marc.json (or whatever) would be an "easy" first step.
On 20
On 4/12/10 4:47 PM, Ryan Eby wrote:
You could put your logs, marc records broken out by fields or
arrays/hashes (types in couchdb) in any of them but the approach each
takes would limit you (or empower you) differently.
Once there's a good marc2json script (and format) out there, it'd be
gra
From my understanding of key/value stores, one can put documents on the
other side of the key, but any and all parsing/processing of that value
happens outside of the database. In CouchDB, the entire document is
query-able from within map/reduce views. After being querying on, those
keys are in
SQL-style JOINs can be done in CouchDB (can't speak for the other NoSQL
DB's).
In CouchDB, it's called view collation:
http://chrischandler.name/couchdb/view-collation-for-join-like-behavior-in-couchdb/
It's a different way of thinking (as there are no tables, and map/reduce
goes through every
I'd actually vote for the "sensible, forward-looking approach." The BBC
(for one) is already using CouchDB in a production:
http://damienkatz.net/2010/03/bbc_and_couchdb.html
That said, NoSQL as a "movement" is as wide and varied as the RDBMS
world, and there are pros and cons to each. I'm per
He means JavaScript. ;)
Honestly, though, PHP and all it's fault not withstanding, I highly
recommend starting with a C syntax-based language such as JavaScript,
PHP, Java, or even C# (and obviously C and C++). Get some basic
programming concepts understood, and then pursue the language the fi
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 d
On 3/5/10 3:45 PM, Bill Dueber wrote:
On Fri, Mar 5, 2010 at 3:14 PM, Houghton,Andrew 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
On 3/5/10 2:46 PM, Ross Singer wrote:
On Fri, Mar 5, 2010 at 2:06 PM, Benjamin Young 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
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,Andrew
wrote:
On 3/5/10 8:15 AM, Godmar Back wrote:
On Fri, Mar 5, 2010 at 3:59 AM, Ulrich Schaeferwrote:
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
Have you seen the Exhibit library (part of the Simile project at MIT)?
It provides faceted browsing along with map integration:
http://www.simile-widgets.org/exhibit/
It should be fairly easy to add to an existing project as it can consume
a pretty simple JSON format that your app could provide
Hey Godmar,
I'd definitely consider CouchDB as Patrick mentioned. It's a
"schema-free" JSON document database and replication is it's greatest
strength.
It does have Lucene integration:
http://github.com/rnewson/couchdb-lucene
Paul J. Davis of the core CouchDB team has a nice write-up:
http:/
19 matches
Mail list logo
