> As an example, I have been looking at CouchDB, which
> Brief summary of CouchDB:
> 1. A B-tree manager whose records are JSON
> 2. Open-source, available from Apache, with
bindings to all common
> 3. An HTTP interface for queries and updates,
which uses map-reduce
> to take advantage of as many CPUs as your
server may have.
> 4. Documented by an O'Reilly book with a draft
available for free:
> At the end of this note is a sample JSON _expression_
used by CouchDB.
> Any quoted string could be a URI or it could be raw
data of any length.
> Suppose that you were a programmer working at a
library, and your boss
> asked you to convert the entire library catalog to
Linked Open Data
> and make it available via HTTP.
> If you chose Couch DB, you could
> 1. Read the O'Reilly book.
> 2. Download and install CouchDB.
> 3. Write a trivial program to map each record in
the library catalog
> to a JSON _expression_ very similar to the
> 4. Write a program to download every record from
> catalog, convert it to JSON, and store it in
> 5. Write a web page that tells any web master
anywhere in the world
> how to write an HTTP statement for accessing
> With CouchDB, you could finish that job in one week.
What could you
> do with RDF and currently available tools?
> Of course, there is no requirement that the strings
in JSON conform
> to any particular ontology. But that is also true of
> JSON makes it easy to tag URIs with types. In the
> anything on the left of a colon ":" could be a type
in the ontology.
> That's more readable and more compact than RDF. One
> also takes one DB access -- much, much less than
multiple RDF triples.
> Source: http://guide.couchdb.org/draft/json.html
> "Subject": "I like Plankton",
> "Author": "Rusty",
> "PostedDate": "2006-08-15T17:30:12-04:00",
> "Tags": [
> "Body": "I decided today that I don't like
baseball. I like plankton."