Property

Note

Value type

Card.

Memobase Entity

Memobase Attribute

Remarks

rdf:about

rico:Record → rico:identifiedBy → rico:Identifier with type main

rico:identifier

Beispiel: https://memobase.ch/record/apf-001-1034

dc:contributor

Use for contributors to the CHO. If possible supply the identifier of the contributor from an authority source. Providers with richer role terms can elect to map a subset to dc:contributor and others to dc:creator. Repeat for multiple contributors.

<dc:contributor>Maria Callas</dc:contributor>

or create a reference to an instance of the Agent class

<dc:contributor rdf:resource=“http://www.example.com/MariaCallas”/>

literal or ref

0…n

rico:Record → rico:recordResourceOrInstantiationIsSourceOfCreationRelation → rico:CreationRelation with type contributor → rico:creationRelationHasTarget → rico:Agent

rico:Record → rdau:P60441 → rico:Agent

rico:name

dc:coverage

The spatial or temporal topic of the CHO. Use the more precise dcterms:spatial or dcterms:temporal properties if the data will support it.

<dc:coverage>1995-1996</dc:coverage>or<dc:coverage>Berlin</dc:coverage>

or create a reference to an instance of a contextual class, for example, a Place class

<dc:coverage rdf:resource=“http://sws.geonames.org/2950159”/>

literal or ref

0….n

NA

NA

nicht verwendet, da wir präziser dcterms:spatial und dcterms:temporal verwenden können

dc:creator

For the creator of the CHO. If possible supply the identifier of the creator from an authority source. Repeat for multiple creators.

<dc:creator>Shakespeare, William</dc:creator>

or create a reference to an instance of the Agent class

<dc:creator rdf:resource=“http://viaf.org/viaf/96994048”/>

literal or ref

0….n

rico:Record → rico:recordResourceOrInstantiationIsSourceOfCreationRelation → rico:CreationRelation with type creator → rico:creationRelationHasTarget → rico:Agent

rico:name

dc:date

Use for a significant date in the life of the CHO. Europeana recommends date conforming to ISO 8601 starting with the year and with hyphens (YYYY-MMDD).

NB: other EDM elements are relevant for expressing dates of different events in the life of the CHO: dcterms:temporal, dcterms:created and dcterms:issued. Be careful and choose the most appropriate one!

<dc:date>Early 20th century</dc:date> or <dc:date>1919</dc:date> or create a reference to an instance of the TimeSpan class

<dc:date rdf:resource=“http://semium.org/time/19xx_1_third”/>

literal or ref

0….n

NA

NA

nicht verwendet, da wir präziser präziser dcterms:temporal, dcterms:created und dcterms:issued verwenden können

dc:description

A description of the CHO. If there is no dc:description for an object, there must be a dc:title. If both are available, provide both.

<dc:description>Illustrated guide to airport markings and lighting signals, with particular reference to SMGCS (Surface Movement Guidance and Control System) for airports with low visibilityconditions.</dc:description>

literal or ref

0….n

rico:Record

dct:abstract

rico:descriptiveNote

rico:scopeAndContent

dc:format

Use for the terms generally applied to indicate the format of the cultural heritage object or the file format of a born digital object. Use the value “3D-PDF” if appropriate.

<dc:format>paper</dc:format>

literal or ref

0….n

NA

NA

weggelassen, da dct:medium subproperty ist und verwendet wird

dc:identifier

An identifier of the original CHO.

<dc:identifier>RP-T-1952-380</dc:identifier>

literal

0….n

rico:Record → rico:identifiedBy → rico:Identifier with type main OR original

rico:identifier

Memobase ID und Source ID

dc:language

The language of text CHOs and also for other types of CHO if there is a language aspect. Mandatory for TEXT objects, strongly recommended for other object types with a language element. Best practice is to use ISO 639 two-or three-letter primary language tags⁵. Repeat for multiple languages.

We also recommend the useof the ISO 639-2 code for no linguistic content (ZXX).

<dc:language>it</dc:language>

literal

0….n

rico:Record → rico:hasLanguage → rico:Language with type caption or content and with rico:resultsFrom

schema:sameAs

Nur angereicherte Werte, gemappt zu ISO 639-3

dc:publisher

The name of the publisher of the CHO. If possible supply the identifier of the publisher from an authority source.

<dc:publisher>Oxford University Press</dc:publisher> or create a reference to an instance of the Agentclass

<dc:publisherrdf:resource=“http://www.oup.com/”/>

literal or ref

0….n

rico:Record → rico:publishedBy → rico:Agent

rico:name

dc:relation

The name or identifier of a related resource, generally used for other related CHOs. Cf edm:isRelatedTo.

<dc:relation>maps.crace.1/33</dc:relation> (Shelf mark) Or to provide a link to another object:

<dc:relation rdf:resource=“http://www.identifier/relatedObject”/>

literal or ref

0….n

NA

NA

evtl. später relevant für Filmwochenschau

dc:rights

Use to give the name of the rights holder of the CHO if possible or for more general rights information. (Note that the controlled edm:rights property relates to the digital objects and applies to the edm:WebResource and/or edm:Aggregation).

<dc:rights>Copyright © British Library Board</dc:rights>

literal or ref

0….n

rico:Record

rico:Record → rico:regulatedBy → rico:Rule with type holder

rico:conditionsOfAccess

rico:name

dc:source

A related resource from which the described resource is derived in whole or in part i.e. the source of the original CHO. (Not the name of the content holder: for this see edm:dataProvider.)

<dc:source>SecurityMagazine pp3-12</dc:source>

literal or ref

0….n

rico:Record

rico:source

dc:subject

The subject of the CHO. One of dc:subject or dc:type or dcterms:spatial or dcterms:temporal must be provided;if more than one of these properties is available, please provide them all. High-­level dc:subject values like 'archaeology' are allowed, especially when there is no other subject that can be easily filled in.

<dc:subject>trombone</dc:subject>

or create a reference to an instance of the Concept class

<dc :subject rdf:resource=http://id.loc.gov/authorities/subjects/sh85137992 "/>

literal or ref

0….n

rico:Record → rico:hasSubject → skos:Concept

rico:Record → rico:hasSubject → rico:Agent

