compared with
Current by Vladimir Alexiev
on May 28, 2013 17:43.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History
{excerpt}YCBA data conversion from LIDO XML to CIDOC CRM RDF{excerpt}

{toc} {children:excerpt=true}

h1. Introduction
Source: LIDO + OAI-PMH XML Examples:
* [^oai-tms.ycba.yale.edu-499.xml]
* [^oai-tms.ycba.yale.edu-757.xml]

Target: CIDOC CRM RDF Examples (Pubby HTML pages):
* [http://collection.britishart.yale.edu/id/page/object/499]
* [http://collection.britishart.yale.edu/id/page/object/757]

Conventions:
- Many of the code fragments below are Turtle, I've converted RDF->Turtle using [http://any23.org]
- DO NOT use Rich Text editing, edit only the Wiki Markup. Do not fall into the fruit salad trap ;-)
- Outstanding issues: search for #! in code, (!) in text.
When you fix an issue, remove these markers but leave the explanatory notes as a guidance


h2. Object - work of art
Identifier = Object ID, Location, Title, Credit Line, Dimensions, Current Repository (building physical and legal custody keeper), Department (association?)
Documented (images, lido ID - admin data?), rights to object, rights to images of object, link to web page)

h3. Labels
- Why do we use double colon :: in the rdfs:label and P3_has_note? Do we need to for indexing in Lucene?
-- OWLIM Lucene indexes just the words, :: doesn't matter. But I kind of like it, it separates the parts of the "display wrap"
- Using rdfs:label vs crm:P3_has_note vs skos:prefLabel
-- rdfs:label: primary string label of a node, eg object title, artist name, dimension "display wrap"
-- skos:prefLabel: primary string label of a SKOS thesaurus node. (This is a sub-property, so it infers rdfs:label)
-- crm:P3_has_note: any additional label/note

h3. Dimensions

LIDO
{code}
<lido:objectMeasurementsWrap>
<lido:objectMeasurementsSet>
<lido:displayObjectMeasurements>78 1/4 x 48 1/8 inches (198.8 x 122.2 cm)</lido:displayObjectMeasurements>
<lido:objectMeasurements>
<lido:measurementsSet>
<lido:measurementType>height</lido:measurementType>
<lido:measurementUnit>cm</lido:measurementUnit>
<lido:measurementValue>198.8</lido:measurementValue>
</lido:measurementsSet>
<lido:measurementsSet>
<lido:measurementType>width</lido:measurementType>
<lido:measurementUnit>cm</lido:measurementUnit>
<lido:measurementValue>122.2</lido:measurementValue>
</lido:measurementsSet>
<lido:extentMeasurements>Support (PTG)</lido:extentMeasurements>
<lido:qualifierMeasurements/>
</lido:objectMeasurements>
</lido:objectMeasurementsSet>
</lido:objectMeasurementsWrap>
{code}

RDF: represented in a structured way (with two dimension nodes: object/499/width and object/499/height)
{code}
<http://collection.britishart.yale.edu/id/object/499>
crm:P43_has_dimension
<http://collection.britishart.yale.edu/id/object/499/height> ,
<http://collection.britishart.yale.edu/id/object/499/width> .

<http://collection.britishart.yale.edu/id/object/499/height>
a crm:E54_Dimension ; # OWLIM RDFS will infer this type from P43_has_dimension
#! crm:P2_has_type <thesaurus/dimension/height>;
crm:P3_has_note "Dimension :: 198.8 cm" ; #! Use rdfs:label, and be more specific in the note
#! rdfs:label "Height :: 198.8 cm" ;
crm:P91_has_unit <http://qudt.org/vocab/unit#Centimeter> ;
crm:P90_has_value "198.8" . #! add type ^^xsd:double

