The document discusses the Europeana API project which aims to expose the functionalities of the main Europeana software product. It notes there will be two major releases of the API called Rhine and Danube. It also discusses gathering requirements and specifications for the API architecture and evaluating the API design. There was discussion on whether the API should be HTTP based, needing rich requirements, and questions around the data and metadata models to support ingestion, dissemination, and updating of content.

1. WP 3.3 Day 2 : API and Functional Architecture Carlo Meghini ISTI

2. WP 3.3 Presentation Presentation on the concept of Europeana API The main software product created by the project Exposes functionallities Two major releases: -Rhine (specifications need to be defined:M8/M18 -Danube (specifications need to be defined:M18/M27) D2.5 Deliverables- document specifies the architecture

3. WP 3.3 Interactive session: the Europeana API (What are we missing?) Next steps: API specifications Evaluation of the API

4. WP 3.3 Round Table In the context of external applications: is API HTTP based?  not necessarily The difficulty with API’s is that we need very rich and precise requirements to have a full understanding, so we have to experiment (Bram) API are less Europeana specific?  this ensures a double component. Need a powerful language supported by all search engine Need of third parties?  this will be necessary to take this forward

5. WP 3.3 Round table Surrogate model Submission information package Request for one 2 one mapping Enrichment- if you ingest an object, what is the dissemination format? Recognize two different models? Discovery manager is described in more detail simple/advanced search: a prototype is implemented Other types of search will be integrated (by Europeana Connect?, What?, Where?...)

6. WP 3.3 Round Table Supply suggestions for attributes (in the form of use cases) The surrogate model will have a hierachy of the properties Through these properties we can accomodate the cross domain Special relationships are needed for museums

7. WP3.3 Brainstorming about API Questions about: Flexible Architecture for ingestion and dissemination Metadata enrichment… Do we need a model for updating information?

8. WP3.3 Wrap-up/next steps For the next meeting Feedback on the specification of API is welcome The Office will set up an mailing list for this workgroup