skos:prefLabel

rico:name

dc:title

A name given to the CHO. dc:titleshouldbe present; but if there is no dc:title available, it is acceptable to have dc:description instead. dc:title and dc:description should be distinct. Exact translations of the title can be provided using appropriate xml language attributes.

<dc:title xml:lang=“en”>Eight Weeks</dc:title>

<dc:title xml:lang=“it”>Ocho semanas</ dc:title>

literal

0….n

rico:Record → rico:hasTitle → rico:Title with type = main

rico:title

dc:type

The nature or genre of the CHO. Ideally the term(s) will be taken from a controlled vocabulary. One of dc:type or dc:subject or dcterms:spatial or dcterms:temporal must be provided; if more than one of these properties is available, please provide them all. dc:type should not be (strictly) identical to edm:type.

<dc:type>Book</dc:type> or <dc:type>trombone</dc:type> or create a reference to an instance of the Concept class

<dc:type rdf:about=“http://www.mimo-db.eu/HornbostelAndSachs/356/”>

literal or ref

0….n

rico:Record → ebucore:hasGenre → skos:Concept without rico:resultsFrom

skos:prefLabel

nur Originalwerte

dcterms:alternative

Any alternative title of the CHO including abbreviations or translations that may not be exact.

<dcterms:alternativexml:lang=“en”>Eight weeks: a novel</dcterms:alternative>

literal

0….n

NA

NA

dcterms:conformsTo

An established standard to which the CHO conforms.

<dcterms:conformsTo>W3C WCAG 2.0</dcterms:conformsTo> (conforms to web content accessibility guidelines).

Or link to the resource

<dcterms:conformsTo rdf:resource=“http://www.w3.org/TR/WCAG/”/>

literal or ref

0….n

NA

NA

dcterms:created

The date of creation of the CHO. Europeana recommends date conforming to ISO 8601 starting with the year and with hyphens (YYYY-­MMDD).

NB: other EDM elements are relevant for expressing dates of different events in the life of the CHO: dc:date, dcterms:temporal and dcterms:issued. Be careful and choose the most appropriate one!

<dcterms:created>Mid 16th century</dcterms:created> or <dcterms:created>1584</dcterms:created> or create a reference to an instance of the TimeSpan class

<dcterms:created rdf:resource=“http://semium.org/time/15xx_3_third”/>

literal or ref

0….n

rico:Record → dct:created → rico:Date

rico:expressedDate

ODER

rico:normalizedDateValue, rico:certainty, rico:dateQualifier

dcterms:extent

The size or duration of the CHO.

<dcterms:extent>13 cm</dcterms:extent> (the width of an original object).

<dcterms:extent>34 minutes</dcterms:extent> (the duration of an audio file).

literal or ref

0….n

rico:Instantiation with type = physicalObject

ebucore:duration

dcterms:hasFormat

A resource related to the CHO that is substantially the same as the CHO but in another format.

<dcterms:hasFormat>http://upload.wikimedia.org/wikipedia/en/f/f3/Europeana_logo.png</dcterms:hasFor mat> for a png image file of the described tiff resource

Or as a link to a resource

<dcterms:hasFormat rdf:resource=“http://upload.wikimedia.org/wikipedia/en/f/f3/Europeana_logo.png’’/>

literal or ref

0….n

NA

NA

dcterms:hasPart

A resource that is included either physically or logically in the CHO. It is possible to use either dcterms:isPartOf or dcterms:hasPart to express relation between objects in a hierarchy. However in many cases (especially when a parent object has many children) it is preferable to usedcterms:isPartOf.

<dcterms:hasPart>Vol.2. Issue 1</dcterms:hasPart>.

literal or ref

0….n

NA

NA

dcterms:hasVersion

Another, later resource that is a version, edition or adaptation of the CHO demonstrating substantive changes in content rather thanformat.

<dcterms:hasVersion>The Sorcerer’s Apprentice (translation by Edwin Zeydel, 1955)</dcterms:hasVersion>. In this example the 1955 translation is a version of the describedresource.

literal or ref

0….n

NA

NA

dcterms:isFormatOf

Another resource that is substantially the same as the CHO but in another format.

<dcterms:isFormatOf>Europeana_logo.tiff</dcterms:isFormatOf>where the resource being described is a png image file.

literal or ref

0….n

NA

NA

dcterms:isPartOf

A resource in which the CHO is physically or logically included. This property can be used for objects that are part of a hierarchy and will be used to support an appropriate display in the portal. For that purpose it will be necessary to supply a reference as the value. See theTask Force report⁶on representing hierarchical entities. It is possible to use either dcterms:isPartOf or dcterms:hasPart to express relation between objects in a hierarchy. However in many cases (especially when a parent object has many children) it is preferable to use dcterms:isPartOf.

<dcterms:isPartOf>Crace Collection of Maps of London</dcterms:isPartOf>

Or link to parent object if part of a hierarchy of CHOs

<dcterms:isPartOf rdf:resource=“http://data.europeana.eu/item/08701/1B0BACAA44D5A807E43D9B411C9781AAD2F96E65”/>

literal or ref

0….n

rico:Record → rico:isPartOf → rico:RecordSet

rico:title

dcterms:isReferencedBy

Another resource that references, cites or otherwise points to the CHO.

<dcterms:isReferencedBy>Till, Nicholas (1994)Mozart and the Enlightenment: Truth, Virtue and Beauty inMozart’s Operas, W. W. Norton & Company</dcterms:isReferencedBy>

literal or ref

0….n

NA

NA

dcterms:isReplacedBy

Another resource that supplants , displaces, or supersedes the CHO.

<dcterms:isReplacedBy>http://dublincore.org/about/2009/01/05/bylaws/</dcterms:isReplacedBy> where the resource described is an older version(http://dublincore.org/about/2006/01/01/bylaws/)

or link

<dcterms:isReplacedBy rdf:resource=“http://dublincore.org/about/2009/01/05/bylaws/”/>

literal or ref

0….n

NA

NA

dcterms:isRequiredBy

Another related resource that requires the CHO to support its function, delivery or coherence

<isRequiredBy>http://www.myslides.com/myslideshow.ppt</isRequiredBy> where the image being described is required for an onlineslideshow.

