A follow-up on the discussions we had last week, in the work we're doing at the Office trying to populate EDM templates.
The basic idea is to make the work easier for providers who don't have to manage the data provenance requirements that Europeana has to meet. For such providers, all descriptive metadata on objects comes from their space, and hence they don't need proxies.
http://europeanalabs.eu/wiki/EDMXMLSchema thus now gives access to two pages:
In the same line, in the next week we would work on making the Primer reflect that, as Herbert suggested. Mostly, streamlining most of the examples and making proxies disappear from the beginning of the document...
> Hi everyone,
> I will mention it at the meeting in Vienna next week, but in case some of you are interested in more details, here are links to recent progresses made at the Office for the Danube programme (beyond the ESE-EDM stuff for linked data that I've circulated last week):
> - identification by the Operations team of properties that apply to the different main EDM classes, so as to prepare programming work by our technical team (and which can be used for XML schema creation). This is based on the EDM specs you know already--notably formal and informal domain and ranges assignments.
> It also tries to fill some gaps re. the contextual entity classes for which little "profiling information" came out of our work in WP3. The aim is clearly not to be exhaustive. Rather, we cherry-picked elements from available ontologies, so that Europeana can later ingest (and exploit) a "core" for each of these types.
> See http://europeanalabs.eu/wiki/EDMXMLSchema