View Source

{excerpt}Mapping of BM Association Codes to CRM constructs{excerpt}

{toc}
h1. Introduction
We put Association Codes in two different nodes depending on what the code relates to. This is described in the next two sections.

h2. Code In Reified Association
When an Association Code is about the role of an entity in an event, we put it in explicit bmo:EX_Association node (reification).
We use an extension of E13_Attribute_Assignment, adding a way to identify which property we are talking about:
{code}
bmo:EX_Association rdfs:subClassOf E13_Attribute_Assignment.
bmo:PX_property a rdf:ObjectProperty; rdf:domain E1_CRM_Entity; rdf:range rdf:ObjectProperty.
{code}

For example the code:
|Acquisition Person|B: Bequeathed by|
is mapped to:
{code}
<obj/acquisition> a E8_Acquisition;
P23_transferred_title_from <person>.
<obj/acquisition/association/N> a bmo:EX_Association;
P140_assigned_attribute_to <obj/acquisition>; P141_assigned <person>; bmo:PX_property P23_transferred_title_from;
P2_has_type <thesaurus/acquisition/bequeathed_by>.
{code}
which is depicted below:
{flowchart}
node [shape=box fontname=Arial fontsize=10 width=0 height=0];
edge [fontname=Arial fontsize=10];
acquisition [label="<obj/acquisition>\na E8_Acquisition"];
association [label="<obj/acquisition/association/N>\na bmo:EX_Association"];
"P23_transferred_title_from" [shape=none];
{edge [weight=100];
acquisition -> "P23_transferred_title_from" -> "<person>";
}
association -> acquisition [label="P140_assigned_attribute_to"];
association -> "<person>" [label="P141_assigned"];
association -> "P23_transferred_title_from" [label="bmo:PX_property"];
association -> "<thesaurus/acquisition/bequeathed_by>" [label="P2_has_type"];
{rank=same;
association; "P23_transferred_title_from"
}
{flowchart}

h2. Translated Code in Event
When an Association Code is about an event, we put it directly on the event.
We translate the code to a thesaurus term that speaks about the *event*, not about an *entity* associated with the event. Often codes from different association vocabularies but having the same meaning, are collapsed to the same term, eg:
| *Association Vocabulary* | *Code* | *Thesaurus Term* |
| Production Person | L: Lustred by | <thesaurus/production/lustred> |
| Production Place | L: Lustred in | <thesaurus/production/lustred> |
{code}
<obj/production/M> a E12_Production; P2_has_type <thesaurus/production/lustred>;
P14_carried_out_by <person>.
<obj/production/N> a E12_Production; P2_has_type <thesaurus/production/lustred>;
P7_took_place_at <place>.
{code}
Note: we cannot collapse these two events into one, since we don't have info to correlate them: see next section.

h2. Multiple Uncorrelated Events
In many cases we cannot correlate entitites, since such info is missing in Merlin. In such cases we use an independent counter (denoted M,N etc) to create unrelated nodes of the same type. Examples:
# Production Person to Production Place, even when the two are of the same type (eg "lustred"): see prev section
# Inscription to specific inscription creator (Inscription by)
{code}
<obj/inscription/M> a E34_Inscription; P3_has_note "Lorem ipsum".
<obj/inscription/N> a E34_Inscription; P94i_was_created_by <obj/inscription/N/creation>.
<obj/inscription/N/creation> P14_carried_out_by <person>;
P2_has_type <type>.
{code}
<obj/inscription/M> carries the properties of the inscription, and <obj/inscription/N> is an empty node that has only type and an attached creation event.