literal or ref

0….n

NA

NA

dcterms:issued

Date of formal issuance or publication of the CHO. Europeana recommends date conforming to ISO 8601 starting with the year and with hyphens (YYYY-MMDD). NB: other EDM elements are relevant for expressing dates of different events in the life of the CHO: dc:date, dcterms:temporal and dcterms:created. Be careful and choose the most appropriate one!

<dcterms:issued>1993</dcterms:issued>

or create a reference to an instance of the TimeSpan class

<dcterms:issued rdf:resource=“http://semium.org/time/17xx_3_third”/> (late 18^thcentury)

literal or ref

0….n

rico:Record → dct:issued → rico:Date

rico:expressedDate

ODER

rico:normalizedDateValue, rico:certainty, rico:dateQualifier

dcterms:isVersionOf

Another, earlier resource of which the CHO is a version, edition or adaptation, demonstrating substantive changes in content rather thanformat.

<dcterms:isVersionOf>The Sorcerer’s Apprentice<dcterms:isVersionOf>. In this example The Sorcerer’s Apprentice (translation by Edwin Zeydel, 1955) is the resource beingdescribed.

literal or ref

0….n

NA

NA

dcterms:medium

The material or physical carrier of the CHO.

<dcterms:medium>metal</dcterms:medium>

literal or ref

0….n

rico:Instantiation with type physicalObject → rico:hasCarrierType → rico:CarrierType with rico:resultsFrom

schema:sameAs

Nur angereicherte Werte

dcterms:provenance

A statement of changes in ownership and custody of the CHO since its creation. Significant for authenticity, integrity and interpretation.

<dcterms:provenance>Donated to The National Library in 1965</dcterms:provenance>

literal or ref

0….n

NA

NA

dcterms:references

Other resources referenced, cited or otherwise pointed to by the CHO.

<dcterms:references>Honderd jaar Noorse schilderkunst </dcterms:references>

literal or ref

0….n

NA

NA

dcterms:replaces

A related resource that is supplanted, displaced, or superseded by the CHO.

<dcterms:replaces>http://dublincore.org/about/2006/01/01/bylaws/</dcterms:replaces> where the resource described is a newer version(http://dublincore.org/about/2009/01/05/bylaws/)

or link to resource

<dcterms:replaces rdf:resource=“http://dublincore.org/about/2006/01/01/bylaws/”/>

literal or ref

0….n

NA

NA

dcterms:requires

Another resource that is required by the described resource to support its function, delivery or coherence.

<dcterms:requires>http://ads.ahds.ac.uk/project/userinfo/css/oldbrowsers.css</dcterms:requires> where

the resource described is an HTML file athttp://ads.ahds.ac.uk/project/userinfo/digitalTextArchiving.html

literal or ref

0….n

NA

NA

dcterms:spatial

Spatial characteristics of the CHO. i.e. what the CHO represents or depicts in terms of space (e.g. a location, co-ordinate or place). Either dcterms:spatial or dc:type or dc:subject or dcterms:temporal must be provided; if more than one of these properties is available, please provide them all.

dcterms:spatial is used to record the place depicted in the CHO and other locations associated with it as opposed to edm:currentLocation which is used only to record the place where the CHO is currently held (e.g. a museum or gallery). Be careful to choose the most appropriate one!

<dcterms:spatial>Portugal</dcterms:spatial>

or create a reference to an instance of the Place class

<dcterms:spatial rdf:resource=“http://sws.geonames.org/2264397/”/>

literal or ref

0….n

rico:Record → dct:spatial → rico:Place

rico:Record → rdau:P60556 → rico:Place

rico:name

dcterms:tableOfContents

A listof sub-­units of the CHO.

<dcterms:tableOfContents>Chapter 1. Introduction, Chapter 2. History </dcterms:tableOfContents>

literal

0….n

NA

NA

dcterms:temporal

Temporal characteristics of the CHO. i.e. what the CHO is about or depicts in terms of time (e.g. a period,date or date range.) Either dcterms:temporal or dc:type or dc:subject or dcterms:spatial mustb e provided; if more than one of these properties is available, please provide them all.

Europeana recommends date conforming to ISO 8601 starting with the year and with hyphens (YYYY-MMDD). NB: other EDM elements are relevant for expressing dates of different events in the life of the CHO: dc:date, dcterms:created and dcterms:issued. Be careful and choose the most appropriate one!

<dcterms:temporal>Roman Empire</dcterms:temporal> or create a reference to an instance of the TimeSpan class

<dcterms:temporal rdf:resource=“http://semium.org/time/roman_empire”/>

literal or ref

0….n

rico:Record → dct:temporal → rico:Date

rico:expressedDate

ODER

rico:normalizedDateValue, rico:certainty, rico:dateQualifier

edm:currentLocation

The geographic location whose boundaries presently include the CHO. This location must have a position within an established positioning system: a location with coordinates or address or inside another location that has a position, such as a room within a (museum) building. Ideally this position should be provided with the value of the property, either by using a reference (to a Place entity) that has coordinates or an address attribute, or as a simple literal.

edm:currentLocation is used only to record the place where the CHO is currently held (e.g. a museum or gallery); dcterms:spatial is used to record the place depicted in the CHO and other locations associated with it. Be careful to choose the most appropriateone!

<edm:currentLocation rdf:resource=“http://sws.geonames.org/2950159”/> (Identifier for Berlin)

literal or ref

0….1

rico:Record → rico:heldBy → rico:CorporateBody with type memobaseInsititution

schema:sameAs

Wikidata URI

edm:hasMet

The identifier of an agent, a place, a time period or any other identifiable entity that the CHO may have “met” in its life.

<edm:hasMet rdf:resource=“http://viaf.org/viaf/96994048”/> (Identifier for William Shakespeare)

<edm:hasMet rdf:resource=“http://sws.geonames.org/6620265”/>(location identifier for Shakespeare’s Globetheatre.)

ref

0….n

NA

NA

edm:hasType

The identifier of a concept, or a word or phrase from a controlled vocabulary (thesaurus etc) giving the type of the CHO. E.g. Painting from the AAT thesaurus. This property can be seen as a super-property of e.g. dc:format or dc:type to support “What” questions.