<http://collection.britishart.yale.edu/id/object/499/width>
a crm:E54_Dimension ;
crm:P3_has_note "Dimension :: 122.2 cm" ;
crm:P91_has_unit <http://qudt.org/vocab/unit#Centimeter> ;
crm:P90_has_value "122.2" .
{code}

- (!) lido:displayObjectMeasurements
If you put this display wrap at the object level, use P3_has_note since that's not the primary label:
{code}<object> crm:P3_has_note "Dimensions :: 78 1/4 x 48 1/8 inches (198.8 x 122.2 cm)"{code}
- (!) lido:extentMeasurements
This says which object part was measured. You need to somehow group the two E54_Dimensions, then map this to a P2_has_type. Alternatives:
-- (complicated) Make an object part "Support"
-- (better) Use E16_Measurement (see this diagram [measurement@crmg]!).
Note that P43 is a shortcut of the "long-cut" path P39i/P40, i.e. P43_has_dimension = P39i_was_measured_by/P40_observed_dimension, and we state both:
{code}
<object> crm:P39i_was_measured_by <object/measurement>;
crm:P43_has_dimension <object/height>, <object/width>.

<object/measurement> a crm:E16_Measurement;
crm:P2_has_type <thesaurus/measurement/support-PTG>; # better than string "Support (PTG)"
rdfs:label "Dimensions :: 78 1/4 x 48 1/8 inches (198.8 x 122.2 cm)"; # Put this display wrap here, or at object level
P40_observed_dimension <object/height>, <object/width>.
{code}

h3. Inventory Number
LIDO (part of lido:repositorySet lido:type="current")
{code}
<lido:workID lido:type="inventory number">B1979.20</lido:workID>
{code}

RDF
{code}
<http://collection.britishart.yale.edu/id/page/object/499/identifier>
#! !!!!!! You must not use "page" in the URI !!!!!!! Read about "CoolURIs" and 303-redirects
#! If that's inventory-number, better use URI <http://collection.britishart.yale.edu/id/object/499/inventory-number> to allow more identifiers
a crm:E42_Identifier ;
crm:P2_has_type <http://collection.britishart.yale.edu/id/thesaurus/identifier/inventory-number> ;
crm:P3_has_note B1979.20 . #! Oops, invalid Turtle. Where are the quotes?

#! add this to connect it
<http://collection.britishart.yale.edu/id/page/object/499>
crm:P1_is_identified_by <http://collection.britishart.yale.edu/id/thesaurus/identifier/inventory-number>.
#? or P48_has_preferred_identifier if that's the "main" identifier