Exception: all Acquisition and Transfer of Custody data (see [#Acquisition Person]) uses the same event URI <obj/acquisition>, since Merlin has data only about the last acquisition

h2. Uncorrelated Events Display
The desired way to display multiple uncorrelated events of the same type is:
- group the events under the same heading (event type)
- append the association code (type) in parentheses, no matter whether it's [In Association|#Code In Reified Association] or [In Event|#Translated Code in Event]

Examples:
|{code}
<obj/production/M> a E12_Production; P14_carried_out_by <person>;
P2_has_type <thesaurus/production/lustred>.
<obj/production/N> a E12_Production; P7_took_place_at <place1>;
P2_has_type <thesaurus/production/lustred>.
<obj/production/K> a E12_Production; P7_took_place_at <place2>.
<obj/production/K/association> a bmo:EX_Association;
P140_assigned_attribute_to <obj/production/K>; P141_assigned <place2>; bmo:PX_property P7_took_place_at;
P2_has_type <thesaurus/production/factory_in>.
{code}|{noformat}
Production
carried out by: Person (lustred)
took place at: Place1 (lustred)
took place at: Place2 (factory in)
{noformat}|
|{code}
<obj/acquisition>
P28_custody_surrendered_by <museum1>;
P11_had_participant <person3>;
P17_was_motivated_by <person4>.
<obj/acquisition/association/K> a bmo:EX_Association;
P140_assigned_attribute_to <obj/acquisition>; P141_assigned <museum1>; bmo:PX_property P28_custody_surrendered_by;
P2_has_type <thesaurus/acquisition/on_loan_from>.
<obj/acquisition/association/M> a bmo:EX_Association;
P140_assigned_attribute_to <obj/acquisition>; P141_assigned <person3>; bmo:PX_property P11_had_participant;
P2_has_type <thesaurus/acquisition/donated_through>.
<obj/acquisition/association/N> a bmo:EX_Association;
P140_assigned_attribute_to <obj/acquisition>; P141_assigned <person4>; bmo:PX_property P17_was_motivated_by;
P2_has_type <thesaurus/acquisition/in_memory_of>.
{code}|{noformat}
Acquisition
custody surrendered by: Museum1 (On Loan From)
had participant: Person3 (Donated Through)
was motivated by: Person4 (In Memory Of)
{noformat}|

(?) But where the hell do we put the Annotation Points, i.e. what can the user annotate and propose new values for?
I suggest we put AP only for the values (person, place, etc). If we also allow proposing new values for the codes:
- it'll get too complex (several APs in one line)
- Josh needs to split into sub-thesauri of "compatible terms", according to the sub-sub-sections of [#Association Mapping]
Example: the user shouldn't be able to propose <thesaurus/acquisition/donated_through> instead of <thesaurus/acquisition/in_memory_of>,
since these terms go along with different CRM properties (P11_had_participant vs P17_was_motivated_by)
and are listed in different sub-sub-sections ([#Acquired Through (intermediary or contributor)] vs [#Acquisition Motivated By])

h2. Association Terms and ConceptSchemes
What Terms and ConceptSchemes should be used in the sections below? Unfortunately this wasn't specified in detail until now (02-Nov-2012):
- [#Translated Code in Event] says that terms should be merged when they express the same meaning
- later the spec uses <type-TRANSLATED> in various places, but leaves the details unspecified

Guiding Principles:
- URIs:
-- each term should have the ConceptScheme URI as a prefix
-- one ConceptScheme should not be prefix of another
-- preferably, term names should be meaningful and not codes.
Eg "school-of" is preferred to "AJ".
Since each term has a meaningful name in skos:prefLabel, this is a preference, not a requirement.
- ConceptSchemes:
-- Terms with related meaning should be in the same scheme
Eg both "lustred" and "decorated" should be inScheme thesauri/production/technique
-- Terms with the same meaning should be merged
Eg both "Lustred by" and "Lustred in" describes a technique, so they should be mapped to thesauri/production/technique/lustred. By/in is taken care of by different CRM relations

This would have impact on RS only if we care what New Values a user can propose, as part of Annotating an association code.
In that case all Terms in a given scheme should be "compatible" (last principle above).
But I don't think we should chase this now, since some of the codes are quite peculiar and the thesaurus becomes quite fragmented (many ConceptSchemes with just 1-2 values)
(This is in a similar train of thought as {jira:RS-716})


Proposed schemes:
| *Association (Section)*|*ConceptScheme*/term|
| [#Acquired From], [#Treasure Act] |*acquisition/from*|
| [#Former Owner] |n/a: this has no association|
| [#Received Custody From] |*custody*/on-loan|
| [#Acquired Through (intermediary or contributor)] | *acquisition/through*|
| [#Acquisition Motivated By] |*acquisition/motivated*|
| [#Found By], [#Jointly Found By], [#Findspot] |*acquisition/found*|
| [#Owned By] |n/a: this has no association|
| [#Produced By Specific Process], [#Produced By Specific Process At] |*production/process*|
| [#Produced By Closely Related Group], [#Produced At] |*production/group* |
| [#Probably/Unlikely Produced By], [#Probably Produced At] |*production/likelihood*.
Some of the codes also have a "group" aspect (eg AC: Attributed to the Circle of). TODO: map it too|
| [#Retailed By], [#Retailed In] |*retailed*|
| [#Inscription Created By] |*production/inscription*|
| [#Part Made By], [#Part Made In] |n/a: uses general "object type" thesaurus|
| [#Influenced By] |*production/influenced-by*|
| [#Production Motivated By], [#Made For Person], [#Made For Place] |*production/motivated-by*|
| [#Depicted Person], [#Person in Inscription], [#Person Depicted and in Inscription], [#Depicted Place], [#Place in Inscription], [#Event in Inscription] |*represents*|
| [#Referred Person], [#Referred Place], [#Referred Event] |n/a: maps to straight P67_refers_to|
| [#Repaired By], [#Repaired In] | *modification*/repaired|
| [#Natural Source] |n/a|
| [#Original From] | *association/object*/original |
| [#Made for Event], [#Used at Event] |n/a: maps to straight P19i_was_made_for, P12i_was_present_at|
| [#Commemorates Event] |n/a: uses bmo:PX_commemorates|
| [#Associated Title] | *association/title* |
| [#Inscription Subject] |*inscription/subject*|
| [#Inscription Type] |*inscription/type*|
| [#Referred Group], [#Depicted Group], [#Made By Group] |n/a: maps to straight CRM properties|

h1. Association Mapping

h2. Acquisition Person

h3. Acquired From
B: Bequeathed by
D: Donated by
E: Exchanged with
F: From
P: Purchased from
T: Transferred from: this is transfer of ownership, and not merely custody
UI: Unclaimed item: the former owner brought it in for examination, and never reclaimed it. "Over time" BM became the owner, although its legal status is a bit unclear

{code}
<obj> P51_has_former_or_current_owner <person>;
P52_has_current_owner id:the-british-museum.
<obj/acquisition> a E8_Acquisition;
P24_transferred_title_of <obj>;
P23_transferred_title_from <person>;
P22_transferred_title_to <id:the-british-museum>.
<obj/acquisition/association/N> a bmo:EX_Association;
P140_assigned_attribute_to <obj/acquisition>; P141_assigned <person>; bmo:PX_property P23_transferred_title_from;
P2_has_type <type>.
{code}

h3. Treasure Act
TT: Treasure Trove
TR: Purchased through the Treasure Act 1996
This says a treasure (eg gold) was found in the UK, and BM (or Department of Culture) purchased it from the land's owner under the Treasure Act.
- The institution mentioned in this association is usually Department of Culture, so we won't record it. (?) Josh: I think we said we would record it as the DfCMS may not always apply.
- There'll be a separate association to say who it was purchased From.

{code}
<obj/acquisition> a E8_Acquisition; P2_has_type <thesauri/acquisition/treasure-act>;
P17_was_motivated_by <id:treasure-act>.
{code}
TODO Josh: check/correct the two fixed URIs above. You should be careful that all Acquisition P2_has_type's come from the same thesaurus!
TODO Josh: Will also keep the current triple of saying the acquisition was motivated_by a URI which represents the Treasure Act / Treasure Trove. Will adjust the type from a E30_Right to a class which represents a law...

h3. Former Owner
PO: Previous owner/ex-collection
All prev owners are listed with this code, and the last one is listed with an [#Acquired From] code
{code}
<obj> P51_has_former_or_current_owner <person>.
{code}

h3. Received Custody From
L: On loan from

{code}
<obj/acquisition> a E10_Transfer_of_Custody;
P30_transferred_custody_of <obj>;
P28_custody_surrendered_by <person>;
P29_custody_received_by id:the-british-museum.
<obj> P49_has_former_or_current_keeper <person>;
P50_has_current_keeper id:the-british-museum.
<obj/acquisition/association/N> a bmo:EX_Association;
P140_assigned_attribute_to <obj/acquisition>; P141_assigned <person>; bmo:PX_property P28_custody_surrendered_by;
P2_has_type <type>.
{code}

h3. Acquired Through (intermediary or contributor)
A: Purchased through
BT: Bequeathed through
CF: With contribution from
EC: Exchanged through
FU: Funded by
S: Sponsored by
V: Donated through

All of the above codes imply that BM received ownership
{code}
<obj> P52_has_current_owner id:the-british-museum.
<obj/acquisition> a E8_Acquisition;
P24_transferred_title_of <obj>;
P11_had_participant <person>;
P22_transferred_title_to <id:the-british-museum>.
<obj/acquisition/association/N> a bmo:EX_Association;
P140_assigned_attribute_to <obj/acquisition>; P141_assigned <person>; bmo:PX_property P11_had_participant;
P2_has_type <type>.
{code}

h3. Acquisition Motivated By
IH: In Honour of
IM: In Memory of

(?) Do all of the above codes imply that BM received ownership? I'm not sure
{code}
<obj> P52_has_current_owner id:the-british-museum.
<obj/acquisition> a E8_Acquisition;
P24_transferred_title_of <obj>;
P17_was_motivated_by <person>
P22_transferred_title_to <id:the-british-museum>.
<obj/acquisition/association/N> a bmo:EX_Association;
P140_assigned_attribute_to <obj/acquisition>; P141_assigned <person>; bmo:PX_property P17_was_motivated_by;
P2_has_type <type>.
{code}

h3. Found By
C: Collected by
EX: Excavated by

Discovery (Finding) is an important kind of event: for most archeological artefacts we don't know much about Production, but we may know about Discovery. So we define a sub-class for it.
{code}
bmo:EX_Discovery rdfs:subClassOf E7_Activity;
rdfs:label "Discovery"; rdfs:comment "The activity of finding, excavating or collecting an object".

<obj> P12i_was_present_at <obj/find>.
<obj/find> a bmo:EX_Discovery; P2_has_type <type-TRANSLATED>; P14_carried_out_by <person>.
{code}
- Finding an object tells us nothing about former or current ownership.

The place of finding ([#Findspot]) is defined in a similar way.
It's mapped to the same node <obj/find>, though there may be some duplicate statements (eg bmo:EX_Discovery is stated twice)

h3. Jointly Found By
DA: Division of Finds: BM and the other Person did a joint excavation, and divided the finds
{code}
<obj> P12i_was_present_at <obj/find>.
<obj/find> a bmo:EX_Discovery; P2_has_type <type-TRANSLATED>;
P14_carried_out_by <person>, <id:the-british-museum>.
{code}

h3. Owned By
OB: Owned by
The object is *not* in the BM collection (and not owned by BM), even though it's in the Merlin database
- The motivation is to create cross-museum catalogs
- Such objects won't be found by RS (they are not marked FC70_Thing so are not searchable)
- They are filtered out of BM's Collection Online
- TODO Josh should filter them out of the .
- TODO Josh: adjust The export from Merlin to BM RDF data to leave out objects which have an association code 'OB'

h2. Production Person

h3. Produced By Specific Process
|5: Drawn by |ID: Intermediary draughtsman |
|AU: Author |J: Modelled by |
|BC: Block cut by |L: Lustred by |
|CA: Calligrapher |M: Made by |
|D: Designed by |P: Painted by |
|DE: Decorated by |PH: Photographed by |
|DM: Medal designed and made by |SC: Scribe |
|E: Engraved by |WR: Written by |
|I: Issuer |Z: Published by |

{code}
<obj> P108i_was_produced_by <obj/production/M>.
<obj/production/M> a E12_Production; P2_has_type <type-TRANSLATED>;
P14_carried_out_by <person>.
{code}

(!) Josh: Ensure any harmonisation of these association codes are done with the ones in Production Place & relevant codes in Association

These codes mean the same:
|G: Moneyer |
|T: Mint |
|Production Authority: M: Moneyer|
TODO Josh: the type-TRANSLATION should map them to the *same* term.

These codes mean the same:
|PA: Print artist |
|PM: Print made by |
|R: Printed by |


h3. Produced By Closely Related Group
AG: Office/studio of
AJ: Circle/School of
F: Factory of: an industrial or mass product (eg ship, porcelain, etc)
N: Pupil of
O: Official/Office/Dept: unsure what's that, there are only 3 objects
W: Workshop of

{code}
<obj> P108i_was_produced_by <obj/production/M>.
<obj/production/M> a E12_Production; P14_carried_out_by <person>.
<obj/production/M/association> a bmo:EX_Association;
P140_assigned_attribute_to <obj/production/M>; P141_assigned <person>; bmo:PX_property P14_carried_out_by;
P2_has_type <type>.
{code}

h3. Retailed By
RT: Originally retailed by: eg Barbie dolls are retailed by Mattell
TODO Josh: Create an Activity which represents the retail (use P2_has_type). The URI can be <obj/retail>. (!) Confirm with Vlado

h3. Probably/Unlikely Produced By
- *Probably*
A: Attributed to
AA: Attributed to an Apprentice/Pupil of
AB: Ascribed to
AC: Attributed to the Circle of
AD: Assigned to
AW: Attributed to the Workshop of
CB: Claimed to be by
- *Unlikely*
AE: Formerly attributed to: It was thought to be made by the person, but not anymore (there would be another Attributed association)

Before we used a (multi-inheritance) sub-property to indicate the uncertainty:
{code}
bmo:PX_probably_carried_out_by rdfs:subPropertyOf crm:P14_carried_out_by, bmo:PX_probably.

<obj> P108i_was_produced_by <obj/production/M>.
<obj/production/M> a E12_Production; bmo:PX_probably_carried_out_by <person>.
<obj/production/M/association> a bmo:EX_Association;
P140_assigned_attribute_to <obj/production/M>; P141_assigned <person>; bmo:PX_property bmo:PX_probably_carried_out_by;
P2_has_type <type>.
{code}
- Josh: Are we sure we want to sub-property CRM to indicate uncertainty? Would it not be better to have a subProperty of PX_probably which is in the BMO?
- Vlado: it is multi-inherited, once from CRM and secondly from PX_probably, so I'm not sure what is your question

Vlado: now I think it's better to put the uncertainty indicator directly on EX_Association:
- Otherwise a BMO-unaware app will not print it out.
- Property multi-inheritance is a bad idea: if the same Production and Person are connected by two properties (eg P14_carried_out_by, P15_was_influenced_by), the PX_probably and PX_unlikely may get mixed up.
- We'll replace 5 extension properties (bmo:PX_probably, bmo:PX_probably_carried_out_by, etc) by 1 (PX_likelihood), which is a good thing.

h4. New Proposal
We define ext prop PX_likelihood and put the specific values in a thesaurus.
OPTIONALLY, we make a hierarchy under terms "likely/unlikely" (maybe that's an overkill!).
{code}
bmo:PX_likelihood rdfs:subPropertyOf P2_has_type.
<thes/likelihood> a skos:ConceptScheme; rdfs:label "BM Likelihood".
<thes/likelihood/probably> a skos:Concept, E55_Type; skos:prefLabel "Probably"; skos:inScheme <thes/likelihood>.
<thes/likelihood/unlikely> a skos:Concept, E55_Type; skos:prefLabel "Unlikely"; skos:inScheme <thes/likelihood>.
<thes/likelihood/attributed> a skos:Concept, E55_Type;
skos:prefLabel "Attributed"; # codes: A (Attributed to), A (Attributed at)
skos:inScheme <thes/likelihood>; skos:broader <thes/likelihood/probably>.
<thes/likelihood/claimed-to-be> a skos:Concept, E55_Type;
skos:prefLabel "Claimed to be"; # CB (Claimed to be by), CF (Claimed to be from)
skos:inScheme <thes/likelihood>; skos:broader <thes/likelihood/probably>.
...
<thes/likelihood/formerly-attributed> a skos:Concept, E55_Type;
skos:prefLabel "Formerly attributed"; # codes: AE (Formerly attributed to)
skos:inScheme <thes/likelihood>; skos:broader <thes/likelihood/unlikely>.
# These are not normally used in data, but can be used to propose a new value
<thes/likelihood/true> a skos:Concept, E55_Type; skos:prefLabel "True"; skos:inScheme <thes/likelihood>.
<thes/likelihood/false> a skos:Concept, E55_Type; skos:prefLabel "False"; skos:inScheme <thes/likelihood>.
{code}

The data mapping then is very simple:
{code}
<obj> P108i_was_produced_by <obj/production/M>.
<obj/production/M> a E12_Production; crm:P14_carried_out_by <person>.
<obj/production/M/association> a bmo:EX_Association;
P140_assigned_attribute_to <obj/production/M>; P141_assigned <person>; bmo:PX_propery crm:P14_carried_out_by;
bmo:PX_likelihood <thes/likelihood/attributed>.
{code}

h3. Inscription Created By
IR: Inscription by
LE: Lettering engraved by

{code}
<obj> P65_shows_visual_item <obj/inscription/M>.
<obj/inscription/M> a E34_Inscription; P94i_was_created_by <obj/inscription/M/creation>.
<obj/inscription/M/creation> a E65_Creation; P14_carried_out_by <person>;
P2_has_type <type>.
{code}

h3. Part Made By
MB: Bell made by
MC: Case made by
MD: Dial made by
ME: Ebauche maker
MM: Movement made by
MP: Watch pendant made by
MQ: Dust-cap maker

{code}
<obj/part/M> a E22_Man-Made_Object; P46i_forms_part_of <obj>;
P2_has_type <type-TRANSLATED>;
P108i_was_produced_by <obj/part/M/production>.
<obj/part/M/production> P14_carried_out_by <person>.
{code}
Here the type translation removes "made by" and leaves only the part type (eg Bell)

h3. Influenced By
AF: Attributed to a Follower of
AI: Attributed to an Imitator of
AL: Manner/Style of
AM: Attributed to the Manner of
AT: After
C: Close to
CF: Compare with
CM: Connected with the Manner of
CW: Connected with
S: School of/style of
RE: Related to
NE: Near: means the same as "In the style of"
RC: Recalls

{code}
<obj> P108i_was_produced_by <obj/production/M>.
<obj/production/M> a E12_Production; P15_was_influenced_by <person>.
<obj/production/M/association> a bmo:EX_Association;
P140_assigned_attribute_to <obj/production/M>; P141_assigned <person>; bmo:PX_property P15_was_influenced_by;
P2_has_type <type>.
{code}

h2. Production Authority

h3. Production Motivated By
E: Eponym: according to [wikipedia|http://en.wikipedia.org/wiki/Eponym], it means something like Inventor, but BM uses it as the others below
G: Governor
I: Issuer
K: Ruler
Y: Magistrate

{code}
<obj> P108i_was_produced_by <obj/production/M>.
<obj/production/M> a E12_Production; P17_was_motivated_by <person>.
<obj/production/M/association> a bmo:EX_Association;
P140_assigned_attribute_to <obj/production/M>; P141_assigned <person>; bmo:PX_property P17_was_motivated_by;
P2_has_type <type>.
{code}

Notes:
M: Moneyer: is mapped the same as Production Person=G: Moneyer

h2. Production Place

h3. Produced By Specific Process At
D: Designed in
DE: Decorated in
I: Issued in
L: Lustred in
M: Made in
MI: Minted in
P: Painted in
PH: Photographed in
R: Printed in
Z: Published in

Similar to [#Produced By Specific Process]:
{code}
<obj> P108i_was_produced_by <obj/production/M>.
<obj/production/M> P7_took_place_at <place>; P2_has_type <type>.
{code}

h3. Produced At
F: Factory in
W: Workshop in

Similar to [#Produced By Closely Related Group]:
{code}
<obj> P108i_was_produced_by <obj/production/M>.
<obj/production/M> P7_took_place_at <place>.
<obj/production/M/association> a bmo:EX_Association;
P140_assigned_attribute_to <obj/production/M>; P141_assigned <place>; bmo:PX_property P7_took_place_at;
P2_has_type <type>.
{code}

h3. Retailed In
RT: Retailed in
TODO
Similar to [#Retailed By]

h3. Probably Produced At
A: Attributed at
CF: Claimed to be from
Similar to [#Probably Produced By] ([#New Proposal])
{code}
<obj> P108i_was_produced_by <obj/production/M>.
<obj/production/M> a E12_Production; crm:P7_took_place_at <place>.
<obj/production/M/association> a bmo:EX_Association;
P140_assigned_attribute_to <obj/production/M>; P141_assigned <person>; bmo:PX_property crm:P7_took_place_at;
bmo:PX_likelihood <thes/likelihood/attributed>.
{code}

h3. Part Made In
MB: Bell made in
MC: Case made in
MD: Dial made in
ME: Ebauche made in
MM: Movement made in
MP: Watch pendant made in
MQ: Dust-cap made in

Similar to [#Part Made By]:
{code}
<obj/part/M> a E22_Man-Made_Object; P46i_forms_part_of <obj>;
P2_has_type <type-TRANSLATED>;
P108i_was_produced_by <obj/part/M/production>.
<obj/part/M/production> P7_took_place_at <place>.
{code}

h2. Associated Person

h3. Depicted Person
AB: Illustration of
IP: Portrait of
IR: Representation of
EE: Emblem of

We choose to state both the shortcut (P62) and longcut (P65-E36-P138) so we can use the intermediate node to attach the type:
{code}
<obj> P62_depicts <person>.
<obj> P65_shows_visual_item <obj/image/N>.
<obj/image/N> a E38_Image; P138_represents <person>; P2_has_type <type>.
{code}

Note about Emblem (eg coat of arms, company logo, etc): it's not a literal depiction, but still very closely related to the Person, so we map it like the rest.
We considered stating it's a conceptual object that belongs to the person (P105_right_held_by instead of P138), but decided that the association is more intimate than just holding a right.

h3. Referred Person
PO: Associated with: the nature of association is unclear, so we use the weaker P67_refers_to
{code}
<obj> P128_carries <obj/concept/N>.
<obj/concept/N> a E73_Information_Object; P67_refers_to <person>.
{code}

h3. Person in Inscription
PI: Named in inscription
{code}
<obj> P65_shows_visual_item <obj/inscription/N>.
<obj/inscription/N> a E34_Inscription; P138_represents <person>; P2_has_type <type>.
{code}

h3. Person Depicted and in Inscription
II: Named in inscription & portrayed

The object has two P65_shows_visual_item: the portrait itself, and the inscription.
{code}
<obj> P62_depicts <person>.
<obj> P65_shows_visual_item <obj/image/N>, <obj/inscription/N>.
<obj/image/N> a E38_Image; P138_represents <person>; P2_has_type <type>.
<obj/inscription/N> a E34_Inscription; P138_represents <person>; P2_has_type <type>.
{code}

h3. Made For Person
F: Made for
PP: Authorised or patronised by
Map the same as [#Production Motivated By]

h3. Repaired By
RP: Repaired by
{code}
<obj/repair> a E11_Modification; P2_has_type <thesaurus/modification/repaired>;
P14_carried_out_by <person>.
{code}

h2. Associated Place

h3. Depicted Place
IT: Topographic representation of
PA: allegory/personification
EE: Emblem of: M.Doerr argues a place can have no emblem, but it's too complicated to make an anonymous group having its residence there
{code}
<obj> P62_depicts <place>.
<obj> P65_shows_visual_item <obj/image/N>.
<obj/image/N> a E38_Image; P138_represents <place>; P2_has_type <type>.
{code}

h3. Referred Place
AW: Associated with: the nature of association is unclear, so we use the weaker P67_refers_to
Essentially the same as [#Referred Person]
{code}
<obj> P128_carries <obj/concept/N>.
<obj/concept/N> a E73_Information_Object; P67_refers_to <place>.
{code}

h3. Made For Place
MF: Made for

Map essentially the same as [#Production Motivated By]
{code}
<obj> P108i_was_produced_by <obj/production/M>.
<obj/production/M> a E12_Production; P17_was_motivated_by <place>.
<obj/production/M/association> a bmo:EX_Association;
P140_assigned_attribute_to <obj/production/M>; P141_assigned <place>; bmo:PX_property P17_was_motivated_by;
P2_has_type <type>.
{code}

h3. Place in Inscription
NI: Named in inscription
Map essentially the same as [#Person in Inscription]
{code}
<obj> P65_shows_visual_item <obj/inscription/N>.
<obj/inscription/N> a E34_Inscription; P138_represents <place>; P2_has_type <type>.
{code}

h3. Natural Source
NS: Natural source
A raw material used in the object comes from Place. This is complicated (and is used in only 13 objects):
- a Material is a conceptual thing, so it doesn't have a location
- we say the Material was Created at Place, although that sounds a bit silly
- we should say the Material was P126_employed in the object's Production, but that is too complex, so we just say the Material P45i_is_incorporated_in the object
{code}
<obj> P45_consists_of <obj/material>.
<obj/material/M> P94i_was_created_by <obj/material/M/creation>.
<obj/material/M/creation> P7_took_place_at <place>.
{code}

h3. Original From
OF: Original from

The object bears the features of an original that is from Place
{code}
<obj> P130_shows_features_of <obj/original/N>.
<obj/original/N> P108i_was_produced_by <obj/original/production>.
<obj/original/N/production> P7_took_place_at <place>; P2_has_type <type>.
{code}

h3. Repaired In
RP: Repaired in
{code}
<obj/repair> a E11_Modification; P2_has_type <thesaurus/modification/repaired>;
P7_took_place_at <place>.
{code}

h2. Associated Event

h3. Made for Event
DF: Designed for
{code}
<obj> P19i_was_made_for <event>.
<obj> P12i_was_present_at <event>.
{code}

h3. Used at Event
IU: Used at
{code}
<obj> P12i_was_present_at <event>.
{code}

h3. Referred Event
IW: Associated Event
Similar to [#Referred Place]
{code}
<obj> P128_carries <obj/concept/N>.
<obj/concept/N> a E73_Information_Object; P67_refers_to <event>.
{code}

h3. Commemorates Event
IC: Commemoration of
{code}
<obj> P128_carries <obj/concept/N>.
<obj/concept/N> a E73_Information_Object; bmo:PX_commemorates <event>.
{code}
where bmo:PX_commemorates is a subprop of P67_refers_to

h3. Event in Inscription
PI: Named in Inscription
Map essentially the same as [#Person in Inscription]
{code}
<obj> P65_shows_visual_item <obj/inscription/N>.
<obj/inscription/N> a E34_Inscription; P138_represents <event>.
{code}

h2. Associated Title
EI: Title
IT: Associated Title (will use <type> thesauri/association/associatedwith which is the same as any other 'Associated With' code used)
TI: Inscription from

This code associates a free text, which is the Title of a work of art (eg Koran, Ramayana, etc). It's not the title *of* the object, yet is a title that the object *carries*
{code}
<obj> P128_carries <obj/title/N>.
<obj/title/N> a E35_Title; rdfs:label "text"; P2_has_type <type>.
{code}

h2. Findspot
E: Excavated/Findspot
F: Found/Acquired
Map similarly to [#Found By]:
{code}
<obj> P12i_was_present_at <obj/find>.
<obj/find> a EX_Discovery; P2_has_type <type-TRANSLATED>; P7_took_place_at <place>.
{code}

h2. Inscription Subject
|administrative|list |
|anra motif |literary |
|catalogue |magical |
|commemorative |mathematical |
|construction |medical |
|dedicatory |motto |
|educational |offering formula |
|epistolary |omen |
|epitaph |private |
|financial |religious |
|funerary |ritual |
|invocation |royal |
|legal |scientific |

Strangely, Inscription Subject is a multi-value field independent from the actual Inscription records. So we replicate each Inscription Subject to every Inscription: in this case M iterates over Inscriptions, not over Inscription Subjects.
We use a sub-property, so as not to conflate P2_has_type for different purposes:
{code}
bmo:PX_inscription_subject rdfs:subPropertyOf P2_has_type.

<obj> P65_shows_visual_item <obj/inscription/M>.
<obj/inscription/M> a E34_Inscription; bmo:PX_inscription_subject <subject>.
{code}

h2. Inscription Type
|annotation |maker's mark |retailer's mark |
|bell maker's mark |mark |sacred monogram |
|casemaker's mark |merchant's mark |seal |
|control mark |mintmark |seal impression |
|countermark |monogram |signature |
|denominational mark |overstamp |signature and date |
|dial maker's mark |owner's mark |signature/monogram |
|dust-cap maker's mark |pewter mark |tamgha |
|ebauche mark |pottery mark |trade mark |
|hallmark |reign mark |vineyard mark |
|inscription |repair mark |watch pendant maker's mark|
|lettering | | |

We use a sub-property, so as not to conflate P2_has_type for different purposes:
{code}
bmo:PX_inscription_type rdfs:subPropertyOf P2_has_type.

<obj> P65_shows_visual_item <obj/inscription/M>.
<obj/inscription/M> a E34_Inscription; bmo:PX_inscription_type <type>.
{code}

h2. Ethnic Group

h3. Referred Group
AW: Associated with
Similar to [#Referred Place]

{code}
<obj> P128_carries <obj/concept/N>.
<obj/concept/N> a E73_Information_Object; P67_refers_to <group>.
{code}

h3. Depicted Group
IR: Representation of
{code}
<obj> P62_depicts <group>.
<obj> P65_shows_visual_item <obj/image/N>.
<obj/image/N> a E38_Image; P138_represents <group>; P2_has_type <type>.
{code}


h3. Made By Group
M: Made by
{code}
<obj> P108i_was_produced_by <obj/production/M>.
<obj/production/M> P14_carried_out_by <group>.
{code}

h2. Location Availability
This association carries a free text describing the actual location. We should publish this text only:
- if the code is "G: on display", or
- if the department is Prints and Drawings

The code itself is not published.
{code}
<obj> P55_has_current_location <obj/location>.
<obj/location> a E53_Place; rdfs:label "text".
{code}