<edm:hasType>Painting</edm:hasType>

ref or literal

0….n

NA

NA

weglassen, da dct:medium und dc:type schon verwendet werden?

edm:incorporates

The identifier of another resource that is incorporated in the described CHO. E.g. the movie “A Clockwork Orange” incorporates Rossini’s La Gazza Ladra” in its soundtrack.

<edm:incorporates rdf:resource=“http://www.identifier/IncorporatedResource”/>

ref

0….n

NA

NA

edm:isDerivativeOf

The identifier of another resource from which the described CHO has been derived. E.g. the identifier of Moby Dick when the Italian translation is the describedCHO.

<edm:isDerivativeOf rdf:resource=“http://www.identifier/SourceResource”/>

ref

0….n

NA

NA

edm:isNextInSequence

The identifier of the preceding object where both objects are part of the same overall resource. Use this for objects that are part of a hierarchy or sequence to ensure correct display in the portal.

<edm:isNextInSequence rdf:resource=“http://www.identifier/PrecedingResource”/>

ref

0….n

NA

NA

edm:isRelatedTo

The identifier or name of a concept or other resource to which the described CHO is related. E.g. Moby Dick is related to XIX Century literature. Cf dc:relation.

<edm:isRelatedTo>Literature</edm:isRelatedTo > Or link to resource

<edm:isRelatedTo rdf:resource=“http://www.eionet.europa.eu/gemet/concept?cp=4850”/>

ref or literal

0….n

NA

NA

evtl. später relevant für Filmwochenschau

edm:isRepresentationOf

The identifier of another object of which the described CHO is a representation. E.g. the identifier of the statue when the CHO being described is a painting of that statue.

<edm:isRepresentativeOf rdf:resource=“http://www.identifier/RepresentedResource”/>

ref

0….1

NA

NA

edm:isSimilarTo

The identifier of another resource to which the described CHO is similar.

<edm:isSimilarTo rdf:resource=“http://www.identifier/SimilarResource”/>

ref

0….n

NA

NA

edm:isSuccessorOf

The identifier of a resource to which the described CHO is a successor. E.g. “The Two Towers” is a successor of “Fellowship of theRing”.

<edm:isSuccessorOf rdf:resource=“http://dbpedia.org/resource/The_Fellowship_of_the_Ring”/>

ref

0….n

NA

NA

edm:realizes

If the CHO described is of type edm:PhysicalThing it may realize an information object. E.g. a copy of the Gutenberg publication realizes the Bible.

<edm:realizes rdf:resource=“http://www.identifier/PhysicalThing”/>

ref

0….n

NA

NA

edm:type

The value must be one of the types accepted by Europeana as it will support portal functionality: TEXT, VIDEO, SOUND, IMAGE, 3D. (For 3D, when applicable, use the value “3D-­PDF” in dc:format )

<edm:type>IMAGE</edm:type>(upper-case)

<edm:type>3D</edm:type>(upper-case)

literal

1….1

rico:Record

rico:type

Mapping:

• Film → VIDEO

• Foto → IMAGE

• Radio → SOUND

• Ton → SOUND

• Tonbildschau → ?

• TV → VIDEO

• Video → VIDEO

owl:sameAs

Use to point to your own (linked data) representation of the object, if you have already minted a URI identifier for it. It is also possible to provide URIs minted by third-­parties for the object.

<owl:sameAs rdf:resource=“http://www.identifier/SameResourceElsewhere”/>

ref

0….n

NA

NA

Relevant sobald wir eine linked data Schnittstelle haben

Property

Note

Value type

Card.

Memobase Entity

Memobase Attribute

Memobase Card.

Remarks

rdf:about

rico:Instantiation with type digitalObject → rico:identiedBy → rico:Identifier with type main

Für Vimeo:

rico:identifier

Daraus URL generieren:

https://media.memobase.ch/memo/[rico:identifier]/master

ebucore:locator

1

Beispiel: https://media.memobase.ch/memo/apf-001-1284-1/master

Beispiel Vimeo:

https://vimeo.com/128323563

dc:creator

For the creator of the web resource. If possible supply the identifier of the creator from an authority source. Repeat for multiplecreators.

<dc:creator xml:lang=“es”>Biblicoteca Nacional de España</dc:creator or create a reference to an instance of the Agent class

<dc:creator rdf:resource=“http://viaf.org/viaf/147143794/”/>

literal or ref

0….n

NA

NA

dc:description

Use for an account or description of this digital representation

<dc:description>Performance with Buccin trombone/>

literal or ref

0….n

NA

NA

dc:format

Use for the format of this digital representation. (Use the value “3D-­PDF” if appropriate.)

<dc:format>image/jpeg</dc:format>

literal or ref

0….n

rico:Instantiation with type digitalObject

ebucore:hasMimeType

0…1

dc:rights

Use for the name of the rights holder of this digital representation if possible or for more general rights information. Note the difference between this property and the mandatory, controlled edm:rights property below.

<dc:rights> Copyright © British Library Board</dc:rights>

literal or ref

0….n

NA

NA

auf Ebene rico:Record abgelget und zu edm:ProvidedCHO gemappt

dc:source

A related resource from which the Web resource is derived in whole or in part.

<dc:source>The name of the source video tape <dc:source>

literal or ref

0….n

NA

NA

dc:type

The nature or genre of the digital representation. Ideally the term(s) will be taken from a controlled vocabulary. dc:type should not be (strictly) identical to edm:type.

<dc:type>video</dc:type>

or create a reference to an instance of the Conceptclass

<dc:type rdf:about=“http://schema.org/VideoObject”>

literal or ref

0….n

NA

NA

alle vorhandenen Angaben schon auf Ebene CHO angegeben

dcterms:conformsTo

An established standard to which the web resource conforms.

<dcterms:conformsTo>W3C WCAG 2.0</dcterms:conformsTo> (web content accessibility guidelines).

literal or ref

0….n

NA

NA

dcterms:created

Date of creation of the Web resource. Europeana recommends date conforming to ISO 8601 starting with the yearandwith hyphens (YYYY-MMDD).

<dcterms:created>2010</dcterms:created>

or create a reference to an instance of the TimeSpan class