#! !! It may not be a good idea to embed the thesaurus entries used by an object into the object's RDF.
#! I think you better emit the thesaurus ONCE
<http://collection.britishart.yale.edu/id/thesaurus/identifier/inventory-number>
a crm:E55_Type ;
crm:P3_has_note "inventory number" . #! skos:prefLabel
#! skos:inScheme
{code}
- [http://collection.britishart.yale.edu/id/thesaurus/indetifier/inventory-number] was misspelled
- This caused an invalid URI {{<crm:E55_Type>}} (prefixed yet enclosed in angle brackets)
{code:xml}<rdf:Description rdf:about="http://collection.britishart.yale.edu/id/thesaurus/indetifier/inventory-number">
<rdf:type rdf:resource="crm:E55_Type" />
</rdf:Description>{code}

h3. Legal Body
LIDO (part of lido:repositorySet lido:type="current")
{code}
<lido:legalBodyName>
<lido:appellationValue>Yale Center for British Art</lido:appellationValue>
</lido:legalBodyName>
{code}
RDF

{code}
...
{code}
- This causes a blank node that is not connected to anything (same for other legal bodies) [http://collection.britishart.yale.edu/id/legal_body/500303557]
{code:xml}<crm:P1_is_identified_by rdf:resource="500303557" />{code}


h3. Images

LIDO
{code}
<lido:resourceWrap>
<lido:resourceSet>
<lido:resourceRepresentation lido:type="thumb">
<lido:linkResource lido:formatResource="jpg">http://deliver.odai.yale.edu/content?objectId=499&repositoryCode=YCBA&objectType=2&formatId=1</lido:linkResource>
</lido:resourceRepresentation>
<lido:resourceRepresentation lido:type="large">
<lido:linkResource lido:formatResource="jpg">http://deliver.odai.yale.edu/content?objectId=499&repositoryCode=YCBA&objectType=2&formatId=3</lido:linkResource>
</lido:resourceRepresentation>
<lido:resourceRepresentation lido:type="list">
<lido:linkResource lido:formatResource="jpg">http://deliver.odai.yale.edu/info?objectId=499&repositoryCode=YCBA&objectType=2&output=jsonp&callback=?</lido:linkResource>
</lido:resourceRepresentation>
<lido:resourceRepresentation lido:type="original">
<lido:linkResource lido:formatResource="tif">http://deliver.odai.yale.edu/content?objectId=499&repositoryCode=YCBA&objectType=2&formatId=6</lido:linkResource>
</lido:resourceRepresentation>
<lido:resourceType>
<lido:term>digital image</lido:term>
</lido:resourceType>
<lido:resourceSource lido:type="holder of image">
<lido:legalBodyName>
<lido:appellationValue>Yale Center for British Art</lido:appellationValue>
</lido:legalBodyName>
</lido:resourceSource>
<lido:rightsResource>
<lido:rightsHolder>
<lido:legalBodyID lido:type="URL">http://hdl.handle.net/10079/w6m90dq</lido:legalBodyID>
<lido:legalBodyName>
<lido:appellationValue>Yale Center for British Art</lido:appellationValue>
</lido:legalBodyName>
</lido:rightsHolder>
</lido:rightsResource>
</lido:resourceSet>
</lido:resourceWrap>
{code}
RDF

{code}
<http://collection.britishart.yale.edu/id/object/499/images>
 a crm:E31_Document ;
crm:P70_is_documented_in
<http://collection.britishart.yale.edu/id/object/499/images/large> ,
<http://collection.britishart.yale.edu/id/object/499/images/list> ,
<http://collection.britishart.yale.edu/id/object/499/images/original> ,
<http://collection.britishart.yale.edu/id/object/499/images/thumb> .

<http://collection.britishart.yale.edu/id/object/499/images/large>
a crm:E55_Type ;
crm:P1_is_identified_by "http://deliver.odai.yale.edu/content?objectId=499&repositoryCode=YCBA&objectType=2&formatId=3" .


<http://collection.britishart.yale.edu/id/object/499/images/list>
...


<http://collection.britishart.yale.edu/id/object/499/images/original>
...


<http://collection.britishart.yale.edu/id/object/499/images/thumb>
...
{code}

h2. Subject Terms (is_about)
Geographical (Getty TGN) or Concepts (Getty AAT concepts can be keywords or people).
(?) I thought people are in ULAN

There are two types of terms we have Art and Architecture Thesauri (AAT) and Thesauri of Geographical Names (TGN). These are based on Getty Vocab and contain Getty IDs. We also have our own terms that would not fit Getty and we provide for these TMS IDs. We also identify as many textural entries / concepts as we can with an ID for example "provenance, exhibition history, etc."

h3. TGN Places

LIDO
{code}
<lido:subjectSet>
<lido:subject lido:type="geographicName">
<lido:subjectPlace>
<lido:place>
<lido:placeID lido:source="TGN" lido:type="local">tgn7008591</lido:placeID>
<lido:namePlaceSet>
<lido:appellationValue>United Kingdom</lido:appellationValue>
</lido:namePlaceSet>
<lido:gml>
<gml:Point>
<gml:coordinates>54.0000, -4.5000</gml:coordinates>
</gml:Point>
</lido:gml>
</lido:place>
</lido:subjectPlace>
</lido:subject>
</lido:subjectSet>
{code}

RDF
{code}
<http://collection.britishart.yale.edu/id/getty/tgn/7002445>
a skos:Place , crm:E55_Type ;
#! You must mean skos:Concept and crm:E53_Place
crm:P87_is_identified_by <http://collection.britishart.yale.edu/id/tgn/7002445/coordinates> ;
wgs84_pos:location <http://collection.britishart.yale.edu/id/tgn/7002445/location> ;
crm:label "England" . #! no such property

<http://collection.britishart.yale.edu/id/tgn/7002445/coordinates>
a crm:E47_Spatial_Coordinates ;
crm:P90_has_value "53.0000, -2.0000" .
<http://collection.britishart.yale.edu/id/tgn/7002445/location>
a wgs84_pos:SpatialThing ;
wgs84_pos:lat "53.0000" ;
wgs84_pos:long "-2.0000" .
{code}
- re [http://collection.britishart.yale.edu/id/tgn/7008591/coordinates]
-- -skos:inScheme ycba_tgn:local : that's not a term value, so it should not be inScheme-
--* {color:#993300}I removed all the skos:inScheme that have: local{color}
-- -a crm:E47_Spacial_Coordinates : misspelt-
-- crm:P90_has_value "54.0000, \-4.5000" : better express this in a structured way.
-- You may want to consider the paper [Integration of Coordinate Information in CIDOC CRM|http://lists.ics.forth.gr/pipermail/crm-sig/attachments/20111107/f2d15017/attachment-0001.pdf]
--* {color:#993300}I represented this based on how Barry suggested using wgs84, awaiting some modification to RDFer for parsing lat,long into separate fields. Please take a look to see if I am missing anything: {color}[http://collection.britishart.yale.edu/id/tgn/7002445/location]

h3. AAT Concepts

LIDO

{code}
<lido:subjectSet>
<lido:subject lido:type="iconography">
<lido:subjectConcept>
<lido:conceptID lido:source="AAT" lido:type="local">248179</lido:conceptID>
<lido:term>religious art</lido:term>
</lido:subjectConcept>
</lido:subject>
</lido:subjectSet>
{code}
RDF

{code}
<http://collection.britishart.yale.edu/id/getty/aat/248179>
crm:E55_Type , skos:Concept .
a rdf:inScheme <http://collection.britishart.yale.edu/id/getty/aat/local> ;
#! "a" is synonym of the rdf:type proeprty, connecting to the classes. skos:inScheme is a different property
crm:label "religious art" ;
{code}

h2. Events


h4. Creation (Production)

h6. creator (actor)

Creator data could come from authority, this data was for YCBA purposes, however authority may not provide the complete creator info and may not facilitate linked data. We provide YCBA, ULAN or Library of Congress (LOC) identifiers where possible. Only LOC currently has linked data, we are working on mapping their URI in RDF.
(!)(!) You should use VIAF ([http://viaf.org/]) that aggregates data across ULAN, LOC and 20 national libraries. It's a most excellent resource.

LIDO

{code}
#! The next line is a duplicate, no?
<lido:eventActor><lido:displayActorInRole>Francis Hayman, 1707/8-1776, British</lido:displayActorInRole></lido:actorInRole></lido:eventActor>
<lido:eventActor>
<lido:displayActorInRole>Francis Hayman, 1707/8-1776, British</lido:displayActorInRole>
<lido:actorInRole>
<lido:actor lido:type="Individual">
<lido:actorID lido:source="YCBA" lido:type="local">7</lido:actorID>
<lido:actorID lido:source="ULAN" lido:type="local">500022272</lido:actorID>
<lido:actorID lido:source="LOC Identifier" lido:type="local">n85157944</lido:actorID>
<lido:nameActorSet>
<lido:appellationValue lido:pref="alternate">Francis Haiman</lido:appellationValue>
<lido:appellationValue lido:pref="preferred">Francis Hayman</lido:appellationValue>
</lido:nameActorSet>
<lido:nationalityActor>
<lido:term>British</lido:term>
</lido:nationalityActor>
<lido:vitalDatesActor>
<lido:earliestDate lido:type="estimatedDate">1707</lido:earliestDate>
<lido:latestDate lido:type="estimatedDate">1776</lido:latestDate>
</lido:vitalDatesActor>
<lido:genderActor>male</lido:genderActor>
</lido:actor>
<lido:roleActor>
<lido:conceptID lido:source="YCBA" lido:type="object related role">7</lido:conceptID>
<lido:term>Artist</lido:term>
</lido:roleActor>
<lido:roleActor>
<lido:conceptID lido:source="AAT" lido:type="Life role">25136</lido:conceptID>
<lido:term>painter</lido:term>
</lido:roleActor>
<lido:roleActor>
<lido:conceptID lido:source="AAT" lido:type="Life role">25165</lido:conceptID>
<lido:term>engraver (printmaker)</lido:term>
</lido:roleActor>
<lido:roleActor>
<lido:conceptID lido:source="AAT" lido:type="Life role">-1</lido:conceptID>
#! Filter this out: don't ever represent "missing" values in RDF
<lido:term>book illustrator</lido:term>
</lido:roleActor>
<lido:attributionQualifierActor/>
<lido:extentActor/>
</lido:actorInRole>
</lido:eventActor>
{code}
Please note that the above includes two kinds of data:
- About the person himself
- About the person's relation to the object (only "object related role")

(!) You must decide whether you emit any Person information from your databases, or trust VIAF to be complete enough

RDF
{code}
<http://collection.britishart.yale.edu/id/getty/tgn/7011781>
a crm:E21_Person, skos:Concept ;
crm:P131_is_identified_by
<http://collection.britishart.yale.edu/id/ycba/names/7/appellation/1> ,
<http://collection.britishart.yale.edu/id/ycba/names/7/appellation/2> ,
<http://collection.britishart.yale.edu/id/getty/ulan/500022272> ,
<http://id.loc.gov/authorities/names/n85157944> .
#! !!! you should use owl:sameAs for the different URIs of the person (ULAN, LOC). VIAF already has these

<http://collection.britishart.yale.edu/id/ycba/names/7/appellation/1>
a crm:E82_Actor_Appellation ;
rdf:label "Francis Haiman" .

<http://collection.britishart.yale.edu/id/ycba/names/7/appellation/2>
a crm:E82_Actor_Appellation ;
rdf:label "Francis Hayman" .
{code}

h6. death place (creator)

rather strange as not part of actor, this was added for YCBA purposes, could come from authority record

LIDO

{code}
<lido:eventPlace lido:type="Death place">
<lido:displayPlace>London</lido:displayPlace>
<lido:place>
<lido:namePlaceSet>
<lido:appellationValue>London</lido:appellationValue>
</lido:namePlaceSet>
<lido:gml>
<gml:Point>
<gml:coordinates>51.5000, -0.1660</gml:coordinates>
</gml:Point>
</lido:gml>
<lido:placeClassification>
<lido:conceptID lido:source="TGN" lido:type="Death place">7011781</lido:conceptID>
</lido:placeClassification>
</lido:place>
</lido:eventPlace>
{code}
RDF - not sure what property type to use to get at this
{code}
<http://collection.britishart.yale.edu/id/ycba/names/7>
crm:__???__ <http://collection.britishart.yale.edu/id/getty/tgn/7011781> .

<http://collection.britishart.yale.edu/id/getty/tgn/7011781>
a skos:Place ; 
a crm:E55_Type ;
crm:P87_is_identified_by <http://collection.britishart.yale.edu/id/tgn/7011781/coordinates> ;
wgs84_pos:location <http://collection.britishart.yale.edu/id/tgn/7011781/location> ;
crm:label "London" .

<http://collection.britishart.yale.edu/id/tgn/7002445/coordinates>
a crm:E47_Spatial_Coordinates ;
crm:P90_has_value "51.5000, -0.1660" .

<http://collection.britishart.yale.edu/id/tgn/7002445/location>
a wgs84_pos:SpatialThing ;
wgs84_pos:lat "51.5000" ;
wgs84_pos:long "-0.1660" .
{code}

h6. birth place (creator)

rather strange as not part of actor, this was added for YCBA purposes, could come from authority record

LIDO

{code}
<lido:eventPlace lido:type="Birth place">
<lido:displayPlace>Exeter</lido:displayPlace>
<lido:place>
<lido:namePlaceSet>
<lido:appellationValue>Exeter</lido:appellationValue>
</lido:namePlaceSet>
<lido:gml>
<gml:Point>
<gml:coordinates>50.7160, -3.5160</gml:coordinates>
</gml:Point>
</lido:gml>
<lido:placeClassification>
<lido:conceptID lido:source="TGN" lido:type="Birth place">7011953</lido:conceptID>
</lido:placeClassification>
</lido:place>
</lido:eventPlace>
{code}
RDF

{code}
same as above "Death place" representation
{code}

h6. date (event date)

LIDO
{code}
<lido:eventDate>
<lido:displayDate>between 1751 and 1752</lido:displayDate>
<lido:date>
<lido:earliestDate>1751</lido:earliestDate>
<lido:latestDate>1752</lido:latestDate>
</lido:date>
</lido:eventDate>
{code}
RDF

{code}
<http://collection.britishart.yale.edu/id/object/499/production/date>
crm:P3_has_note "Production date :: between 1751 and 1752" ;
crm:P82_at_some_time_within "between 1751 and 1752" ;
crm:P82a_begin_of_the_begin "1751"^^ ;
crm:P82b_end_of_the_end "1752"^^ .
{code}

h6. period (text time period this event occurred in)

LIDO

{code}
<lido:periodName>
<lido:conceptID lido:type="Period" lido:source="YCBA">22</lido:conceptID>
<lido:term>18th century</lido:term>
</lido:periodName>
</lido:periodName>
{code}
RDF

This is definitely not E55_Type
{code}
<http://collection.britishart.yale.edu/id/aat/22>
a crm:E55_Type , skos:Concept ; 
a crm:E4_Period ;
skos:inScheme ycba_aat:Period ; 
skos:prefLabel "18th century"{code}
- I think this is better mapped to E52_Time-Span since it's not a cultural period and has only a time aspect
- Consider using the excellent work on [Handling Time Periods in STAR|http://hypermedia.research.glam.ac.uk/kos/star/time-periods/] to assign actual dates to such time-spans, using the label
- {color:#993300}I already have time span defined with actual dates, the period is to provide label, if there is something else I need to do please let me know. I removed E55_Type. {color}
- {color:#993300}Production dates: {color}[http://collection.britishart.yale.edu/id/object/499/production/date|http://collection.britishart.yale.edu/id/page/object/499/production/date]
- {color:#993300}Period {color}[http://collection.britishart.yale.edu/id/getty/aat/300111159|http://collection.britishart.yale.edu/id/page/getty/aat/300111159]
-

h6. culture

LIDO

{code}
<lido:culture>
<lido:conceptID lido:source="AAT" lido:type="Culture">300111159</lido:conceptID>
<lido:term>British</lido:term>
</lido:culture>
{code}
RDF

This is neither E55_Type nor E74_Group. It's a [E4_Period@crm] (see the Scope Note)
{code}<http://collection.britishart.yale.edu/id/getty/aat/300111159>
a crm:E55_Type , skos:Concept ; 
a crm:E74_Group ;
skos:inScheme aat:Culture ;  
skos:prefLabel "British"{code}
- (!) See [BMX Issues#Theaurus Requirements] for more guidelines
- {color:#993300}Looking at the requirements and notes between Ontotext and BM, I am confused as to what is the agreed solution. {color}
- {color:#993300}Do I need anything else? I now have:{color}
- {code}
<http://collection.britishart.yale.edu/id/getty/aat/300111159>
a crm:E4_Period ;a rdfs:label "British" ;a skos:inScheme aat:Culture
{code}

h6. technique (support and medium)

LIDO

{code}
<lido:eventMaterialsTech>
<lido:displayMaterialsTech>Oil on canvas</lido:displayMaterialsTech>
<lido:materialsTech>
<lido:termMaterialsTech>
<lido:conceptID lido:type="support" lido:source="AAT">14078</lido:conceptID>
<lido:term>canvas</lido:term>
</lido:termMaterialsTech>
<lido:termMaterialsTech>
<lido:conceptID lido:type="medium" lido:source="AAT">230810</lido:conceptID>
<lido:term>oil paint</lido:term>
</lido:termMaterialsTech>
</lido:materialsTech>
</lido:eventMaterialsTech>
{code}
RDF

In this below the Medium (technique) is mapped ok, but Support should be mapped to E57_Material and you should attach it with {{crm:P45_consists_of}} and {{crm:P126_employed}}. See [Material and Medium-Technique|Material and Medium-Technique] for details
{code}
<http://collection.britishart.yale.edu/id/object/499/production> 
a crm:E12_Production ;
crm:P32_used_general_technique <http://collection.britishart.yale.edu/id/getty/aat/14078> , <http://collection.britishart.yale.edu/id/getty/aat/230810> .
<http://collection.britishart.yale.edu/id/getty/aat/14078> 
a crm:E55_Type , skos:Concept ;
skos:inScheme aat:support ; 
skos:prefLabel "canvas" .
<http://collection.britishart.yale.edu/id/getty/aat/230810> 
a crm:E55_Type , skos:Concept ;
skos:inScheme aat:medium ; 
skos:prefLabel "oil paint" .
{code}\* {color:#993300}Another quick look at this to make sure I setup Support correctly:{color} [http://collection.britishart.yale.edu/id/getty/aat/14078|http://collection.britishart.yale.edu/id/page/getty/aat/14078]
- crm:P82a_end_of_the_end "1752" : misspelt, that's P82b.
- -Also, you better put a type{-}{code}"1752"^^xsd:gYear{code}
{color:#993300}Production Date looks a bit different for YCBA and BM, we use {color}[P4_has_time-span|http://erlangen-crm.org/current/P4_has_time-span]{color:#993300} BM does not. Here is my example: {color}[http://collection.britishart.yale.edu/id/object/499/production|http://collection.britishart.yale.edu/id/page/object/499/production]

h4. Provenance

Currently big block of text represented as PX3_provenance, it is just under the main object. Provenance does not currently have identifiers, it is part of an object, it may be divided into smaller components in the future ie; names, dates, and prices at which point we may need the unique identifiers.

LIDO

{code}
<lido:eventSet>
<lido:displayEvent>Commissioned by William Wrightson for the chapel at Cusworth Hall and paid for in full March 19, 1752; by descent in the Battie-Wrightson family as follows: Isabel Wrightson (1727-1784) and John Battie of Warmsworth Hall (1722-1765); William Wrightson [Battie] (1752-1827); William Battie Wrightson (1789-1879); Richard Heber Wrightson (1800-1891); William Henry Thomas [Battie-Wrightson] (1855-1903) and Lady Isabella Georgiana Katherine Battie Wrightson (1853-1917); Robert Cecil Battie-Wrightson (1888-1952); Barbara Isabella Georgiana Battie-Wrightson [Mrs. Maureen L. Pearse] (1890-1989) by whom given to the St Hubert Church Charitable Trust; sold by order of the St Hubert Church trustees, Sotheby’s, London, July 6, 1977, lot. 78; Somerville and Simpson from whom purchased by the Yale Center for British Art, 1978</lido:displayEvent>
<lido:event>
<lido:eventType>
<lido:conceptID lido:source="AAT" lido:type="LIDO">300055863</lido:conceptID>
<lido:term>provenance</lido:term>
</lido:eventType>
</lido:event>
</lido:eventSet>
</lido:eventSet>
{code}
RDF

{code}
<http://collection.britishart.yale.edu/id/ontology/PX3_provenance> "Commissioned by William Wrightson for the chapel at Cusworth Hall and paid for in full March 19, 1752; by descent in the Battie-Wrightson family as follows: Isabel Wrightson (1727-1784) and John Battie of Warmsworth Hall (1722-1765); William Wrightson [Battie] (1752-1827); William Battie Wrightson (1789-1879); Richard Heber Wrightson (1800-1891); William Henry Thomas [Battie-Wrightson] (1855-1903) and Lady Isabella Georgiana Katherine Battie Wrightson (1853-1917); Robert Cecil Battie-Wrightson (1888-1952); Barbara Isabella Georgiana Battie-Wrightson [Mrs. Maureen L. Pearse] (1890-1989) by whom given to the St Hubert Church Charitable Trust; sold by order of the St Hubert Church trustees, Sotheby’s, London, July 6, 1977, lot. 78; Somerville and Simpson from whom purchased by the Yale Center for British Art, 1978" ;
{code}

h4. Exhibition History

Currently only title of exhibition, comma separated, date (YYYY format). We also have the unique exhibition ID that is part of the URI. We model conceptID terms separately under subject terms, is this correct?

LIDO

{code}
<lido:eventSet>
<lido:displayEvent>Connections, 2011</lido:displayEvent>
<lido:event>
<lido:eventID lido:type="TMS">757</lido:eventID>
<lido:eventType>
<lido:conceptID lido:source="AAT" lido:type="LIDO">300054766</lido:conceptID>
<lido:term>exhibition history</lido:term>
</lido:eventType>
</lido:event>
</lido:eventSet>
{code}
RDF
{code}
<http://collection.britishart.yale.edu/id/exhibition/389> 
a crm:E7_Activity ;
crm:P3_has_note "Francis Hayman, 1987" .
{code}


h4. Publication

We have a text for bibliographic entry and plan to add URI to OCLC WorldCat and Google Books (at some point once these provide linked data, it will be all linked). As above term and concept ID is under subject terms.

LIDO

{code}
<lido:eventSet>
<lido:displayEvent>J. H. Plumb, The pursuit of happiness, a view of life in Georgian England : an exhibition selected from the Paul Mellon collection, Yale Center for British Art, New Haven, 1977, pp. 45, 97, no. 67, N6766 Y34 1977 (YCBA)</lido:displayEvent>
<lido:event>
<lido:eventID lido:type="TMS">191</lido:eventID>
<lido:eventID lido:type="OCLC Number">3447120</lido:eventID>
<lido:eventType>
<lido:conceptID lido:source="AAT" lido:type="LIDO">300111999</lido:conceptID>
<lido:term>publication</lido:term>
</lido:eventType>
</lido:event>
</lido:eventSet>
{code}
RDF

{code}
<http://collection.britishart.yale.edu/id/publication/191> 
a <bibo:Journal> ;
crm:P1_is_identified_by <http://www.worldcat.org/oclc/3447120> ;
<http://purl.org/dc/terms/description> "J. H. Plumb, The pursuit of happiness, a view of life in Georgian England : an exhibition selected from the Paul Mellon collection, Yale Center for British Art, New Haven, 1977, pp. 45, 97, no. 67, N6766 Y34 1977 (YCBA)" .
{code}

h4. Acquisition

\-\- pending test case and LIDO

h4. Framing History (part addition)

\-\- pending test case and LIDO

h4. Conservation (modification)

\-\- pending test case and LIDO
----