cultural heritage categories and properties - AyranIsTheNewRaki/Herodot GitHub Wiki

Properties of cultural heritage items chosen

# References: #

http://pro.europeana.eu/share-your-data/data-guidelines/edm-documentation

http://labs.europeana.eu/api/linked-open-data-introduction

http://pro.europeana.eu/files/Europeana_Professional/Share_your_data/Technical_requirements/EDM_Documentation/EDM_Factsheet.pdf

http://pro.europeana.eu/files/Europeana_Professional/Share_your_data/Technical_requirements/EDM_Documentation/EDM_Mapping_Guidelines_v2.3_112016.pdf

http://pro.europeana.eu/files/Europeana_Professional/Share_your_data/Technical_requirements/EDM_Documentation/EDM_Primer_130714.pdf

https://github.com/europeana/corelib/wiki/EDMObjectTemplatesProviders

After reading the Europeana Data Model, and linked data and its workings, the logic and technology behind semantic web and annotations and their data models, in addition with standards, it was evident that a schema was already in place and as software engineers we needed to understand and use these standards in order to deliver the requirements asked by the client.

The client would be happy to know that the end product/ web site with its data and metadata will be interoperable in web and may also have a value proposition to be more visible than other resources by the use of these linked in data benefis and be a pioneer in the new linked in data network in progress. More inbound means better site score, data is more enriched and visible. Trustworthy linked open data being made available now, gives you big advantage in the www in terms of users, traffic, etc etc. by being a canonical reference point.

In short after reading all the standards in place on the linked data structure, it was meaningless to come up with a new data properties. As software engineers we will be using already established standards in our domain according to our needs.

EDM: europeana data model

CHO: cultural heritage object

The EDM Mapping Guidelines– give guidance for providers wanting to map their data to EDM. They show which property relates to which class and contains definitions of the properties, the data types that can be used as values and the obligation level of each property. It also has an example of original data, the same data converted to EDM and diagrams showing the distribution of the properties amongst the classes. The full set of EDM classes and properties are being implemented incrementally and the Mapping Guidelines is the reference document showing which are currently available

The EDM object templates – a working document is a simple wiki listing that shows which properties apply to which class and states the data types and obligation of the values. These templates should be regarded as a work in progress however and may be out of step with the Guidelines. Please refer to the Mapping guidelines for the current set of classes and properties in use.

The core classes are: • edm:ProvidedCHO** - the provided cultural heritage object • edm:WebResource - the web resource that is the digital representation • ore:Aggregation - the aggregation that groups the classes together

Here the focus will be on the core class provided cultural heritage item as a real object

Properties for EDM:ProvidedCHO meaning the attributes of the monalisa painting but not the attributes of the digitized image of the monalisa painting

Before we proceed on more terminology to clarify: dc and dcterms http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=terms DCMI metadata terms, namescapes and elements are used in the below attributes since metadata is the backbone of this linked data schema