<dc:date rdf:resource=“http://semium.org/time/2010”/>

literal or ref

0….n

NA

NA

dcterms:extent

The size or duration of the digital resource.

<dcterms:extent>1h 26 min 41 sec</dcterms:extent>

literal or ref

0….n

rico:Instantiation with type digitalObject

ebucore:duration

0…1

dcterms:hasPart

A resource that is included either physically or logically in the web resource.

<dcterms:hasPart rdf:resource=“http://www.identifier/Part”/>

ref

0….n

NA

NA

dcterms:isFormatOf

Another resource that is substantially the same as the web resource but in another format.

<dcterms:isFormatOf>http://upload.wikimedia.org/wikipedia/en/f/f3/Europeana_logo.png</dcterms:isForm atOf> for a png image file of the described tiff web resource.

Or as a link to a resource

<dcterms:isFormatOf rdf:resource=“http://upload.wikimedia.org/wikipedia/en/f/f3/Europeana_logo.png”/>

literal

0….n

NA

NA

dcterms:isPartOf

A resource in which the WebResource is physically or logically included. This property can be used for web resources that are part of a hierarchy. Hierarchies can be represented as hierarchies of ProvidedCHOs or hierarchies of web resources but not both at the same time. See theTask Force report⁹on representing hierarchical entities.

<dcterms:isPartOf rdf:resource=“http://data.europeana.eu/item/08701/1B0BACAA44D5A807E43D9B411C9781AAD2F96E65”/>

ref

0….n

NA

NA

dcterms:isReferencedBy

A related resource that references, cites, or otherwise points to the described resource. In a IIIF implementation, dcterms:isReferencedBy can be used to connect a edm:WebResource to a IIIF manifest¹⁰URI.

<dcterms:isReferencedBy rdf:resource="http://dams.llgc.org.uk/iiif/2.0/1294670/manifest.json"/>

literal or ref

0…n

NA

NA

dcterms:issued

Date of formal issuance or publication of the web resource. Europeana recommends date conforming to ISO 8601 startingwith the yearandwith hyphens (YYYY-MMDD).

<dcterms:issued>1999</dcterms:issued>

or create a reference to an instance of the TimeSpan class

<dcterms:issued rdf:resource=“http://semium.org/time/2010”/>

literal or ref

0….n

NA

NA

edm:isNextInSequence

Where one CHO has several web resources, shown by multiple instances of the edm:hasView property on the ore:Aggregation this property can be used to show the sequence of the objects. Each web resource (apart from the first in the sequence) should use this property to give the URI of the preceding resource in the sequence.

<edm:isNextInSequence rdf:resource=“http://data.europeana.eu/item2020601/9A3907CB46B651DE91621933ECC31EC1DC52B33C”/> links to the web resource for page 2 of a digitised diary from the WebResource for page 3.

ref

0….n

NA

NA

edm:rights

The value in this element will indicate the copyright, usage and access rights that apply to this digital representation. It is strongly recommended that a value is supplied for this property for each instance of a web resource. The rights statement specified at the level of the web resource will ‘override’ the statement specified at the level of the aggregation.

The value in this element is a URI taken from the set of those defined for use in Europeana. A list of these can befoundathttps://pro.europeana.eu/available-rights-statements. Note: rights statements must be exactly as specified there, which means in many cases that they must start with http and not https.

<edm:rights rdf:resource=“http://creativecommons.org/publicdomain/mark/1.0/”/>

<edm:rights rdf:resource=“http://rightsstatements.org/vocab/InC/1.0/”/>

Or create a reference to an instance of the cc:License class where additional details of the rights can be provided (such as an expiry date for therestrictions):

http://rightsstatements.org/vocab/NoC-NC/1.0/or

<edm:rights rdf:resource="#statement_3000095353971"/>

ref

0….1

rico:Instantiation with type digitalObject → rico:regulatedBy → rico:Rule with type usage

schema:sameAs

1

owl:sameAs

Provide the URI of another web representation of the same resource.

<owl:sameAs rdf:resource=”urn:soundcloud:150424305”

ref

0….n

TBD

TBD

URL Institution?

Property

Note

Value type

Card.

Memobase Entity

Memobase Attribute

Memobase Card.

Remarks

rdf:about

rico:Record → rico:identifiedBy → rico:Identifier with type main

rico:identifier

Daraus URL generieren

https://memobase.ch/object/[rico:identifier]

1

Beispiel: https://memobase.ch/object/apf-001-1284

edm:aggregatedCHO

The identifier of the source object e.g. the Mona Lisa itself. This could be a full linked open data URI or an internal identifier.

<edm:aggregatedCHO rdf resource=“#UEDIN:214”/>

ref

1….1

rico:Record → rico:identifiedBy → rico:Identifier with type main

rico:identifier

Daraus URL generieren

https://memobase.ch/record/[rico:identifier]

entspricht ID des CHO

edm:dataProvider

The name or identifier of the data provider of the object (i.e. the organisation providing data to an aggregator). Identifiers will not be available until Europeana has implemented its Organization profile¹¹.

In the case of the data provider Zuidwestbrabants Museum, which delivers data through Erfgoedplus.be to LoCloud, the properties would look likethis:

<edm:dataProvider>Zuidwestbrabants Museum</edm:dataProvider>

<edm:intermediateProvider>Erfgoedplus.be</edm:intermediateProvider>

<edm:provider>LoCloud</edm:provider>

literal or ref

1….1

rico:Record → rico:heldBy → rico:CorporateBody with type memobaseInsititution

rico:name

Name der Instiution

edm:hasView

The URL of a web resource which is a digital representation of the CHO. This may be the source object itself in the case of a born digital cultural heritage object.

edm:hasView should only be used where there are several views of the CHO and one (or both) of the mandatory edm:isShownAt or edm:isShownBy properties have already been used. It is for cases where one CHO has several views of the same object. (e.g. a shoe and a detail of the label of the shoe)

<edm:hasView rdf:resource="http://www.mimo-db.eu/media/UEDIN/VIDEO/0032195v.mpg"/>

<edm:hasView rdf:resource="http://www.mimo-db.eu/media/UEDIN/AUDIO/0032195s.mp3"/>

ref

0….n

NA

NA

edm:isShownAt

