Kennisinstituut voor amateurkunst en cultuurinstituut

Seems like candidates for re-euse somewhere in the ECK

Inspiration for the Europeana Management Information?

Wikimedia as extra target for the ECK?

Klimpel, Paul. [14]Free Knowledge Based on Creative Commons Licenses: Consequences, Risks and Side-Effects of the License Module Berlin: Wikimedia Germany, February

another service useful to overcome barriers for using the ECK

developped tools/service might be implemented in the ECK to apply right labels in batch.

Overview of what are non-functional requirements

Also highly relevant since it specifies how proprietary metadata is transformed in a couple of stages into Europeana EDM as well as other service providers including Flickr. The only concern is that for HOPE it was clear from the beginning that a central service was delivered unlike EU-Inside.

A good example for D2.4? Although in the document it says: we must stress that this document is neither a Functional Requirements nor a Technical Specifications document. It's unclear to me if such documents have been produced in the HOPE project and if they are accessible to us.

Also has a chapter of implementing licence in data exchange.

helps institutions to choose the appropriate license for their content.

Although a very different context of use this deliverable has a lot to learn for EU-Inside

Although the context of use is different, this document comes closes to what we have to deliver as D2.2. so far.

Since we've aggreed to use UML in helping to put together the specifications, it's useful to reach aggrement on how far we go with this. The maturity level might be of help.

Described by Isaac it illustrates the making available of metadata by content privders from an Europeana point of view. Also touches on enrichements.

I guess this is deliverable describes the core of what Europeana is supposed to be. It is however over 2 years old, and the ideas have shifted somewhat.