In message
<[log in to unmask]>,
Mike Ellis <[log in to unmask]> writes
>In other, rather more uplifting news, the Brooklyn Museum releases an API:
"Another API" is indeed good news when there is only a handful of them.
Anything from a museum context that delivers XML cheers me up, as you
know ;-)
However, "[yet] another API with its own home-grown query syntax and
unique results format" will start to be wearisome news to integrators,
when there are hundreds of APIs out there, and more arriving every week.
Don't we need a standard for what a museum API looks like, and what it
delivers? Even better, shouldn't we stop thinking that we need to
invent everything we use, and just adopt something like the Linked Data
paradigm?
Richard
--
Richard Light
**************************************************
For mcg information and to manage your subscription to the list, visit the website at http://www.museumscomputergroup.org.uk
**************************************************
|