Thanks to a bit of creative re-purposing, museum-api.pbwiki.com is open for sharing, discussing, arguing over and hopefully coming to some common agreements on APIs and data schemas for museum collections.
What you can do:
- Upload or copy and paste some examples from your collections data schemas – whether that’s nicely marked up xml, a table structure from the databases that feed your website, even plain old HTML from an online page.
- Link to your API, tell us what’s worked, which ideas we should pinch
- List the functionality of your API (through documentation, examples, whatever)
- Talk about how you decided how to implement your API
- Start a discusion with your questions, unresolved issues
The great API challenge
Thursday, March 5th, 2009Another MCG (museums computer group) discussion list post repurposed as a blog post… In a discussion about the Brooklyn Museum API following on from discussion of the NMOLP ‘Creative Spaces’ project, Richard Light asked:
I quickly checked with Daniel, our head of web, that it was ok for me to throw this open to the world, and posted in response:
So, are you up for it? I’ve had a few good responses already. My vague idea is maybe using digitalheritage.ning.com to share data schemas, API functionality, discuss the various acronyms we’re using, etc.
You can leave a comment here, or join the ning, or @miaridge on twitter.
Posted in API, crowdsourcing, design, requestforcomment | No Comments »