The URL of a web view of the object in full information context. An edm:isShownAt must be provided. If there is no edm:isShownAt for an object, there must be a edm:isShownBy. If both are available, provide both the use of edm:isShownBy is preferred.

<edm:isShownAt rdf:resource="http://www.mimo-db.eu/UEDIN/214"/>

ref

0….1

rico:Record → rico:identifiedBy → rico:Identifier with type main

rico:identifier

Daraus URL generieren

https://memobase.ch/object/[rico:identifier]

1

Link zu Memobase Oberfläche

Beispiel: https://memobase.ch/object/apf-001-1284

edm:isShownBy

The URL of a web view of the object. An edm:isShownBy must be provided. If there is no edm:isShownBy for an object, there must be a edm:isShownAt. The use of edm:isShownBy is preferred. Europeana generates previews for any direct link to an image file. See Europeana Portal Image Guidelines¹²for information regarding the specifications of previews.

<edm:isShownBy rdf:resource="http://www.mimo-db.eu/media/UEDIN/IMAGE/0032195c.jpg"/>

ref

0….1

rico:Instantiation with type digitalObject → rico:identiedBy → rico:Identifier with type main

Für Vimeo:

rico:identifier

Daraus URL generieren:

https://media.memobase.ch/memo/[rico:identifier]/master

ebucore:locator

1

Direkter Link zu Medienobjekt, entspricht ID der WebResource

Vimeo: direkter Link

edm:object

The URL of a representation of the CHO which will be used for generating previews for use in the Europeana portal. This may be the same URL as edm:isShownBy. See Europeana Portal Image Guidelines for information regarding the specifications of previews. This must be an image, even if it is for a sound object.

<edm:object rdf:resource="http://www.mimo-db.eu/media/UEDIN/IMAGE/0032195c.jpg"/>

ref

0….1

Wenn rico:Record type Foto

rico:Instantiation with type digitalObject → rico:identifiedBy → rico:Identifier with type main

Sonst:

rico:Instantiation with type digitalObject → rico:identifiedBy → rico:Identifier with type main

rico:identifier

Daraus URL generieren:

https://media.memobase.ch/memo/[rico:identifier]/master

rico:identifier

Daraus URL generieren:

https://media.memobase.ch/memo/[rico:identifier]-poster

1

Link für Preview

Bild: identisch wie isShownBy

Video/Audio x-poster

Beispiel:

https://media.memobase.k8s.unibas.ch/memo/apf-001-1090-1-poster

edm:provider

The name or identifier of the provider of the object (i.e. the organisation providing data directly to Europeana). Identifiers will not be available until Europeana has implemented its Organization profile.

In the case of the provider LoCloud, which collects data from the data provider Zuidwestbrabants Museum through Erfgoedplus.be, the properties would look like this:

<edm:dataProvider>Zuidwestbrabants Museum</edm:dataProvider>

<edm:intermediateProvider>Erfgoedplus.be</edm:intermediateProvider><edm:provider>LoCloud</ed m:provider>

<edm:provider>LoCloud</edm:provider>

literal or ref

1….1

fixer Wert: Memoriav

1

dc:rights

Ideally this should be applied to the edm:WebResource or the edm:ProvidedCHO. It is included here for the conversion of data from ESE where it is not known which object the rights apply to.

literal

0….n

NA

NA

geben wir bei edm:WebResource und edm:ProvidedCHO an

edm:rights

This is a mandatory property and the value given here should be the rights statement that applies to the digital representation as given (for example) in edm:object or edm:isShownAt/By, when these resources are not provided with their own edm:rights (see edm:rights documentation). The value for the rights statement in this element is a URI taken from the set of those defined for use in Europeana at http://pro.europeana.eu/available-rights-statements. Note: rights statements must be exactlyas specified there, which means in many cases that they must start with http and nothttps.

The rights statement given in this property will also by default apply to the previews used in the portal and will support portal search and display functionality.

Where there are several web resources attached to one edm:ProvidedCHO the rights statement given here will be regarded as the “reference” value for all the web resources. Therefore a suitable value should be chosen with care if the rights statements vary between different resources. In fact in such cases Europeana encourages the provision of separate rights statements for each individual web resource.Forexample,alow-resolutionofaJPEGfilecouldbeCC-BY,whilethehighresolutionversionoravideoshowingtheobjectwouldbeCC-BY-NC.Insuchcasestherightsstatementsgivenforthe individual web resources would ‘override’ the one specified at the ore:Aggregation level. Any other associated web resources would still be governed by the edm:rights of theore:Aggregation.

<edm:rights rdf:resource=“http://creativecommons.org/publicdomain/mark/1.0/”/>

<edm:rights rdf:resource=“http://rightsstatements.org/vocab/InC/1.0/”/>

Or create a reference to an instance of the cc:License class where additional details of the rights can be provided (such as an expiry date for therestrictions):

http://rightsstatements.org/vocab/NoC-NC/1.0/ or <edm:rights rdf:resource="#statement_3000095353971"/>

ref

1….1

rico:Instantiation with type digitalObject → rico:regulatedBy → rico:Rule with type usage

schema:sameAs

1

identisch zu edm:rights
bei WebRessource

edm:ugc

This is a mandatory property for objects that are user generated or user created that have been collected by crowdsourcing or project activity. The property is used to identify such content and can only take the value “true” (lowercase).

<edm:ugc>true<edm:ugc>

literal

0….1

NA

NA

edm:intermediateProvider

The name or identifier of the intermediate organization that selects, collates, or curates data from a Data Provider that is then aggregated by a Provider from which Europeana harvests. The Intermediate Provider must be distinct from both the Data Provider and the Provider in the data supply chain. Identifiers will not be available until Europeana has implemented its Organization profile.

In the case of the Erfgoedplus.be, which collects data from Zuidwestbrabants Museum and provides it to LoCloud, the properties would look likethis:

<edm:dataProvider>Zuidwestbrabants Museum</edm:dataProvider>

<edm:provider>LoCloud</edm:provider>

<edm:intermediateProvider>Erfgoedplus.be</edm:intermediateProvider>

literal or ref

0…n

NA

NA

nicht notwendig

Property

Note

Value type

Card.

