Main thought: Smaller chunks of interlinked services (eg James, Neil, Tom)

Transcription: REST calls (JSON) to save. API is the rest call to do
one function, can be implemented in any way at the back end.
Versioning.
Broadcast list of MS descriptions
Expose full/brief metadata
Image streaming (dimensions, format etc)
Service registry
Citation (down to page region)
Text search
Access Control (Auth'n and Interoperability)

Neil: Objects in system for registry
Raphael: What is a common API? (to be discussed)

Technology implications:

REST unanimously supported over SOAP / SOA
RDF: OAC, Oxford, Text grid using. Stanford and James looking at.
Linked Data, rather than full RDF tech stack
METS: not used, moving to ORE

__

Rob Sanderson