Dear All,
Hugues from McCord sent along this great email with links to some of
the API solutions that museums are using.
Have a look...
Welcome to the list Hugues!
Best,
Jess
~~~~~~~~~~~~~~~~~~~~~~
Jess Mitchell
Boston, MA, USA
Project Manager / Fluid Project
[email protected]
/ w / 617.326.7753 / c / 919.599.5378
jabber: [email protected]
http://www.fluidproject.org
~~~~~~~~~~~~~~~~~~~~~~
Begin forwarded message:
From: Hugues Boily <[email protected]>
Date: May 20, 2009 1:15:14 PM EDT
To: Jess Mitchell <[email protected]>
Cc: Colin Clark <[email protected]>
Subject: Re: Fluid Engage | McCord | Icebreaker project
Cool!
On a related note, i had an idea regarding data exchange between
client applications & museum back-ends : what about using museum
APIs? A few museums have recently developed APIs to their
collections, exhibits, etc. More are in the work (like the V&A
Museum API which is in beta) and the McCord is considering
implementing such an API. Different output formats could be
supported (XML, JSON, RSS, ...).
Examples
The Brooklyn Museum API:
http://www.brooklynmuseum.org/opencollection/api/
The Brooklyn is developing an Iphone App which will use the API to
retrieve data
http://www.brooklynmuseum.org/community/blogosphere/bloggers/2009/04/17/brooklyn-museum-api-the-iphone-app/
Digital New-Zealand API
http://www.digitalnz.org/developer
The Victoria & Albert has also developed an API (still in beta),
which incorporates social media and user generated content
http://www.archimuse.com/mw2009/papers/morgan/morgan.html
Cheers
Hugues
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