skos:prefLabel

The preferred form of the name of the agent. Although the maximum number of occurrences is set at 1, it can be interpreted as 1 per language tag. At least one skos:prefLabel SHOULD be provided. Several prefLabels with languages tags are strongly recommended for language variants and translations.

<skos:prefLabel xml:lang="fr">Courtois neveu aîné</skos:prefLabel>

<skos:prefLabel xml:lang="en">Courtois’eldest nephew</skos:prefLabel>

literal

0…1

skos:altLabel

Alternative forms of the name of the agent. This is a recommended property for this class.

<skos:altLabel xml:lang="en">Courtois</skos:altLabel>

<skos:altLabel xml:lang="fr">Augte. Courtois aîné</skos:altLabel>

literal

0….n

skos:note

A note about the agent e.g. biographical notes.

<skos:note> Courtois neveu aîné started a company of the same name manufacturing brass instruments in Paris in1803</skos:note>

literal

0….n

dc:date

A significant date associated with the Agent. Europeana recommends date conforming to ISO8601 startingwith the yearandwith hyphens (YYYY-MMDD).

<dc:date>1803</dc:date/>

literal orref

0….n

dc:identifier

An identifier of the agent.

<dc:identifier>http://viaf.org/viaf/96994048</dc:identifier>

literal

0….n

dcterms:hasPart

Reference to an Agent that is part of the Agent being described (e.g. a part of a corporation).

<dcterms:hasPart rdf:resource=“http://identifier/partOfCorporation/”>

ref

0….n

dcterms:isPartOf

Reference to an agent that the described agent is part of.

<dcterms:isPartOf rdf:resource=“http://identifier/parentCorporation/”>

ref

0….n

edm:begin*

The date the agent was born/established. Europeana recommends date conforming to ISO 8601 startingwith the yearandwith hyphens (YYYY-MMDD).

<edm:begin>1795</edm:begin>

literal

0….1

edm:end*

The date the agent died/terminated. Europeana recommends date conforming to ISO 8601 starting with the yearandwith hyphens (YYYY-MMDD).

<edm:end>1885</edm:end>

literal

0….1

edm:hasMet

Reference to another entity which the agent has “met” in a broad sense. For example a reference to a Place class

<edm:hasMet rdf:resource=“http://sws.geonames.org/6620265/”>

ref

0….n

edm:isRelatedTo

Reference to other entities, particularly other agents, with whom the agent is related in a generic sense.

<edm:isRelatedTo rdf:resource=“http://identifier/relatedAgent/”>

ref

0….n

foaf:name

The name of the agent as a simple textual string.

<foaf:name>Auguste Courtois</foaf:name>

literal

0….n

rdaGr2:biographicalInfo rmation

Information pertaining to the life or history of the agent.

<rdaGr2:biographicalInformation>Courtois neveu aîné started a company of the same name manufacturing brass instruments in Paris in1803</rdaGr2:biographicalInformation>

literal

0….n

rdaGr2:dateOfBirth

The date the agent (person) was born. Europeana recommends date conforming to ISO 8601 startingwith the yearandwith hyphens (YYYY-MMDD).Thisis arecommendedpropertyforthisclass.

<rdaGr2:dateOfBirth>1795</rdaGr2:dateOfBirth>

literal

0….1

rdaGr2:dateOfDeath

The date the agent (person) died. Europeana recommends date conforming to ISO 8601 starting with the yearandwith hyphens (YYYY-MMDD).Thisis arecommendedpropertyforthisclass.

<rdaGr2:dateOfDeath>1895</rdaGr2:dateOfDeath>

literal

0….1

rdaGr2:dateOfEstablishment

The date on which the agent (corporate body) was established or founded.

<rdaGr2:dateOfEstablishment>1795</rdaGr2:dateOfEstablishment>

literal

0….1

rdaGr2:dateOfTermination

The date on which the agent (corporate body) was terminated or dissolved.

<rdaGr2:dateOfTermination>1895</rdaGr2:dateOfTermination>

literal

0….1

rdaGr2:gender

The gender with which the agentidentifies.

<rdaGr2:gender>Female</rdaGr2:gender>

literal

0….1

rdaGr2:placeOfBirth

The town, city, province, state, and/or country in which a person was born.

<rdaGr2:placeOfBirth>Lusaka, Northern Rhodesia</rdaGr2:placeOfBirth>

<rdaGr2:placeOfBirth rdf:resource=”http://sws.geonames.org/909137/”/>

literal orref

0….1

rdaGr2:placeOfDeath

The town, city, province, state, and/or country in which a person died.

<rdaGr2:placeOfDeath>London, United Kingdom</rdaGr2:placeOfDeath>

<rdaGr2:placeOfDeath rdf:resource=“http://sws.geonames.org/2635167/”/>

literal orref

0….1

rdaGr2:professionOrOccupation

The profession or occupation in which the agent works or has worked.

<rdaGr2:professionOrOccupation>Instrument Maker</rdaGr2:professionOrOccupation>

literal orref

0….n

owl:sameAs

Another URI of the same agent.

<owl:sameAs rdf:resource=“http://www.identifier/sameResourceElsewhere”/>

ref

0….n

Property

Note

Value type

Card.

wgs84_pos:lat

The latitude of a spatial thing (decimal degrees). This is a recommended property for this class.

<wgs84_pos:lat>51.5075</wgs84_pos:lat>

Floating point¹⁴

0….1

wgs84_pos:long

The longitude of a spatial thing (decimal degrees). This is a recommended property for this class.

<wgs84_pos:long>-0.1231</wgs84_pos:long>

Floating point¹⁴

0….1

wgs84_pos:alt

The altitude of a spatial thing (decimal metres above the reference)

<wgs84_pos:alt>21</wgs84_pos:alt>

Floating point¹⁴

0….1

skos:prefLabel

The preferred form of the name of the place. Although the maximum number of occurrences is set at 1, it can be interpreted as 1 per language tag. At least one skos:prefLabel SHOULD be provided. Several prefLabels with languages tags are strongly recommended for language variants and translations.

<skos:prefLabel xml:lang="en">London</skos:prefLabel>

literal

0….1

skos:altLabel

Alternative forms of the name of the place.

<skos:altLabel xml:lang="en">Greater London</skos:altLabel>

literal

0….n

skos:note

Information relating to the place.

<skos:note xml:lang="en">Pop. 21m</skos:note>

literal

0….n

dcterms:hasPart

Reference to a place that is part of the place being described.

<dcterms:hasPart rdf:resource=“http://sws.geonames.org/2643741/”/> (City of London)

ref

0….n

dcterms:isPartOf

Reference to a place that the described place is part of.

<dcterms:isPartOf rdf:resource=“http://sws.geonames.org/2635167/”/> (United Kingdom)

ref

0….n

edm:isNextInSequence

Can be used to represent a sequence of Place entities over time e.g. the historical layers of the city of Troy. Use this for objects that are part of a hierarchy or sequence to ensure correct display in theportal.

ref

0….n

owl:sameAs

URI of a Place

<owl:sameAs rdf:resource=“http://sws.geonames.org/2635167/”/>(London)

ref

0….n

Property

Note

Value type

Card.

skos:prefLabel

The preferred form of the name of the timespan or period. Although the maximum number of occurrences is set at 1, it can be interpreted as 1 per language tag. At least one skos:prefLabel SHOULD be provided. Several prefLabels with languages tags are strongly recommended for language variants and translations.

<skos:prefLabel xml:lang=“en”>Roman Empire</skos:prefLabel>

literal

0….1

skos:altLabel

Alternative forms of the name of the timespan or period.

<skos:altLabelxml:lang=“fr”>Empire romain (27 avantJ.-C.-476 aprèsJ.-C.)</skos:altLabel >

literal

0….n

skos:note

Information relating to the timespan or period.

<skos:note>TheRoman Empire(Latin:Imperium Romanum) was the post-Republican period of the ancient Roman civilization, characterised by an autocratic form of government and large territorial holdings around the Mediterranean in Europe, Africa, and Asia.</skos:note>

literal

0….n

dcterms:hasPart

Reference to a timespan which is part of the described timespan.

ref

0….n

dcterms:isPartOf

Reference to a timespan of which the described timespan is a part.

ref

0….n

edm:begin

The date the timespan started. Europeana recommends date conforming to ISO 8601 starting with the year and with hyphens (YYYY-MMDD).Providing edm:begin in combination with edm:end is recommended for this class.

<edm:begin>27 BC</edm:begin>

literal

0….1

edm:end

The date the timespan finished. Europeana recommends date conforming to ISO 8601 starting with the year and with hyphens (YYYY-MMDD).Providing edm:end in combination with edm:begin is recommended for this class.

<edm:end>476 AD</edm:end>

literal

0….1

edm:isNextInSequence

Can be used to represent a sequence of Time periods. Use this for objects that are part of a hierarchy or sequence to ensure correct display in theportal.

<edm:isNextInSequence rdf:resource=“http://semium.org/time/roman_republic”/> (The Roman Empire was preceded by the RomanRepublic)

ref

0….n

owl:sameAs

The URI of a timespan

<owl:sameAs rdf:resource=“http://semium.org/time/roman_empire”/>

ref

0….n

Property

Note

Value type

Card.

skos:prefLabel

The preferred form of the name of the concept. Although the maximum number of occurrences is set at 1, it can be interpreted as 1 per language tag. At least one skos:prefLabel SHOULD be provided. Several prefLabels with languages tags are strongly recommended for language variants and translations.

<skos:prefLabel xml:lang="fr">Buccin</skos:prefLabel>

<skos:prefLabel xml:lang="de">Buccin</skos:prefLabel>

<skos:prefLabel xml:lang="nl">Buccin</skos:prefLabel>

literal

0….1

skos:Concpet

skos:prefLabel

skos:altLabel

Alternative forms of the name of the concept. Recommended unless several prefLabel are already given with different language tags (altLabel is not suitable for translations ofprefLabel).

<skos:altLabel xml:lang="en">Buccin</skos:altLabel>

literal

0….n

skos:broader

The identifier of a broader concept in the same thesaurus or controlled vocabulary.

<skos:broader rdf:resource=“http://www.mimo-db.eu/InstrumentsKeywords/4369_1”/>

ref

0….n

skos:narrower

The identifier of a narrower concept.

<skos:narrower rdf:resource=“http://narrower.term/”/>

ref

0….n

skos:related

The identifier of a related concept

<skos:related rdf:resource=“http://related.term/”/

ref

0….n

skos:broadMatch skos:narrowMatch skos:relatedMatch

The identifier of a broader, narrower or related matching concepts from other concept schemes.

<skos:broadMatch rdf:resource=“http://broadMatch.term/”/>

<skos:narrowMatchrdf:resource=“http://narrowMatch.term/”/>

<skos:relatedMatchrdf:resource=“http://relatedMatch.term/”/>

ref

0….n

skos:exactMatch skos:closeMatch

The identifier of close or exactly matching concepts from other concept schemes.

<skos:exactMatch rdf:resource=“http://exactMatch.term/”/>

<skos:closeMatch rdf:resource=“http://closeMatch.term/”/>

ref

0….n

skos:note

Information relating to the concept.

<skos:note>The buccin is a visually distinctive trombone popularized in military bands in France between 1810–1845 which subsequently faded intoobscurity.</skos:note>

literal

0….n

skos:notation

The notation in which the concept is represented. This may not be words in natural language for some knowledge organisation systems e.g.algebra

<skos:notation rdf:datatype=“http://www.w3.org/2001/XMLSchema#int”>123</skos:notation>

string (+rdf: datatype attribute)

0….n

skos:inScheme

The URI of a concept scheme

ref

0….n

odrl:inheritFrom

ID of a base rights statement from which the described License is derived. This value must come for a list of statements controlled byEuropeana.

<odrl:inheritFrom rdf:resource=“http://rightsstatements.org/vocab/NoC-NC/1.0/”/>

ref

1….1

cc:deprecatedOn

The date that the license expires, as it has been described, which implies among other things the expiration of the restrictions specified by the license.

<cc:deprecatedOnrdf:datatype=”http://www.w3.org/2001/XMLSchema-datatypes#date”>2029-06-01</cc:deprecatedOn>

Literal

expressed as an XML date type

0….1