[crm-sig] CIDOC CRM in RDFS

martin martin at ics.forth.gr
Fri Oct 12 17:57:13 EEST 2001


Dear All,

Attached the CIDOC CRM version 3.2 (latest) in RDFS, plus an exampe instance.
In the RDFS version, for convenience of use in RDF, we have implemented all properties
twice, forward and backward, marked by a "F" or "B" after the id. Properties of properties
are not implemented in this version. References to universals like "in the role of" can be
implemented by dynamically subtyping properties like "carried out by".

Martin

--

--------------------------------------------------------------
 Dr. Martin Doerr              |  Vox:+30(81)391625          |
 Senior Researcher             |  Fax:+30(81)391609          |
 Project Leader SIS            |  Email: martin at ics.forth.gr |
                                                             |
               Centre for Cultural Informatics               |
               Information Systems Laboratory                |
                Institute of Computer Science                |
   Foundation for Research and Technology - Hellas (FORTH)   |
                                                             |
 Vassilika Vouton,P.O.Box1385,GR71110 Heraklion,Crete,Greece |
                                                             |
         Web-site: http://www.ics.forth.gr/proj/isst         |
--------------------------------------------------------------

-------------- next part --------------
<?xml version="1.0"?>
<!-- edited with XML Spy v3.5 NT (http://www.xmlspy.com) by sis ICS-FORTH (ISL-ICS) -->
<!--Partial Definition of the oo CIDOC Reference Model in RDF

    May 24 2000 -->
<rdf:RDF xml:lang="en" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
	<!--E1 CRM Entity-->
	<rdfs:Class rdf:ID="E1.CRM_Entity">
		<rdfs:comment>This is the abstract concept of the entities of our

     universe of discourse. It carries the rule that all entities can

     be classified by a type, which further refines the specific

     subclass an instance belongs to, and a free text field for

     anything we want to express and that is not captured by formal

     links.

  </rdfs:comment>
	</rdfs:Class>
	<rdf:Property rdf:ID="P1F.is_identified_by">
		<rdfs:domain rdf:resource="#E1.CRM_Entity"/>
		<rdfs:range rdf:resource="#E41.Appellation"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P1B.identifies">
		<rdfs:domain rdf:resource="#E41.Appellation"/>
		<rdfs:range rdf:resource="#E1.CRM_Entity"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P2F.has_type">
		<rdfs:domain rdf:resource="#E1.CRM_Entity"/>
		<rdfs:range rdf:resource="#E55.Type"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P2B.is_type_of">
		<rdfs:domain rdf:resource="#E55.Type"/>
		<rdfs:range rdf:resource="#E1.CRM_Entity"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P3F.has_note">
		<rdfs:domain rdf:resource="#E1.CRM_Entity"/>
		<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
	</rdf:Property>
	<!--E2 Temporal Entity -->
	<rdfs:Class rdf:ID="E2.Temporal_Entity">
		<rdfs:comment>This is an abstract entity and has no examples. It

     groups together things such as events, states and other phenomena

     which are limited in time. It is specialized into Period,

     which holds on some geographic area, and Condition State,

     which holds for, on, or over a certain object.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E1.CRM_Entity"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P4F.has_time-span">
		<rdfs:comment>Outer bounds for the real time span things

     happened in.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E2.Temporal_Entity"/>
		<rdfs:range rdf:resource="#E52.Time-Span"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P4B.is_time-span_of">
		<rdfs:comment>Outer bounds for the real time span things

     happened in.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E52.Time-Span"/>
		<rdfs:range rdf:resource="#E2.Temporal_Entity"/>
	</rdf:Property>
	<!--E3 Condition State-->
	<rdfs:Class rdf:ID="E3.Condition_State">
		<rdfs:comment>The state of an object characterized by a certain

     condition and a time-span, e.g. "In ruins from 1695 until 1952",

     where the qualifier "in ruins" is represented as the condition

     state type.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E2.Temporal_Entity"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P5F.consists_of">
		<rdfs:domain rdf:resource="#E3.Condition_State"/>
		<rdfs:range rdf:resource="#E3.Condition_State"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P5B.forms_part_of">
		<rdfs:domain rdf:resource="#E3.Condition_State"/>
		<rdfs:range rdf:resource="#E3.Condition_State"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P6F.falls_within">
		<rdfs:domain rdf:resource="#E3.Condition_State"/>
		<rdfs:range rdf:resource="#E3.Condition_State"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P6B.contains">
		<rdfs:domain rdf:resource="#E3.Condition_State"/>
		<rdfs:range rdf:resource="#E3.Condition_State"/>
	</rdf:Property>
	<!--E4 Period -->
	<rdfs:Class rdf:ID="E4.Period">
		<rdfs:comment>A period is characterized by a coherent set of

     phenomena and or manifestations .explicitly intended or not.,

     which are assumed to have taken place over a certain space

     and time.



     Examples: Glacial period, bronze period, Ming Dynasty,

     Impressionism, Neolithic Period, Mc Carthy Era, The Sixties,

     Niniveh, 'Sturm und Drang'.



     There are different opinions as to whether a ?style? is

     defined by physical features or by the historical

     context.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E2.Temporal_Entity"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P7F.took_place_at">
		<rdfs:comment>Denotes eventually a wider region than the real spot

     things happened on.May be took place at would be a better name

     for this link.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E4.Period"/>
		<rdfs:range rdf:resource="#E53.Place"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P7B.witnessed">
		<rdfs:comment>Denotes eventually a wider region than the real spot

     things happened on.May be took place at would be a better name

     for this link.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E53.Place"/>
		<rdfs:range rdf:resource="#E4.Period"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P8F.took_place_on_or_within">
		<rdfs:domain rdf:resource="#E4.Period"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P8B.witnessed">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E4.Period"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P9F.consists_of">
		<rdfs:comment>Aggregation of subperiods, the total of which

     completely cover the places and times there things really

     happened, used if time spans are different for different

     places .better name "composed of"?.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E4.Period"/>
		<rdfs:range rdf:resource="#E4.Period"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P9B.forms_part_of">
		<rdfs:comment>Aggregation of subperiods, the total of which

     completely cover the places and times there things really

     happened, used if time spans are different for different

     places .better name "composed of"?.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E4.Period"/>
		<rdfs:range rdf:resource="#E4.Period"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P10F.falls_within">
		<rdfs:domain rdf:resource="#E4.Period"/>
		<rdfs:range rdf:resource="#E4.Period"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P10B.contains">
		<rdfs:domain rdf:resource="#E4.Period"/>
		<rdfs:range rdf:resource="#E4.Period"/>
	</rdf:Property>
	<!--E5 Event -->
	<rdfs:Class rdf:ID="E5.Event">
		<rdfs:comment>A change of state in cultural, social, physical

     systems, regardless of scale, brought about by a series or group

     of coherent physical, cultural, technological or legal phenomena.



     Examples : World War II, Battle of Stalingrad, Earthquake in

     Lisbon, birth of Cleopatra, my birthday celebration 28-6-1995,

     the Yal ta Conference, "a tile fell from my roof", the CIDOC

     Conference 2005.



     The distinction between and event and a period is partly a

     question of scale.Viewed at a broad scale, an event is an

     "instantaneous" change of state. At a fine scale, the event

     can be analysed into its component phenomena within a space and

     time frame,i.e., a period. The reverse is not necessarily

     the case, not all periods give rise to a noteworthy change of

     state.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E4.Period"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P11F.had_participants">
		<rdfs:domain rdf:resource="#E5.Event"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P11B.participated_in">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E5.Event"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P12F.ocurred_in_the_presence_of">
		<rdfs:domain rdf:resource="#E5.Event"/>
		<rdfs:range rdf:resource="#E70.Stuff"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P12B.was_present_at">
		<rdfs:domain rdf:resource="#E70.Stuff"/>
		<rdfs:range rdf:resource="#E5.Event"/>
	</rdf:Property>
	<!--E6 Destruction-->
	<rdfs:Class rdf:ID="E6.Destruction">
		<rdfs:comment>An event which causes one or more objects to lose

     their identity as the current subjects of documentation.

     Some destructions are intentional, others are independent of

     human activity. The decision as to the point at which an object

     is destroyed rather than modified may be arbitrary in some cases.

     The same event may, in some cases, be documented both as a

     destruction of one or more objects and as the creation of others

     using parts or material from the original, or, alternatively,

     as a modification.  In the former case, the object

     record would close, in the latter, it would continue.



     For living beings, death is usually more clearly defined.



     Examples: The Lisbon Earthquake, the destruction of Nineveh,

     I broke a champagne glass yesterday, the shooting of the last

     wolf in Germany in 1729.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E64.End_of_Existence"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P13F.destroyed">
		<rdfs:domain rdf:resource="#E6.Destruction"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
		<rdfs:subPropertyOf rdf:resource="#P12F.ocurred_in_the_presence_of"/>
		<rdfs:subPropertyOf rdf:resource="#P93F.took_out_of_existence"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P13B.was_destroyed_by">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E6.Destruction"/>
		<rdfs:subPropertyOf rdf:resource="#P12B.was_present_at"/>
		<rdfs:subPropertyOf rdf:resource="#P93B.was_taken_out_of_existence_by"/>
	</rdf:Property>
	<!--E7 Activity-->
	<rdfs:Class rdf:ID="E7.Activity">
		<rdfs:comment>An action or a series of actions, carried out by

     actors .people, groups or organisations. which follow a certain

     explicit or implicit intention and result as a collective effect

     in some change of state in the cultural, social, physical systems

     we are interested in. This notion includes both complex

     and long lasting actions such as the building of a settlement, or

     a war, as well as simple, short-lived actions such as the opening

     of a door. It does not include the notion of activity in the

     sense of professions and other non-targeted

     notions. These are seen rather as belonging to a part

     in the hierarchy above Event.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E5.Event"/>
	</rdfs:Class>
	<!--COMMENT: In the CRM this link has a link: .in the role of: Type.

    In RDFs we propose to the user to create a subproperty of this link 

    for each type of role.-->
	<rdf:Property rdf:ID="P14F.carried_out_by">
		<rdfs:domain rdf:resource="#E7.Activity"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
		<rdfs:subPropertyOf rdf:resource="#P11F.had_participants"/>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has a link: .in the role of: Type.

    In RDFs we propose to the user to create a subproperty of this link 

    for each type of role.-->
	<rdf:Property rdf:ID="P14B.performed">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E7.Activity"/>
		<rdfs:subPropertyOf rdf:resource="#P11B.participated_in"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P15F.took_into_account">
		<rdfs:domain rdf:resource="#E7.Activity"/>
		<rdfs:range rdf:resource="#E28.Conceptual_Object"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P15B.was_taken_into_account_by">
		<rdfs:domain rdf:resource="#E28.Conceptual_Object"/>
		<rdfs:range rdf:resource="#E7.Activity"/>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has a link: .mode of use: String.-->
	<rdf:Property rdf:ID="P16F.used_object">
		<rdfs:domain rdf:resource="#E7.Activity"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
		<rdfs:subPropertyOf rdf:resource="#P12F.ocurred_in_the_presence_of"/>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has a link: .mode of use: String.-->
	<rdf:Property rdf:ID="P16B.was_used_for">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E7.Activity"/>
		<rdfs:subPropertyOf rdf:resource="#P12B.was_present_at"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P17F.was_motivation_for">
		<rdfs:domain rdf:resource="#E7.Activity"/>
		<rdfs:range rdf:resource="#E28.Conceptual_Object"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P17B.motivated">
		<rdfs:domain rdf:resource="#E28.Conceptual_Object"/>
		<rdfs:range rdf:resource="#E7.Activity"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P18F.motivated_the_creation_of">
		<rdfs:domain rdf:resource="#E7.Activity"/>
		<rdfs:range rdf:resource="#E28.Conceptual_Object"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P18B.was_created_for">
		<rdfs:domain rdf:resource="#E28.Conceptual_Object"/>
		<rdfs:range rdf:resource="#E7.Activity"/>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has a link: .mode of use: String.-->
	<rdf:Property rdf:ID="P19F.was_intended_use_of">
		<rdfs:domain rdf:resource="#E7.Activity"/>
		<rdfs:range rdf:resource="#E22.Man-Made_Object"/>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has a link: .mode of use: String.-->
	<rdf:Property rdf:ID="P19B.was_made_for">
		<rdfs:domain rdf:resource="#E22.Man-Made_Object"/>
		<rdfs:range rdf:resource="#E7.Activity"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P20F.had_specific_purpose">
		<rdfs:comment>E.g. making of a gift for the wedding of king

     George

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E7.Activity"/>
		<rdfs:range rdf:resource="#E7.Activity"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P20B.was_purpose_of">
		<rdfs:comment>E.g. making of a gift for the wedding of king

     George

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E7.Activity"/>
		<rdfs:range rdf:resource="#E7.Activity"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P21F.had_as_general_purpose">
		<rdfs:comment>E.g. making of a dress for wedding.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E7.Activity"/>
		<rdfs:range rdf:resource="#E55.Type"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P21B.was_purpose_of">
		<rdfs:comment>E.g. making of a dress for wedding.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E55.Type"/>
		<rdfs:range rdf:resource="#E7.Activity"/>
	</rdf:Property>
	<!--E8 Acquisition-->
	<rdfs:Class rdf:ID="E8.Acquisition">
		<rdfs:comment>This entity describes the transfer of the legal

     ownership from one legal person to another. Either one of the

     actors may be omitted, unknown or not existing. The entity

     describes the beginning, the end or the transfer of an ownership,

     acquisition from unknown source or loss of title, depending

     on the circumstances. It takes a neutral position with respect to

     the actors involved. The museum notion of "accession" seems to

     differ between institutions.

     We preferred therefore to model the notions of legal ownership

     and physical custody instead, which are well defined in

     international business. Institutions can choose to model their

     specific notions as combinations of these.



     Annexation, donation, purchase, field collection - where legal

     title is appropriated by the collector, are types of acquisition.

     Examples: a fish collected in international waters, a painting

     bequeathed to a museum.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E7.Activity"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P22F.transferred_title_to">
		<rdfs:domain rdf:resource="#E8.Acquisition"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
		<rdfs:subPropertyOf rdf:resource="#P14F.carried_out_by"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P22B.acquired_title_of">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E8.Acquisition"/>
		<rdfs:subPropertyOf rdf:resource="#P14B.performed"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P23F.transferred_title_from">
		<rdfs:domain rdf:resource="#E8.Acquisition"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
		<rdfs:subPropertyOf rdf:resource="#P14F.carried_out_by"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P23B.surrendered_title_of">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E8.Acquisition"/>
		<rdfs:subPropertyOf rdf:resource="#P14B.performed"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P24F.transferred_title_of">
		<rdfs:domain rdf:resource="#E8.Acquisition"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
		<rdfs:subPropertyOf rdf:resource="#P12F.ocurred_in_the_presence_of"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P24B.changed_ownership_by">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E8.Acquisition"/>
		<rdfs:subPropertyOf rdf:resource="#P12B.was_present_at"/>
	</rdf:Property>
	<!--E9 Move-->
	<rdfs:Class rdf:ID="E9.Move">
		<rdfs:comment>This entity captures the change of physical location

     of a museum object for exhibitions, conservation, reorganization,

     loans, study etc.



     e.g. Taking objects from storage and putting them on display is

     a type of move.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E7.Activity"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P25F.moved">
		<rdfs:domain rdf:resource="#E9.Move"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
		<rdfs:subPropertyOf rdf:resource="#P12F.ocurred_in_the_presence_of"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P25B.moved_by">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E9.Move"/>
		<rdfs:subPropertyOf rdf:resource="#P12B.was_present_at"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P26F.moved_to">
		<rdfs:domain rdf:resource="#E9.Move"/>
		<rdfs:range rdf:resource="#E53.Place"/>
		<rdfs:subPropertyOf rdf:resource="#P7F.took_place_at"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P26B.occupied">
		<rdfs:domain rdf:resource="#E53.Place"/>
		<rdfs:range rdf:resource="#E9.Move"/>
		<rdfs:subPropertyOf rdf:resource="#P7B.witnessed"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P27F.moved_from">
		<rdfs:domain rdf:resource="#E9.Move"/>
		<rdfs:range rdf:resource="#E53.Place"/>
		<rdfs:subPropertyOf rdf:resource="#P7F.took_place_at"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P27B.vacated">
		<rdfs:domain rdf:resource="#E53.Place"/>
		<rdfs:range rdf:resource="#E9.Move"/>
		<rdfs:subPropertyOf rdf:resource="#P7B.witnessed"/>
	</rdf:Property>
	<!--E10 Transfer of Custody-->
	<rdfs:Class rdf:ID="E10.Transfer_of_Custody">
		<rdfs:comment>This entity describes the transfer of physical custody

     from one legal person to another. Either one of the actors may be

     omitted, unknown or not existing. The entity may describe the

     beginning, the end or the transfer of custody, field collection

     or declared loss of an object, depending on the circumstances.

     It takes a neutral position with respect to the actors involved.



     The distinction between legal and physical custody can be

     modelled as types.



     Some events can simultaneously be considered as acquisition,

     transfer of custody and move. For example, purchase of a

     Polynesian feather hat at a market. In other cases, separate

     events are involved,

     e.g. purchase by telephone of an object on auction, physical

     transportation, and reception by the new owner.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E7.Activity"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P28F.custody_surrendered_by">
		<rdfs:domain rdf:resource="#E10.Transfer_of_Custody"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
		<rdfs:subPropertyOf rdf:resource="#P14F.carried_out_by"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P28B.surrendered_custody">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E10.Transfer_of_Custody"/>
		<rdfs:subPropertyOf rdf:resource="#P14B.performed"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P29F.custody_received_by">
		<rdfs:domain rdf:resource="#E10.Transfer_of_Custody"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
		<rdfs:subPropertyOf rdf:resource="#P14F.carried_out_by"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P29B.received_custody">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E10.Transfer_of_Custody"/>
		<rdfs:subPropertyOf rdf:resource="#P14B.performed"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P30F.transferred_custody_of">
		<rdfs:domain rdf:resource="#E10.Transfer_of_Custody"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
		<rdfs:subPropertyOf rdf:resource="#P12F.ocurred_in_the_presence_of"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P30B.custody_changed_by">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E10.Transfer_of_Custody"/>
		<rdfs:subPropertyOf rdf:resource="#P12B.was_present_at"/>
	</rdf:Property>
	<!--E11 Modification-->
	<rdfs:Class rdf:ID="E11.Modification">
		<rdfs:comment>This entity comprises all activities which

     intentionally alter physical objects, regardless of the degree

     of intervention: creation of some item from raw material,

     restorations, use of ancient objects in jewelry, etc..

     Since many cases the distinction between modification and creation

     is not clear, and the actions implied are basically the same,

     modification is regarded as the more general .and less ambiguous.

     concept. This implies that some items may be consumed or

     destroyed in a modification process, and others emerge from it.

     Typically, objects involved in the process, such as tools,

     materials, etc., which are foreseen by the applied technique are

     modeled as attributes of the Design or Procedure, for reasons of

     efficient data representation.

     Nevertheless, unusual and remarkable items used for a specific

     instance of aprocess should be referred to here.



     This entity is thought to be collective, e.g. the printing of a

     thousand books should be one event. Conservation actions can be

     modeled as a type of modification.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E7.Activity"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P31F.has_modified">
		<rdfs:domain rdf:resource="#E11.Modification"/>
		<rdfs:range rdf:resource="#E24.Physical_Man-Made_Stuff"/>
		<rdfs:subPropertyOf rdf:resource="#P12F.ocurred_in_the_presence_of"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P31B.was_modified_by">
		<rdfs:domain rdf:resource="#E24.Physical_Man-Made_Stuff"/>
		<rdfs:range rdf:resource="#E11.Modification"/>
		<rdfs:subPropertyOf rdf:resource="#P12B.was_present_at"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P32F.used_general_technique">
		<rdfs:domain rdf:resource="#E11.Modification"/>
		<rdfs:range rdf:resource="#E55.Type"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P32B.was_technique_of">
		<rdfs:domain rdf:resource="#E55.Type"/>
		<rdfs:range rdf:resource="#E11.Modification"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P33F.used_specific_technique">
		<rdfs:domain rdf:resource="#E11.Modification"/>
		<rdfs:range rdf:resource="#E29.Design_or_Procedure"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P33B.was_used_by">
		<rdfs:domain rdf:resource="#E29.Design_or_Procedure"/>
		<rdfs:range rdf:resource="#E11.Modification"/>
	</rdf:Property>
	<!--E12 Production-->
	<rdfs:Class rdf:ID="E12.Production">
		<rdfs:comment>This entity specializes the notion of modification

     into production, i.e. activities which are designed to and

     succeed in creating one or a series of new items, new in the

     sense that there is no obvious similarity to the consumed items

     and material.

     Examples: painting a watercolour, printing an etching, producing

     a series of household forks, the recasting of the mermaid in

     Copenhagen.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E11.Modification"/>
		<rdfs:subClassOf rdf:resource="#E63.Beginning_of_Existence"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P108F.has_produced">
		<rdfs:domain rdf:resource="#E12.Production"/>
		<rdfs:range rdf:resource="#E24.Physical_Man-Made_Stuff"/>
		<rdfs:subPropertyOf rdf:resource="#P31F.has_modified"/>
		<rdfs:subPropertyOf rdf:resource="#P92F.brought_into_existence"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P108B.was_produced_by">
		<rdfs:domain rdf:resource="#E24.Physical_Man-Made_Stuff"/>
		<rdfs:range rdf:resource="#E12.Production"/>
		<rdfs:subPropertyOf rdf:resource="#P31B.was_modified_by"/>
		<rdfs:subPropertyOf rdf:resource="#P92B.was_brought_into_existence_by"/>
	</rdf:Property>
	<!--E13 Attribute Assignment-->
	<rdfs:Class rdf:ID="E13.Attribute_Assignment">
		<rdfs:comment>This entity comprises the actions of making assertions

     about properties of an object. It serves the documentation of how

     the respective assessment came about, and whose opinion it was.

     All the attributes or properties assigned in such an action can

     also be seen as directly attached to the respective object,

     possibly as a collection of contradictory values. All cases of

     direct links from objects to values which are, in this model,

     also referred to indirectly through an action, are characterized

     as "short cuts" of this action. This redundant modeling of two

     alternative views is preferred because many implementations may

     have good reasons to model either the action or the short cut,

     and the relation between both alternatives can be captured by

     simple rules.



     In addition, the entity describes the actions of people making

     propositions and statements during certain museum procedures,

     e.g. the person and date when a condition statement was made, an

     identifier was assigned, the museum object was measured, etc..

     Which kinds of such assignments and statements need to be

     documented explicitly in schema structures rather than free text,

     depends on a museum=B4s practice. In the latter case shortcuts may

     be used which refer directly to the museum object.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E7.Activity"/>
	</rdfs:Class>
	<!--E14 Condition Assessment-->
	<rdfs:Class rdf:ID="E14.Condition_Assessment">
		<rdfs:comment>This entity describes the action of assessing the

     condition of preservation of an object over a particular period,

     either by inspection, measurement or historical

     studies.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E13.Attribute_Assignment"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P34F.concerned">
		<rdfs:domain rdf:resource="#E14.Condition_Assessment"/>
		<rdfs:range rdf:resource="#E18.Physical_Stuff"/>
		<rdfs:subPropertyOf rdf:resource="#P12F.ocurred_in_the_presence_of"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P34B.was_assessed_by">
		<rdfs:domain rdf:resource="#E18.Physical_Stuff"/>
		<rdfs:range rdf:resource="#E14.Condition_Assessment"/>
		<rdfs:subPropertyOf rdf:resource="#P12B.was_present_at"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P35F.has_identified">
		<rdfs:domain rdf:resource="#E14.Condition_Assessment"/>
		<rdfs:range rdf:resource="#E3.Condition_State"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P35B.identified_by">
		<rdfs:domain rdf:resource="#E3.Condition_State"/>
		<rdfs:range rdf:resource="#E14.Condition_Assessment"/>
	</rdf:Property>
	<!--E15 Identifier Assignment-->
	<rdfs:Class rdf:ID="E15.Identifier_Assignment">
		<rdfs:comment>This entity describes the action of assigning an

     identifier, such as a museum number, to an object. The interest

     in this action arises when objects are exchanged, and multiple

     identifiers are used, or the identification system of an

     organization is changed. In order to cover these cases, it is

     important to document by whom, when and for what purpose an

     identifier is assigned to a museum object.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E13.Attribute_Assignment"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P36F.registered">
		<rdfs:domain rdf:resource="#E15.Identifier_Assignment"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
		<rdfs:subPropertyOf rdf:resource="#P12F.ocurred_in_the_presence_of"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P36B.registered_by">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E15.Identifier_Assignment"/>
		<rdfs:subPropertyOf rdf:resource="#P12B.was_present_at"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P37F.assigns">
		<rdfs:domain rdf:resource="#E15.Identifier_Assignment"/>
		<rdfs:range rdf:resource="#E42.Object_Identifier"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P37B.is_assigned_by">
		<rdfs:domain rdf:resource="#E42.Object_Identifier"/>
		<rdfs:range rdf:resource="#E15.Identifier_Assignment"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P38F.deassigns">
		<rdfs:domain rdf:resource="#E15.Identifier_Assignment"/>
		<rdfs:range rdf:resource="#E42.Object_Identifier"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P38B.is_deassigned_by">
		<rdfs:domain rdf:resource="#E42.Object_Identifier"/>
		<rdfs:range rdf:resource="#E15.Identifier_Assignment"/>
	</rdf:Property>
	<!--E16 Measurement-->
	<rdfs:Class rdf:ID="E16.Measurement">
		<rdfs:comment>This entity describes actions of measuring physical

     properties by counting or use of some tool, whether by simple

     yardstick or complex radiation detection device. The interest

     is in the method and care applied, in order to decide afterwards

     on the reliability of the result. For properties which may change

     value over time, such as length, due to shrinkage, the date is

     of direct relevance as well. Details of methods and devices are

     best handled as free text, whereas basic methods such as "C14"

     should be encoded in the type field.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E13.Attribute_Assignment"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P39F.measured">
		<rdfs:comment>This link has to be specialized further in

     subclasses.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E16.Measurement"/>
		<rdfs:range rdf:resource="#E18.Physical_Stuff"/>
		<rdfs:subPropertyOf rdf:resource="#P12F.ocurred_in_the_presence_of"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P39B.was_measured">
		<rdfs:comment>This link has to be specialized further in

     subclasses.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E18.Physical_Stuff"/>
		<rdfs:range rdf:resource="#E16.Measurement"/>
		<rdfs:subPropertyOf rdf:resource="#P12B.was_present_at"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P40F.observed_dimension">
		<rdfs:comment>This link has to be specialized further in subclasses.

     Examples: hight, length, diameter of base,

     major hight etc.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E16.Measurement"/>
		<rdfs:range rdf:resource="#E54.Dimension"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P40B.was_observed">
		<rdfs:comment>This link has to be specialized further in subclasses.

     Examples: hight, length, diameter of base,

     major hight etc.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E54.Dimension"/>
		<rdfs:range rdf:resource="#E16.Measurement"/>
	</rdf:Property>
	<!--E17 Type Assignment-->
	<rdfs:Class rdf:ID="E17.Type_Assignment">
		<rdfs:comment>This entity describes the act of scientifically

     classifying some entity, an object, a work, an action or whatever.

     The value of classification depends critically on general and

     personal knowledge and the scientific system used. Therefore the

     interest lies in the author and date.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E13.Attribute_Assignment"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P41F.classified">
		<rdfs:domain rdf:resource="#E17.Type_Assignment"/>
		<rdfs:range rdf:resource="#E1.CRM_Entity"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P41B.was_classified_by">
		<rdfs:domain rdf:resource="#E1.CRM_Entity"/>
		<rdfs:range rdf:resource="#E17.Type_Assignment"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P42F.assigned">
		<rdfs:domain rdf:resource="#E17.Type_Assignment"/>
		<rdfs:range rdf:resource="#E55.Type"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P42B.was_assigned_by">
		<rdfs:domain rdf:resource="#E55.Type"/>
		<rdfs:range rdf:resource="#E17.Type_Assignment"/>
	</rdf:Property>
	<!--E18 Physical Stuff-->
	<rdfs:Class rdf:ID="E18.Physical_Stuff">
		<rdfs:comment>Physical Stuff is an abstract notion that groups

     all physical objects, man made and natural, as well as physical

     features of objects, such as holes. We use the term 'feature'

     to refer to anything of a material nature, such as scratches,

     holes, rivers, and stains, which it would be strange to refer

     to as ?objects?.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E70.Stuff"/>
		<rdfs:subClassOf rdf:resource="#E72.Legal_Object"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P43F.has_dimension">
		<rdfs:domain rdf:resource="#E18.Physical_Stuff"/>
		<rdfs:range rdf:resource="#E54.Dimension"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P43B.is_dimension_of">
		<rdfs:domain rdf:resource="#E54.Dimension"/>
		<rdfs:range rdf:resource="#E18.Physical_Stuff"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P44F.has_condition">
		<rdfs:domain rdf:resource="#E18.Physical_Stuff"/>
		<rdfs:range rdf:resource="#E3.Condition_State"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P44B.condition_of">
		<rdfs:domain rdf:resource="#E3.Condition_State"/>
		<rdfs:range rdf:resource="#E18.Physical_Stuff"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P45F.consists_of">
		<rdfs:domain rdf:resource="#E18.Physical_Stuff"/>
		<rdfs:range rdf:resource="#E57.Material"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P45B.is_incorporated_in">
		<rdfs:domain rdf:resource="#E57.Material"/>
		<rdfs:range rdf:resource="#E18.Physical_Stuff"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P46F.is_composed_of">
		<rdfs:domain rdf:resource="#E18.Physical_Stuff"/>
		<rdfs:range rdf:resource="#E18.Physical_Stuff"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P46B.forms_part_of">
		<rdfs:domain rdf:resource="#E18.Physical_Stuff"/>
		<rdfs:range rdf:resource="#E18.Physical_Stuff"/>
	</rdf:Property>
	<!--E19 Physical Object-->
	<rdfs:Class rdf:ID="E19.Physical_Object">
		<rdfs:comment>An discrete, real item of material nature which

     constitutes a unit for documentation. The decision as to what

     constitutes a complete item, rather than parts or components,

     may be purely administrative.



     Examples : John Smith, Aphrodite of Milos, the Palace of Knossos,

     the Cullinan diamond, Apollo 13 a the time

     of launch.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E18.Physical_Stuff"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P47F.is_identified_by">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E42.Object_Identifier"/>
		<rdfs:subPropertyOf rdf:resource="#P1F.is_identified_by"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P47B.identifies">
		<rdfs:domain rdf:resource="#E42.Object_Identifier"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
		<rdfs:subPropertyOf rdf:resource="#P1B.identifies"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P48F.preferred_identifier_is">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E42.Object_Identifier"/>
		<rdfs:subPropertyOf rdf:resource="#P47F.is_identified_by"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P48B.is_preffered_identifier_of">
		<rdfs:domain rdf:resource="#E42.Object_Identifier"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
		<rdfs:subPropertyOf rdf:resource="#P47B.identifies"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P49F.has_former_or_current_keeper">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P49B.is_former_or_current_keeper_of">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P50F.has_current_keeper">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
		<rdfs:subPropertyOf rdf:resource="#P49F.has_former_or_current_keeper"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P50B.is_current_keeper_of">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
		<rdfs:subPropertyOf rdf:resource="#P49B.is_former_or_current_keeper_of"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P51F.has_former_or_current_owner">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P51B.is_former_or_current_owner_of">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P52F.has_current_owner">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
		<rdfs:subPropertyOf rdf:resource="#P51F.has_former_or_current_owner"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P52B.is_current_owner_of">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
		<rdfs:subPropertyOf rdf:resource="#P51B.is_former_or_current_owner_of"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P53F.has_former_or_current_location">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E53.Place"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P53B.is_former_or_current_location_of">
		<rdfs:domain rdf:resource="#E53.Place"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P54F.has_current_permanent_location">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E53.Place"/>
		<rdfs:subPropertyOf rdf:resource="#P53F.has_former_or_current_location"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P54B.is_current_permanent_location_of">
		<rdfs:domain rdf:resource="#E53.Place"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
		<rdfs:subPropertyOf rdf:resource="#P53B.is_former_or_current_location_of"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P55F.has_current_location">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E53.Place"/>
		<rdfs:subPropertyOf rdf:resource="#P53F.has_former_or_current_location"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P55B.currently_holds">
		<rdfs:domain rdf:resource="#E53.Place"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
		<rdfs:subPropertyOf rdf:resource="#P53B.is_former_or_current_location_of"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P56F.bears_feature">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E26.Physical_Feature"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P56B.is_found_on">
		<rdfs:domain rdf:resource="#E26.Physical_Feature"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P57F.has_number_of_parts">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P58F.has_section_definition">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E46.Section_Definition"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P58B.defines_section">
		<rdfs:domain rdf:resource="#E46.Section_Definition"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P59F.has_section">
		<rdfs:domain rdf:resource="#E19.Physical_Object"/>
		<rdfs:range rdf:resource="#E53.Place"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P59B.is_located_on_or_within">
		<rdfs:domain rdf:resource="#E53.Place"/>
		<rdfs:range rdf:resource="#E19.Physical_Object"/>
	</rdf:Property>
	<!--E20 Biological Object-->
	<rdfs:Class rdf:ID="E20.Biological_Object">
		<rdfs:comment>An individual, real item of material nature,

     which lives, has lived, or is a natural products of living

     organisms. Artificial objects which incorporate biological

     elements, such as Victorian butterfly frames, can be classified

     as both natural and man-made objects.



     Examples : Me, Tut-Ankh-Amun, Boukephalas.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E19.Physical_Object"/>
	</rdfs:Class>
	<!--E21 Person-->
	<rdfs:Class rdf:ID="E21.Person">
		<rdfs:comment>A real person, who lives or is assumed to have lived.



     Examples : John Smith, Tut-Ankh-Amun.



     Legendary figures, such as Ulysses and King Arthur, who may have

     existed, fall into this class if the documentation refers to them

     as historical figures. In cases where doubt exists as to whether

     several persons are in fact identical, multiple instances can be

     created and linked to indicate their relationship.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E20.Biological_Object"/>
		<rdfs:subClassOf rdf:resource="#E39.Actor"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P60F.is_member_of">
		<rdfs:domain rdf:resource="#E21.Person"/>
		<rdfs:range rdf:resource="#E40.Legal_Body"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P60B.has_members">
		<rdfs:domain rdf:resource="#E40.Legal_Body"/>
		<rdfs:range rdf:resource="#E21.Person"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P61F.has_gender">
		<rdfs:domain rdf:resource="#E21.Person"/>
		<rdfs:range rdf:resource="#E76.Gender"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P61B.is_gender_of">
		<rdfs:domain rdf:resource="#E76.Gender"/>
		<rdfs:range rdf:resource="#E21.Person"/>
	</rdf:Property>
	<!--E22 Man-Made Object-->
	<rdfs:Class rdf:ID="E22.Man-Made_Object">
		<rdfs:comment>An discrete real item of material nature, which

     is an artifact of technological actions.



     Example : My car, chassis no. AMT-9566-XXX9384,

                  The Portland Vase,

        The Colloseum, The Parthenon.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E19.Physical_Object"/>
		<rdfs:subClassOf rdf:resource="#E24.Physical_Man-Made_Stuff"/>
	</rdfs:Class>
	<!--E23 Iconographic Object-->
	<rdfs:Class rdf:ID="E23.Iconographic_Object">
		<rdfs:comment>This entity comprises objects which are designed

     primarily or in addition to another functionality to represent

     or depict something in an optical manner, be it concrete or

     abstract. Examples: Paintings, Sculpture, a vase in form of

     a head, a decoration on a medieval gun.



     This entity has a certain pragmatic value in the fine arts

     since it conveniently groups together objects such as paintings,

     drawings, watercolours and other similar objects. From a

     philosophical point of view, representation is an 'intentional'

     act. Natural objects may resemble other objects by chance but

     they can represent only as a result of intervention by some fairly

     sophisticated semiotic arrangements.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E22.Man-Made_Object"/>
		<rdfs:subClassOf rdf:resource="#E73.Information_Object"/>
	</rdfs:Class>
	<!--E24 Physical Man-Made Stuff-->
	<rdfs:Class rdf:ID="E24.Physical_Man-Made_Stuff">
		<rdfs:comment>Man-made entity is a general class that groups man

     made objects and features. The distinction between 'objects'

     and 'features' is useful since it avoids referring to things

     like holes and texture as objects. Features and objects share

     many common characteristics however, hence the need for a

     general class of man-made things.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E18.Physical_Stuff"/>
		<rdfs:subClassOf rdf:resource="#E71.Man-Made_Stuff"/>
	</rdfs:Class>
	<!--COMMENT: In the CRM this link has a link:.mode of depiction:Type.

    In RDFs we propose to the user to create a subproperty of this link 

    for each type of role.-->
	<rdf:Property rdf:ID="P62F.depicts_object">
		<rdfs:domain rdf:resource="#E24.Physical_Man-Made_Stuff"/>
		<rdfs:range rdf:resource="#E18.Physical_Stuff"/>
		<rdfs:comment>This link serves particularly to trace

       cross-references to objects in collections, especially in the

       same museum.  Else, a simple textual note would be enough.

       The qualifier mode of depiction captures view, angle, part,

       salience, quality etc.

       If the iconography depicts an existing real object,

       e.g. real person, building, place, or another museum object

       .like it usually happens with photos., the link depicts object

       should be used, pointing to an instance of the Physical Stuff

       class or of any of its subclasses.

       Mode of depiction examples: sketch, caricature,

       animation.

  </rdfs:comment>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has a link:.mode of depiction:Type.

    In RDFs we propose to the user to create a subproperty of this link 

    for each type of role.-->
	<rdf:Property rdf:ID="P62B.is_depicted_by">
		<rdfs:domain rdf:resource="#E18.Physical_Stuff"/>
		<rdfs:comment>This link serves particularly to trace

       cross-references to objects in collections, especially in the

       same museum.  Else, a simple textual note would be enough.

       The qualifier mode of depiction captures view, angle, part,

       salience, quality etc.

       If the iconography depicts an existing real object,

       e.g. real person, building, place, or another museum object

       .like it usually happens with photos., the link depicts object

       should be used, pointing to an instance of the Physical Stuff

       class or of any of its subclasses.

       Mode of depiction examples: sketch, caricature,

       animation.

  </rdfs:comment>
		<rdfs:range rdf:resource="#E24.Physical_Man-Made_Stuff"/>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has a link:.mode of depiction:Type.

    In RDFs we propose to the user to create a subproperty of this link 

    for each type of role-->
	<rdf:Property rdf:ID="P63F.depicts_event">
		<rdfs:domain rdf:resource="#E24.Physical_Man-Made_Stuff"/>
		<rdfs:range rdf:resource="#E5.Event"/>
		<rdfs:comment>This link serves particularly for cross-references

       to archives and history, as above.

       If the iconography depicts a real Event, e.g. the battle of

       Bankerhill, the link depicts Event should be used, pointing to

       an instance of the class Event. Depicted events of which the

       time or place are out of interest, e.g. mythological &amp;

       religious events, should by regarded as

       Event Types.

  </rdfs:comment>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has a link:.mode of depiction:Type.

    In RDFs we propose to the user to create a subproperty of this link 

    for each type of role.-->
	<rdf:Property rdf:ID="P63B.is_depicted_by">
		<rdfs:domain rdf:resource="#E5.Event"/>
		<rdfs:comment>This link serves particularly for cross-references

       to archives and history, as above.

       If the iconography depicts a real Event, e.g. the battle of

       Bankerhill, the link depicts Event should be used, pointing to

       an instance of the class Event. Depicted events of which the

       time or place are out of interest, e.g. mythological &amp;

       religious events, should by regarded as

       Event Types.

  </rdfs:comment>
		<rdfs:range rdf:resource="#E24.Physical_Man-Made_Stuff"/>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has a link:.mode of depiction:Type.

    In RDFs we propose to the user to create a subproperty of this link 

    for each type of role.-->
	<rdf:Property rdf:ID="P64F.depicts_concept">
		<rdfs:domain rdf:resource="#E24.Physical_Man-Made_Stuff"/>
		<rdfs:range rdf:resource="#E55.Type"/>
		<rdfs:comment>This link replaces the usual subject. If the links

       above are used, it is recommended to conclude on the subject

       from the type of the referred object, if the subject  is not

       different from that. This avoids redundancy and inconsistencies.

       If the iconography depicts a non-specifically identified image,

       e.g. a child, a house, a landscape, a symbol, a motive, the link

       depicts concept should be used, pointing

       to a Type.

  </rdfs:comment>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has a link:.mode of depiction:Type.

    In RDFs we propose to the user to create a subproperty of this link 

    for each type of role.-->
	<rdf:Property rdf:ID="P64B.is_depicted_by">
		<rdfs:domain rdf:resource="#E55.Type"/>
		<rdfs:comment>This link replaces the usual subject. If the links

       above are used, it is recommended to conclude on the subject

       from the type of the referred object, if the subject  is not

       different from that. This avoids redundancy and inconsistencies.

       If the iconography depicts a non-specifically identified image,

       e.g. a child, a house, a landscape, a symbol, a motive, the link

       depicts concept should be used, pointing

       to a Type.

  </rdfs:comment>
		<rdfs:range rdf:resource="#E24.Physical_Man-Made_Stuff"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P65F.shows_visual_item">
		<rdfs:domain rdf:resource="#E24.Physical_Man-Made_Stuff"/>
		<rdfs:range rdf:resource="#E36.Visual_Item"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P65B.is_shown_by">
		<rdfs:domain rdf:resource="#E36.Visual_Item"/>
		<rdfs:range rdf:resource="#E24.Physical_Man-Made_Stuff"/>
	</rdf:Property>
	<!--E25 Man-Made Feature-->
	<rdfs:Class rdf:ID="E25.Man-Made_Feature">
		<rdfs:comment>Man made features are those physical features

     which result from human intervention. Cf.E27 Physical

     Feature.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E24.Physical_Man-Made_Stuff"/>
		<rdfs:subClassOf rdf:resource="#E26.Physical_Feature"/>
	</rdfs:Class>
	<!--E26 Physical Feature-->
	<rdfs:Class rdf:ID="E26.Physical_Feature">
		<rdfs:comment>This class was introduced in order to avoid the

     counter-intuitive sense of referring to holes and similar features

     of objects as physical objects. Features are logically or

     physically attached to a particular physical object, and they

     share many of the attributes of physical objects - they can be

     measured and dated, and we can sometimes say who was responsible

     for them. However, you can't pick up a hole and put it in your

     pocket - Yellow Submarine not withstanding. Physical feature

     groups together all features of physical objects. Cf. Man-made

     features for the results of human intervention.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E18.Physical_Stuff"/>
	</rdfs:Class>
	<!--E27 Site-->
	<rdfs:Class rdf:ID="E27.Site">
		<rdfs:comment>A site is a recognisable place that can be represented

     by an Iconographic object, such as a photograph, painting or map.

     A site is composed of relatively immobile material items and

     features in a particular configuration at a particular

     location.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E26.Physical_Feature"/>
	</rdfs:Class>
	<!--E28 Conceptual Object-->
	<rdfs:Class rdf:ID="E28.Conceptual_Object">
		<rdfs:comment>This entity is the attempt to group the non-material

     products of our minds, and specifically to allow for reasoning

     about their identity, circumstances of creation and historical

     implications. Characteristically, these things are created,

     invented or thought, and somehow documented or communicated

     between persons.

     Conceptual objects need not have a particular carrier, but may be

     found on several different carriers, such as paper, electronic

     signals, marks, audio media, paintings, photos, human memory, etc.

     They cannot be destroyed as long as they exist on at least one

     carrier or in memory. Examples include texts, maps, photos, music,

     sounds, fairy tales, signs, patterns, symbols, plans, rights,

     and rules. A greater distinction could be made between products

     having a clear identity, such as a specific text, or photographs,

     and the ideas and concepts shared and traded by

     groups of people.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E71.Man-Made_Stuff"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P66F.refers_to_concept">
		<rdfs:domain rdf:resource="#E28.Conceptual_Object"/>
		<rdfs:range rdf:resource="#E55.Type"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P66B.is_refered_to_by">
		<rdfs:domain rdf:resource="#E55.Type"/>
		<rdfs:range rdf:resource="#E28.Conceptual_Object"/>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has a link:.mode of depiction:Type.

    In RDFs we propose to the user to create a subproperty of this link 

    for each type of role.-->
	<rdf:Property rdf:ID="P67F.referrs_to">
		<rdfs:domain rdf:resource="#E28.Conceptual_Object"/>
		<rdfs:range rdf:resource="#E1.CRM_Entity"/>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has a link:.mode of depiction:Type.

    In RDFs we propose to the user to create a subproperty of this link 

    for each type of role.-->
	<rdf:Property rdf:ID="P67B.is_referred_to_by">
		<rdfs:domain rdf:resource="#E1.CRM_Entity"/>
		<rdfs:range rdf:resource="#E28.Conceptual_Object"/>
	</rdf:Property>
	<!--E29 Design or Procedure-->
	<rdfs:Class rdf:ID="E29.Design_or_Procedure">
		<rdfs:comment>An established plan for execution of a series or group

     of technological actions, which result in a physical change of

     state in certain pieces of material and/or any physical object.



     Examples: All elements of the AAT "processes and techniques"

     facets., a plan for a building, conservation procedures,

     complex editing techniques, flint napping, etc..

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E73.Information_Object"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P68F.usually_employs">
		<rdfs:comment>This link is used to avoid repetition of materials for

     each object in case it is already mandatory for the

     technique.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E29.Design_or_Procedure"/>
		<rdfs:range rdf:resource="#E57.Material"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P68B.is_usually_employed_by">
		<rdfs:comment>This link is used to avoid repetition of materials for

     each object in case it is already mandatory for the

     technique.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E57.Material"/>
		<rdfs:range rdf:resource="#E29.Design_or_Procedure"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P69F.associated_with">
		<rdfs:comment>This link allows to model sequences and complex

     composite procedures. To be further specialized down.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E29.Design_or_Procedure"/>
		<rdfs:range rdf:resource="#E29.Design_or_Procedure"/>
	</rdf:Property>
	<!--E30 Right-->
	<rdfs:Class rdf:ID="E30.Right">
		<rdfs:comment>Rights are used in the sense of legal privileges such

     as the right of property, reproduction rights, etc.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E28.Conceptual_Object"/>
	</rdfs:Class>
	<!--E31 Document-->
	<rdfs:Class rdf:ID="E31.Document">
		<rdfs:comment>This entity comprises items which make propositions

     about reality, whether intentionally or by chance. The means

     may be text, graphics, images, sound, video. Examples: Books

     on history, maps, photos.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E73.Information_Object"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P70F.documents">
		<rdfs:comment> The specific interest is to capture cross-references

     to objects in collections.

     A document might also refer to an event, a type or a

     site.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E31.Document"/>
		<rdfs:range rdf:resource="#E1.CRM_Entity"/>
		<rdfs:subPropertyOf rdf:resource="#P67F.referrs_to"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P70B.is_documented_in">
		<rdfs:comment> The specific interest is to capture cross-references

     to objects in collections.

     A document might also refer to an event, a type or a

     site.

  </rdfs:comment>
		<rdfs:domain rdf:resource="#E1.CRM_Entity"/>
		<rdfs:range rdf:resource="#E31.Document"/>
		<rdfs:subPropertyOf rdf:resource="#P67B.is_referred_to_by"/>
	</rdf:Property>
	<!--E32 Authority Document-->
	<rdfs:Class rdf:ID="E32.Authority_Document">
		<rdfs:comment>This entity describes encyclopedia, thesauri,

     authority lists: all documents which define terminology or

     conceptual systems for consistent use.

     e.g. Webster's, Getty Art and Architecture Thesaurus, MDA

     Archaeological Objects Thesaurus,

     This Document, etc.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E31.Document"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P71F.contains">
		<rdfs:domain rdf:resource="#E32.Authority_Document"/>
		<rdfs:range rdf:resource="#E55.Type"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P71B.is_part_of">
		<rdfs:domain rdf:resource="#E55.Type"/>
		<rdfs:range rdf:resource="#E32.Authority_Document"/>
	</rdf:Property>
	<!--E33 Linguistic Object-->
	<rdfs:Class rdf:ID="E33.Linguistic_Object">
		<rdfs:comment>This entity comprises texts of all kind,

     be they written or recorded speech,

     in any physical language.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E73.Information_Object"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P72F.has_language">
		<rdfs:domain rdf:resource="#E33.Linguistic_Object"/>
		<rdfs:range rdf:resource="#E56.Language"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P72B.is_language_of">
		<rdfs:domain rdf:resource="#E56.Language"/>
		<rdfs:range rdf:resource="#E33.Linguistic_Object"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P73F.has_translation">
		<rdfs:domain rdf:resource="#E33.Linguistic_Object"/>
		<rdfs:range rdf:resource="#E33.Linguistic_Object"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P73B.is_translation_of">
		<rdfs:domain rdf:resource="#E33.Linguistic_Object"/>
		<rdfs:range rdf:resource="#E33.Linguistic_Object"/>
	</rdf:Property>
	<!--E34 Inscription-->
	<rdfs:Class rdf:ID="E34.Inscription">
		<rdfs:comment>This entity comprises texts attached to a physical

     object. The attributes of the entity could be extended to include

     alphabet used, rather than documenting these features in the note.

     NB The entity does not describe idiosyncratic characteristics of

     individual physical embodiments of an inscription but the

     underlying prototype, e.g. Duerer=B4s signature.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E33.Linguistic_Object"/>
		<rdfs:subClassOf rdf:resource="#E37.Mark"/>
	</rdfs:Class>
	<!--E35 Title-->
	<rdfs:Class rdf:ID="E35.Title">
		<rdfs:comment>This entity comprises the short pieces of texts that

     are used, by the creator or tradition, to characterize or identify

     a work, often alluding to its subject. The work may be linguistic,

     musical, iconographic or other.

     Examples: Giaconda, La Joconde, Mona Lisa, Die Dreigroschenoper,

     La Pie, La Marseillaise. 

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E33.Linguistic_Object"/>
		<rdfs:subClassOf rdf:resource="#E41.Appellation"/>
	</rdfs:Class>
	<!--E36 Visual Item-->
	<rdfs:Class rdf:ID="E36.Visual_Item">
		<rdfs:comment>Visual Items refers to the intellectual or conceptual

     aspect of recognizable marks and images. When we identify a trade

     mark, say the ICOM logo, we are generally prepared to say that

     the same logo is used on any number of publications. The size,

     orientation and colour may change, but something uniquely

     identifiable remains. The same can be said of images which are

     reproduced many times. What these examples highlight is that

     visual items are independent of their physical support. The visual

     items class provides a means of identifying and linking together

     objects which carry the same visual symbols, marks, images

     or whatever.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E73.Information_Object"/>
	</rdfs:Class>
	<!--E37 Mark-->
	<rdfs:Class rdf:ID="E37.Mark">
		<rdfs:comment>Martin Doerr: Symbols, signs, signatures or short texts

     applied to physical objects by arbitrary techniques in order to

     indicate the creator, owner, dedications, purpose, etc.

     Examples: Minoan double axe mark, =A9, STOP! .

    

     This entity specifically does not included marks such as

     scratches, which have no semantic significance. These case be

     documented as physical features.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E36.Visual_Item"/>
	</rdfs:Class>
	<!--E38 Image-->
	<rdfs:Class rdf:ID="E38.Image">
		<rdfs:comment>This entity refers to distributions of form and colour

     which may be found on surfaces such as photos, paintings, prints,

     and sculptures etc. or directly on electronic media. The degree

     to which variations in the distribution of form and colour are

     tolerated depends on a given purpose.

    

     The "depiction" links between objects and depicted subjects

     may be regarded as short cuts of an intermediate image node

     capturing the optical features of the depiction. Cf E25.



     Examples: The front side of all 20 Frs notes.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E36.Visual_Item"/>
	</rdfs:Class>
	<!--E39 Actor-->
	<rdfs:Class rdf:ID="E39.Actor">
		<rdfs:comment>People, either individuals or a groups of persons,

     or organisations, under the aspect of their role in activities.

     E.g. The ISO central committe, the Benaki Museum in Athens,

     Greece, the Bauhaus in Weimar, Germany, Monet, Me.

    

     An informal group, such as a school of artists, may acquire an

     identity and perform actions without ever becoming an officially

     established legal entity. Such cases should be documented as

     instances of Actors, using an appropriate

     sub type.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E77.Existence"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P74F.has_current_or_former_residence">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E53.Place"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P74B.is_current_or_former_residence_of">
		<rdfs:domain rdf:resource="#E53.Place"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P75F.possesses">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E30.Right"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P75B.is_possessed_by">
		<rdfs:domain rdf:resource="#E30.Right"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P76F.has_contact_points">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E51.Contact_Point"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P76B.provides_access_to">
		<rdfs:domain rdf:resource="#E51.Contact_Point"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
	</rdf:Property>
	<!--E40 Legal Body-->
	<rdfs:Class rdf:ID="E40.Legal_Body">
		<rdfs:comment>A legal body is any institution or group of people

     which can act collectively as an agent i.e. it can perform

     actions, own property, create or destroy and be held responsible

     for its actions. The term 'personne morale' is often used in

     French.

    

     Examples: MDA .Europe. Ltd., GreenPeace.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E74.Group"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P77F.consists_of">
		<rdfs:domain rdf:resource="#E40.Legal_Body"/>
		<rdfs:range rdf:resource="#E40.Legal_Body"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P77B.belongs_to">
		<rdfs:domain rdf:resource="#E40.Legal_Body"/>
		<rdfs:range rdf:resource="#E40.Legal_Body"/>
	</rdf:Property>
	<!--E41 Appellation-->
	<rdfs:Class rdf:ID="E41.Appellation">
		<rdfs:comment>This entity comprises all names in the proper sense.

     Codes or words, meaningless or meaningful, in the script of

     some group or encoding of an electronic system, used solely to

     identify a specific instance of some category within a certain

     context. These words do not identify the object by their meaning

     but by convention, tradition or agreement.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E77.Existence"/>
	</rdfs:Class>
	<!--E42 Object Identifier-->
	<rdfs:Class rdf:ID="E42.Object_Identifier">
		<rdfs:comment>Unique codes assigned to objects in order to identify

     them uniquely within the context of one or more organizations.

     Typically alphanumeric sequences.

    

     examples: MM.GE.195, 13.45.1976, etc.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E41.Appellation"/>
	</rdfs:Class>
	<!--E44 Place Appellation-->
	<rdfs:Class rdf:ID="E44.Place_Appellation">
		<rdfs:comment>A place appellation is any sort of identifier used to

     refer to a place. Place appellations may vary over time, and the

     same appellation may be used to refer to several places, either

     because of cultural shifts, or because things move around.

     These unstable aspects of place appellations are dealt with in

     the more general Appellation class. Place appellations can be

     extremely varied in form, postal addresses and spatial coordinates

     and parts of buildings can all be considered as place appellations.



     Examples: Vienna, Wien, Aquae Sulis Minerva, Bath, Cambridge,

               The Other Place. The City.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E41.Appellation"/>
	</rdfs:Class>
	<!--E45 Address-->
	<rdfs:Class rdf:ID="E45.Address">
		<rdfs:comment>An address is generally a postal address used for

     mailing. An address can be considered both as the name of a place

     and as a contact point for an actor. This dual aspect is reflected

     in the multiple inheritance.

    

     Example :       1-29-3 Otsuka, Bunkyo-ku,

                     Tokyo, 121, Japan.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E44.Place_Appellation"/>
		<rdfs:subClassOf rdf:resource="#E51.Contact_Point"/>
	</rdfs:Class>
	<!--E46 Section Definition-->
	<rdfs:Class rdf:ID="E46.Section_Definition">
		<rdfs:comment>section definition groups together names used to refer

     to parts of objects. The 'prow' of a boat, the 'frame' of the

     picture, the 'basement' of the building are all section

     definitions. The entity highlights the fact that parts of objects

     can be treated as locations. .cf. E53 Place. In answer to the

     question 'where is the signature?' one might reply 'on the lower

     left corner'.

    

     Example: The entrance lobby to MDA House, Matthew?s bedroom,

     the poop deck of H.M.S. Victory, the Venus de Milo?s left buttock,

     left inner side of the box.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E44.Place_Appellation"/>
	</rdfs:Class>
	<!--E47 Spatial Coordinates-->
	<rdfs:Class rdf:ID="E47.Spatial_Coordinates">
		<rdfs:comment>Coordinates are a specific form of place appellation,

     that is, a means of referring to a particular place.

     .cf E53 place.

     Coordinates are not restricted to longitude, latitude and altitude.



     Any regular system of reference that maps onto a physical object

     can be considered as coordinates.

     Examples: 6=B05?29N 45=B012?13W,

                        Black queen?s bishop 4.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E44.Place_Appellation"/>
	</rdfs:Class>
	<!--E48 Place Name-->
	<rdfs:Class rdf:ID="E48.Place_Name">
		<rdfs:comment>A place name is a particular and common form of

     place appellation. 'Greece', 'Athens', 'Geneva', are all

     place names. Place names may shift their meaning over time.

     Cf Place appellations.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E44.Place_Appellation"/>
	</rdfs:Class>
	<!--E49 Time Appellation-->
	<rdfs:Class rdf:ID="E49.Time_Appellation">
		<rdfs:comment>Time appellation groups all forms of names or codes,

     such as historical periods, and dates, which are used to refer

     to specific time frames. Time appellations may vary in their

     degree of precision, and they may be relative to other time

     frames, 'prehistoric' for example. These aspects of time

     appellations are dealt with in the more general 'appellations'

     class.



     In contrast to cultural periods, proper names are seldom given

     to particular Time-spans, hence it was decided to exclude a

     specific entity ?Time-spans name?. Time-spans are often referred

     to in association with cultural periods, and events

     e.g. ?the duration of Ming Dynasty?. cf. E52 Time span.



     Examples: Meiji, 1st half of the XX century, Quaternary,

     1215 Hegira. Last century.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E41.Appellation"/>
	</rdfs:Class>
	<!--E50 Date-->
	<rdfs:Class rdf:ID="E50.Date">
		<rdfs:comment>Dates are a specific form of time appellation.

     Dates may vary in their degree of precision.

     E.g. 1900, 4-4-1959, 19640604.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E49.Time_Appellation"/>
	</rdfs:Class>
	<!--E51 Contact Point-->
	<rdfs:Class rdf:ID="E51.Contact_Point">
		<rdfs:comment>This entity comprises identifiers used to communicate

     with Actors. Examples: E-mail addresses, telephone numbers, post

     office boxes, Fax numbers, etc. NB postal addresses can be

     considered both as place appellations and

     Contact Points.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E1.CRM_Entity"/>
	</rdfs:Class>
	<!--E52 Time Span-->
	<rdfs:Class rdf:ID="E52.Time-Span">
		<rdfs:comment>A determination of a range of dates or duration without

     any further connotations, to be used to confine periods, events,

     and any other phenomena valid for a certain time. A time

     appellation is a verbal form which refers to a time-span.

     The time-span itself is a temporal extent in the sense of Galilean

     physics. Different time-appellations may express the same

     time-span.



     Examples : from 12-17-1993 to 12-8-1996,

     14h30 - 16h22 4th July 1945, 9.30 am 1.1.1999 to 2.OO pm 1.1.1999,

     Duration of the Ming Dynasty.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E1.CRM_Entity"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P78F.is_identified_by">
		<rdfs:domain rdf:resource="#E52.Time-Span"/>
		<rdfs:range rdf:resource="#E49.Time_Appellation"/>
		<rdfs:subPropertyOf rdf:resource="#P1F.is_identified_by"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P78B.identifies">
		<rdfs:domain rdf:resource="#E49.Time_Appellation"/>
		<rdfs:range rdf:resource="#E52.Time-Span"/>
		<rdfs:subPropertyOf rdf:resource="#P1B.identifies"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P79F.begins_at_qualify">
		<rdfs:domain rdf:resource="#E52.Time-Span"/>
		<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P80F.ends_at_qualify">
		<rdfs:domain rdf:resource="#E52.Time-Span"/>
		<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P81F.at_least_covering">
		<rdfs:domain rdf:resource="#E52.Time-Span"/>
		<rdfs:range rdf:resource="#E61.Time_Primitive"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P82F.at_most_within">
		<rdfs:domain rdf:resource="#E52.Time-Span"/>
		<rdfs:range rdf:resource="#E61.Time_Primitive"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P83F.had_at_least_duration">
		<rdfs:domain rdf:resource="#E52.Time-Span"/>
		<rdfs:range rdf:resource="#E54.Dimension"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P84F.had_at_most_duration">
		<rdfs:domain rdf:resource="#E52.Time-Span"/>
		<rdfs:range rdf:resource="#E54.Dimension"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P85F.consists_of">
		<rdfs:domain rdf:resource="#E52.Time-Span"/>
		<rdfs:range rdf:resource="#E52.Time-Span"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P85B.forms_part_of">
		<rdfs:domain rdf:resource="#E52.Time-Span"/>
		<rdfs:range rdf:resource="#E52.Time-Span"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P86F.falls_within">
		<rdfs:domain rdf:resource="#E52.Time-Span"/>
		<rdfs:range rdf:resource="#E52.Time-Span"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P86B.contains">
		<rdfs:domain rdf:resource="#E52.Time-Span"/>
		<rdfs:range rdf:resource="#E52.Time-Span"/>
	</rdf:Property>
	<!--E53 Place-->
	<rdfs:Class rdf:ID="E53.Place">
		<rdfs:comment>This entity describes extents in space, in particular

     on the surface of the earth, in the pure sense of physics:

     independent from temporal phenomena and matter. Places are usually

     determined by reference to the position of immobile objects

     such as buildings, cities, mountains, and rivers. On a large

     time-scale however, these things are either not persistent or may

     actually move, with respect to each other. This motivates the

     search for a global or absolute system of reference.



     However, relative references are more relevant in the context of

     cultural documentation and records of relative places tend to be

     more precise. In particular, we are often interested in position

     in relation to large objects, such as ships, which move. Any

     object can serve as a reference for place determination;

     therefore the model foresees the notion of a "section" of a

     physical object as a place determination of equal validity.



     Matching between multiple reference systems is in principle

     possible for a given moment in time, but depends on the precision

     and completeness of the information available. However, the

     resolution of places to absolute coordinates is not, in =

general,

     necessary in cultural documentation systems, and absolute

     referencing may be dependent on the present state of

     global knowledge.



     Example: the place at which Nelson died is known with reference

     to a large mobile object - H.M.S Victory. A resolution of this

     place in terms of absolute coordinates requires knowledge about

     the position of the vessel and the precise time of his death,

     either of which may be revised. Hence, documenting only an

     absolute reference effectively removes the possibility of

     recalculating.

     It is more relevant to preserve the reasoning behind an assumption

     than the result.



     Hence a place can be determined by combining, one or more times,

     a frame of reference and a location with respect to this frame.

     These combinations are modelled by Place Appellation.

     .Instance of place are themselves nameless..



     Example: The place referred to by the Fish collected at three

     miles north of the confluence of the Arve and the Rhone,

     or N W. .GPS., Here.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E1.CRM_Entity"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P87F.is_identified_by">
		<rdfs:domain rdf:resource="#E53.Place"/>
		<rdfs:range rdf:resource="#E44.Place_Appellation"/>
		<rdfs:subPropertyOf rdf:resource="#P1F.is_identified_by"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P87B.identifies">
		<rdfs:domain rdf:resource="#E44.Place_Appellation"/>
		<rdfs:range rdf:resource="#E52.Time-Span"/>
		<rdfs:subPropertyOf rdf:resource="#P1B.identifies"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P88F.consists_of">
		<rdfs:domain rdf:resource="#E53.Place"/>
		<rdfs:range rdf:resource="#E53.Place"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P88B.forms_part_of">
		<rdfs:domain rdf:resource="#E53.Place"/>
		<rdfs:range rdf:resource="#E53.Place"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P89F.falls_within">
		<rdfs:domain rdf:resource="#E53.Place"/>
		<rdfs:range rdf:resource="#E53.Place"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P89B.contains">
		<rdfs:domain rdf:resource="#E53.Place"/>
		<rdfs:range rdf:resource="#E53.Place"/>
	</rdf:Property>
	<!--E54 Dimension-->
	<rdfs:Class rdf:ID="E54.Dimension">
		<rdfs:comment>This entity is an abstract class for properties that

     are measured by some calibrated means and result in numerical

     values.



     Examples: currency: =A326.00, length: 4 cm, diameter 26 mm,

     weight 150 lbs, density : 0.85 gm/cc, luminescence :

     56 ISO lumens, tin content: 0.46 %, taille au garot :

     5 hands, C14 date : 2460 years, etc.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E1.CRM_Entity"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P90F.value">
		<rdfs:domain rdf:resource="#E54.Dimension"/>
		<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P91F.unit">
		<rdfs:domain rdf:resource="#E54.Dimension"/>
		<rdfs:range rdf:resource="#E58.Measurement_Unit"/>
	</rdf:Property>
	<!--E55 Type-->
	<rdfs:Class rdf:ID="E55.Type">
		<rdfs:comment>This entity captures the names of all entities in the

     model and any refinements of these entities which do not require

     further analysis of their formal properties, but which represent

     typological distinctions important to a given user group. The

     semantic interpretation of these subtypes is based on the

     agreement of specific groups. Instances of the Type entity have

     to be formally organized in thesauri, with scope notes,

     illustrations, etc. to clarify their meaning.

     In general, it is expected that different domains and cultural

     groups develop different thesauri in parallel. Consistent

     reasoning on the expansion of sub terms used in a thesaurus is

     possible insofar as it conforms to both the entities and the

     hierarchies of this Model.



     Examples: Weight, length, depth are types of measurement.

     Portrait, sketch, animation could be types of depiction. Oral,

     written could be types of language. Excellent, good, poor could

     be types of condition state.

  </rdfs:comment>
	</rdfs:Class>
	<!--E56 Language-->
	<rdfs:Class rdf:ID="E56.Language">
		<rdfs:comment>This entity comprises the names identifying natural

     languages.Internationally used codes are recommended .ISO.....

     This type does not correspond to another explicit entity in the

     Model.

     Example:   ISO language codes.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E55.Type"/>
	</rdfs:Class>
	<!--E57 Material-->
	<rdfs:Class rdf:ID="E57.Material">
		<rdfs:comment>This entity comprises the names used to identify

     materials. Internationally used codes and terminology are

     recommended. This type does not correspond to any other explicit

     entity in the Model, because materials do not have well-defined

     instances, especially after they are used. Discrete pieces of

     raw-materials kept in museums, such as bricks, sheets of fabric,

     pieces of metal, should be modelled separately just as

     other objects. Discrete used or processed pieces, such as the

     stones from Nefer Titi's temple, should be modelled

     as parts.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E55.Type"/>
	</rdfs:Class>
	<!--E58 Measurement Unit-->
	<rdfs:Class rdf:ID="E58.Measurement_Unit">
		<rdfs:comment>This entity provides the authority list for all types

     of measurement units: feet, inches, centimeters, litres, lumens,

     etc.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E55.Type"/>
	</rdfs:Class>
	<!--E59 Primitive Value-->
	<rdfs:Class rdf:ID="E59.Primitive_Value">
		<rdfs:comment>This entity is a container for primitive values used

     as documentation elements which are not further analysed. As such

     they are not considered as elements within our universe of

     discourse. No specific implementation

     recommendations are made. 

  </rdfs:comment>
	</rdfs:Class>
	<!--E60 Number, E62 String are mapped to rdf:literal-->
	<!--E61 Time Primitive-->
	<rdfs:Class rdf:ID="E61.Time_Primitive">
		<rdfs:comment>This entity is a primitive value that should implement

     appropriate validation and interval logic for date ranges and

     precision relevant to cultural documentation. It is not further

     analysed in this model.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E59.Primitive_Value"/>
	</rdfs:Class>
	<rdfs:Class rdf:ID="E63.Beginning_of_Existence">
		<rdfs:comment>Entity for temporal reasoning about things beginning to exist Β– 

     Intellectual products, physical items, groups of people, living beings ,   periods ?Β–  

     A hook for termini postquem and antequem. It may turn out useful to define more 

     specializations of this entity for Natural History.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E5.Event"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P92F.brought_into_existence">
		<rdfs:domain rdf:resource="#E63.Beginning_of_Existence"/>
		<rdfs:range rdf:resource="#E77.Existence"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P92B.was_brought_into_existence_by">
		<rdfs:domain rdf:resource="#E77.Existence"/>
		<rdfs:range rdf:resource="#E63.Beginning_of_Existence"/>
	</rdf:Property>
	<rdfs:Class rdf:ID="E64.End_of_Existence">
		<rdfs:comment>Entity for temporal reasoning about things  stopping to exist Β– 

     physical items, groups of people, living beings Β–

     A hook for termini postquem and antequem.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E5.Event"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P93F.took_out_of_existence">
		<rdfs:domain rdf:resource="#E64.End_of_Existence"/>
		<rdfs:range rdf:resource="#E77.Existence"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P93B.was_taken_out_of_existence_by">
		<rdfs:domain rdf:resource="#E77.Existence"/>
		<rdfs:range rdf:resource="#E64.End_of_Existence"/>
	</rdf:Property>
	<rdfs:Class rdf:ID="E65.Conceptual_Creation">
		<rdfs:comment>The creation of an inmaterial product - Text,

     music, image, movie, Law, etc.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E63.Beginning_of_Existence"/>
		<rdfs:subClassOf rdf:resource="#E7.Activity"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P94F.has_created">
		<rdfs:domain rdf:resource="#E65.Conceptual_Creation"/>
		<rdfs:range rdf:resource="#E28.Conceptual_Object"/>
		<rdfs:subPropertyOf rdf:resource="#P12F.ocurred_in_the_presence_of"/>
		<rdfs:subPropertyOf rdf:resource="#P92F.brought_into_existence"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P94B.was_created_by">
		<rdfs:domain rdf:resource="#E28.Conceptual_Object"/>
		<rdfs:range rdf:resource="#E65.Conceptual_Creation"/>
		<rdfs:subPropertyOf rdf:resource="#P12B.was_present_at"/>
		<rdfs:subPropertyOf rdf:resource="#P92B.was_brought_into_existence_by"/>
	</rdf:Property>
	<rdfs:Class rdf:ID="E66.Formation">
		<rdfs:comment>The formation or foundation of a formal or informal

     group of people.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E63.Beginning_of_Existence"/>
		<rdfs:subClassOf rdf:resource="#E7.Activity"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P95F.has_formed">
		<rdfs:domain rdf:resource="#E66.Formation"/>
		<rdfs:range rdf:resource="#E74.Group"/>
		<rdfs:subPropertyOf rdf:resource="#P11F.had_participants"/>
		<rdfs:subPropertyOf rdf:resource="#P92F.brought_into_existence"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P95B.was_formed_by">
		<rdfs:domain rdf:resource="#E74.Group"/>
		<rdfs:range rdf:resource="#E66.Formation"/>
		<rdfs:subPropertyOf rdf:resource="#P11B.participated_in"/>
		<rdfs:subPropertyOf rdf:resource="#P92B.was_brought_into_existence_by"/>
	</rdf:Property>
	<rdfs:Class rdf:ID="E67.Birth">
		<rdfs:comment>The birth of a human being.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E63.Beginning_of_Existence"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P96F.by_mother">
		<rdfs:domain rdf:resource="#E67.Birth"/>
		<rdfs:range rdf:resource="#E21.Person"/>
		<rdfs:subPropertyOf rdf:resource="#P11F.had_participants"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P96B.gave_birth">
		<rdfs:domain rdf:resource="#E21.Person"/>
		<rdfs:range rdf:resource="#E67.Birth"/>
		<rdfs:subPropertyOf rdf:resource="#P11B.participated_in"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P97F.from_father">
		<rdfs:domain rdf:resource="#E67.Birth"/>
		<rdfs:range rdf:resource="#E21.Person"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P97B.was_father_for">
		<rdfs:domain rdf:resource="#E21.Person"/>
		<rdfs:range rdf:resource="#E67.Birth"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P98F.brought_into_life">
		<rdfs:domain rdf:resource="#E67.Birth"/>
		<rdfs:range rdf:resource="#E21.Person"/>
		<rdfs:subPropertyOf rdf:resource="#P11F.had_participants"/>
		<rdfs:subPropertyOf rdf:resource="#P92F.brought_into_existence"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P98B.was_born">
		<rdfs:domain rdf:resource="#E21.Person"/>
		<rdfs:range rdf:resource="#E67.Birth"/>
		<rdfs:subPropertyOf rdf:resource="#P11B.participated_in"/>
		<rdfs:subPropertyOf rdf:resource="#P92B.was_brought_into_existence_by"/>
	</rdf:Property>
	<rdfs:Class rdf:ID="E68.Dissolution">
		<rdfs:comment>The formal or informal end of a group of people. If it was

     a deliberate act, the instance should also be instantiated as an activity.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E64.End_of_Existence"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P99F.dissolved">
		<rdfs:domain rdf:resource="#E68.Dissolution"/>
		<rdfs:range rdf:resource="#E74.Group"/>
		<rdfs:subPropertyOf rdf:resource="#P11F.had_participants"/>
		<rdfs:subPropertyOf rdf:resource="#P93F.took_out_of_existence"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P99B.was_dissolved_by">
		<rdfs:domain rdf:resource="#E74.Group"/>
		<rdfs:range rdf:resource="#E68.Dissolution"/>
		<rdfs:subPropertyOf rdf:resource="#P11B.participated_in"/>
		<rdfs:subPropertyOf rdf:resource="#P93B.was_taken_out_of_existence_by"/>
	</rdf:Property>
	<rdfs:Class rdf:ID="E69.Death">
		<rdfs:comment>The death of a human being. If the person was killed,

     the instance should also be instantiated as an activity.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E64.End_of_Existence"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P100F.was_death_of">
		<rdfs:domain rdf:resource="#E69.Death"/>
		<rdfs:range rdf:resource="#E21.Person"/>
		<rdfs:subPropertyOf rdf:resource="#P11F.had_participants"/>
		<rdfs:subPropertyOf rdf:resource="#P93F.took_out_of_existence"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P100B.died_in">
		<rdfs:domain rdf:resource="#E21.Person"/>
		<rdfs:range rdf:resource="#E69.Death"/>
		<rdfs:subPropertyOf rdf:resource="#P11B.participated_in"/>
		<rdfs:subPropertyOf rdf:resource="#P93B.was_taken_out_of_existence_by"/>
	</rdf:Property>
	<rdfs:Class rdf:ID="E70.Stuff">
		<rdfs:comment>An identifiable, discrete, persistent item which constitutes a unit for 

     documentation, be it an intellectual product or a physical thing. Such items

     are characterized by a relative stability, i.e. either a solid physical form, an electronic

     encoding, a reproducible pattern, a logical concept or structure. It introduces the concept 

     of being used.

     Excluded are liquids flowing, gases moving around etc. A packaged liquid however fits 

     this entity.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E77.Existence"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P101F.had_as_general_use">
		<rdfs:domain rdf:resource="#E70.Stuff"/>
		<rdfs:range rdf:resource="#E55.Type"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P101B.was_use_of">
		<rdfs:domain rdf:resource="#E55.Type"/>
		<rdfs:range rdf:resource="#E70.Stuff"/>
	</rdf:Property>
	<!--E71 Man-Made Stuff-->
	<rdfs:Class rdf:ID="E71.Man-Made_Stuff">
		<rdfs:comment>An identifiable,discrete, persistent, item deliberately produced,

     invented or created by humans which constitutes a unit for 
   
     documentation, be an intellectual product, idea or a physical thing.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E70.Stuff"/>
	</rdfs:Class>
	<!--COMMENT: In the CRM this link has a link:.has type: Type.

    In RDFs we propose to the user to create a subproperty of this 

    link for each type of role.-->
	<rdf:Property rdf:ID="P102F.has_title">
		<rdfs:domain rdf:resource="#E71.Man-Made_Stuff"/>
		<rdfs:range rdf:resource="#E35.Title"/>
		<rdfs:subPropertyOf rdf:resource="#P1F.is_identified_by"/>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has a link:.has type: Type.

    In RDFs we propose to the user to create a subproperty of this 

    link for each type of role.-->
	<rdf:Property rdf:ID="P102B.is_title_of">
		<rdfs:domain rdf:resource="#E35.Title"/>
		<rdfs:range rdf:resource="#E71.Man-Made_Stuff"/>
		<rdfs:subPropertyOf rdf:resource="#P1B.identifies"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P103F.was_intended_for">
		<rdfs:domain rdf:resource="#E71.Man-Made_Stuff"/>
		<rdfs:range rdf:resource="#E55.Type"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P103B.was_intention_of">
		<rdfs:domain rdf:resource="#E55.Type"/>
		<rdfs:range rdf:resource="#E71.Man-Made_Stuff"/>
	</rdf:Property>
	<rdfs:Class rdf:ID="E72.Legal_Object">
		<rdfs:comment>An identifiable item which can be owned or people can have a right

     on. It is not restricted to Stuff. May also be Legal Bodies should be
     
     included.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E1.CRM_Entity"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P104F.is_subject_to">
		<rdfs:domain rdf:resource="#E72.Legal_Object"/>
		<rdfs:range rdf:resource="#E30.Right"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P104B.applies_to">
		<rdfs:domain rdf:resource="#E30.Right"/>
		<rdfs:range rdf:resource="#E72.Legal_Object"/>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has two links:

    .has type: Type 

    	In RDFs we propose to the user to create a subproperty of this 

    	link for each type of role. 

    and

    .has note: String.-->
	<rdf:Property rdf:ID="P105F.right_held_by">
		<rdfs:domain rdf:resource="#E72.Legal_Object"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
	</rdf:Property>
	<!--COMMENT: In the CRM this link has two links:

    .has type: Type. 

	In RDFs we propose to the user to create a subproperty of this 

    	link for each type of role. 

    and

    .has note: String.-->
	<rdf:Property rdf:ID="P105B.owns_rights_to">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E72.Legal_Object"/>
	</rdf:Property>
	<rdfs:Class rdf:ID="E73.Information_Object">
		<rdfs:comment>An identifiable inmaterial item which constitutes a unit for 

     documentation and has an objectively recognizable structure.

     Examples are data sets, images, texts, procedure prescriptions. It does

     not include types, ideas, etc.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E28.Conceptual_Object"/>
		<rdfs:subClassOf rdf:resource="#E72.Legal_Object"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P106F.is_composed_of">
		<rdfs:domain rdf:resource="#E73.Information_Object"/>
		<rdfs:range rdf:resource="#E73.Information_Object"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P106B.forms_part_of">
		<rdfs:domain rdf:resource="#E73.Information_Object"/>
		<rdfs:range rdf:resource="#E73.Information_Object"/>
	</rdf:Property>
	<rdfs:Class rdf:ID="E74.Group">
		<rdfs:comment>A group is any gathering of people that acts collectively or in a  

     similar way due to any kind of social bounds or contact. 

     Nationality can be handled as a link to a group of appropriate type. 

     Note the distinction between citizenship and ethnic group and other subtleties 
 
     not easily expressible by nationality adjectives. 

     Examples: A group of people painting together at some happening,

     A tribe of indigenous people, an artist workshop, a museum, "Those at the Bastille", 

     a nation, a government, a company.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E39.Actor"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="P107F.had_member">
		<rdfs:domain rdf:resource="#E74.Group"/>
		<rdfs:range rdf:resource="#E39.Actor"/>
	</rdf:Property>
	<rdf:Property rdf:ID="P107B.was_member_of">
		<rdfs:domain rdf:resource="#E39.Actor"/>
		<rdfs:range rdf:resource="#E74.Group"/>
	</rdf:Property>
	<rdfs:Class rdf:ID="E75.Conceptual_Object_Appellation">
		<rdfs:comment>Specific Identifiers of an intellectual product or standarized

     pattern.

     Examples: ISBN 3-7913-1418-1, ISO2788-1986(E)

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E41.Appellation"/>
	</rdfs:Class>
	<rdfs:Class rdf:ID="E76.Gender">
		<rdfs:comment/>
		<rdfs:subClassOf rdf:resource="#E55.Type"/>
	</rdfs:Class>
	<rdfs:Class rdf:ID="E77.Existence">
		<rdfs:comment>This is an abstract entity, which comprises the kinds of things that have the potenctial to exist

     for a relevant time-span preserving their identity. It comprises physical items and intellectual

     products, groups of people, living beings, etc. Types are included in yheir nature as intellectual

     product, in particular in natural history, where types are based on the findings of a prototypical 

     specimen. Appellations are included in their nature as creations of the people using them.

     Examples: ISBN 3-00-007556-9, me, Arethusa ophioglossoides, Shakespeare's Hamlet,

     Aphrodite of Milos.

  </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#E1.CRM_Entity"/>
	</rdfs:Class>
</rdf:RDF>
-------------- next part --------------
<?xml version="1.0" encoding="ISO-8859-7"?>
<!-- edited with XML Spy v3.5 NT (http://www.xmlspy.com) by sis ICS-FORTH (ISL-ICS) -->
<rdf:RDF xml:lang="en" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:crm="file:C:\tmp_local_users\gaspar\CIDOC.rdf#">
	<!--Description of Epitaphios GE34604-->
	<crm:E23.Iconographic_Object rdf:about="Epitaphios_GE34604">
		<crm:P47F.is_identified_by>
			<crm:E42.Object_Identifier rdf:about="TA_959a"/>
		</crm:P47F.is_identified_by>
		<crm:P47F.is_identified_by>
			<crm:E42.Object_Identifier rdf:about="GE_34604"/>
		</crm:P47F.is_identified_by>
		<crm:P48F.preferred_identifier_is rdf:resource="GE_34604"/>
		<crm:P2F.has_type>
			<crm:E55.Type rdf:about="ecclesiastical_embroidery"/>
		</crm:P2F.has_type>
		<crm:P2F.has_type>
			<crm:E55.Type rdf:about="liturgical_cloth"/>
		</crm:P2F.has_type>
		<crm:P52F.has_current_owner>
			<crm:E40.Legal_Body rdf:about="Museum Benaki">
				<crm:P2F.has_type>
					<crm:E55.Type rdf:about="private_museum"/>
				</crm:P2F.has_type>
				<crm:P76F.has_contact_points>
					<crm:E51.Contact_Point rdf:about="Ifigenia_Dionissiadu_ifi at benaki.gr"/>
				</crm:P76F.has_contact_points>
				<crm:P76F.has_contact_points>
					<crm:E45.Address rdf:about="Koumbari_Street_1_Athens"/>
				</crm:P76F.has_contact_points>
			</crm:E40.Legal_Body>
		</crm:P52F.has_current_owner>
		<crm:P51F.has_former_or_current_owner>
			<crm:E21.Person rdf:about="Georgios, son of Kyriazes">
				<crm:P3F.has_note>He was pilgrim of the Holy Land</crm:P3F.has_note>
			</crm:E21.Person>
		</crm:P51F.has_former_or_current_owner>
		<crm:P51F.has_former_or_current_owner>
			<crm:E39.Actor rdf:about="Metropolitan_Church_of_the_Greek_Community_of_Ankara">
				<crm:P2F.has_type>
					<crm:E55.Type rdf:about="ecclesiastical_institution"/>
				</crm:P2F.has_type>
			</crm:E39.Actor>
		</crm:P51F.has_former_or_current_owner>
		<crm:P51F.has_former_or_current_owner rdf:resource="Museum Benaki"/>
		<crm:P50F.has_current_keeper rdf:resource="Museum Benaki"/>
		<crm:P49F.has_former_or_current_keeper rdf:resource="Metropolitan_Church_of_the_Greek_Community_of_Ankara"/>
		<crm:P49F.has_former_or_current_keeper rdf:resource="Museum Benaki"/>
		<crm:P30B.custody_changed_by>
			<crm:E10.Transfer_of_Custody rdf:about="Transfer of Epitaphios GE34604">
				<rdf:type rdf:resource="file:C:\tmp_local_users\gaspar\CIDOC.rdf#E8.Acquisition"/>
				<crm:P28F.custody_surrendered_by rdf:resource="Metropolitan_Church_of_the_Greek_Community_of_Ankara"/>
				<crm:P23F.transferred_title_from rdf:resource="Metropolitan_Church_of_the_Greek_Community_of_Ankara"/>
				<crm:P29F.custody_received_by rdf:resource="Museum Benaki"/>
				<crm:P22F.transferred_title_to>
					<crm:E40.Legal_Body rdf:about="Exchangable Fund of Refugees">
						<crm:P2F.has_type>
							<crm:E55.Type rdf:about="national foundation"/>
						</crm:P2F.has_type>
					</crm:E40.Legal_Body>
				</crm:P22F.transferred_title_to>
				<crm:P14F.carried_out_by rdf:resource="Museum Benaki"/>
				<crm:P4F.has_time-span>
					<crm:E52.Time-Span rdf:about="vv">
						<crm:P81F.at_least_covering>
							<crm:E61.Time_Primitive rdf:about="1923"/>
						</crm:P81F.at_least_covering>
						<crm:P82F.at_most_within>
							<crm:E61.Time_Primitive rdf:about="1928"/>
						</crm:P82F.at_most_within>
					</crm:E52.Time-Span>
				</crm:P4F.has_time-span>
				<crm:P7F.took_place_at>
					<crm:E53.Place rdf:about="Greece">
						<crm:P2F.has_type>
							<crm:E55.Type rdf:about="nation"/>
						</crm:P2F.has_type>
						<crm:P2F.has_type>
							<crm:E55.Type rdf:about="republic"/>
						</crm:P2F.has_type>
						<crm:P89F.falls_within>
							<crm:E53.Place rdf:about="Europe">
								<crm:P2F.has_type>
									<crm:E55.Type rdf:about="continent"/>
								</crm:P2F.has_type>
							</crm:E53.Place>
						</crm:P89F.falls_within>
					</crm:E53.Place>
				</crm:P7F.took_place_at>
			</crm:E10.Transfer_of_Custody>
		</crm:P30B.custody_changed_by>
		<crm:P55F.has_current_location>
			<crm:E53.Place rdf:about="drawer8/case_27/room_6/floor-1/new_wing">
				<crm:P2F.has_type>
					<crm:E55.Type rdf:about="drawer"/>
				</crm:P2F.has_type>
				<crm:P89F.falls_within>
					<crm:E53.Place rdf:about="Museum_Benaki_Main_Building">
						<crm:P2F.has_type>
							<crm:E55.Type rdf:about="meseum building"/>
						</crm:P2F.has_type>
						<crm:P87F.is_identified_by rdf:resource="Koumbari_Street_1_Athens"/>
						<crm:P89F.falls_within>
							<crm:E53.Place rdf:about="Athens">
								<crm:P2F.has_type>
									<crm:E55.Type rdf:about="city"/>
								</crm:P2F.has_type>
								<crm:P2F.has_type>
									<crm:E55.Type rdf:about="national capital"/>
								</crm:P2F.has_type>
								<crm:P89F.falls_within rdf:resource="Greece"/>
							</crm:E53.Place>
						</crm:P89F.falls_within>
					</crm:E53.Place>
				</crm:P89F.falls_within>
			</crm:E53.Place>
		</crm:P55F.has_current_location>
		<crm:P54F.has_current_permanent_location rdf:resource="drawer8/case_27/room_6/floor-1/new_wing"/>
		<crm:P53F.has_former_or_current_location rdf:resource="drawer8/case_27/room_6/floor-1/new_wing"/>
		<crm:P53F.has_former_or_current_location>
			<crm:E53.Place rdf:about="Ankara">
				<crm:P2F.has_type rdf:resource="city"/>
				<crm:P2F.has_type rdf:resource="national capital"/>
				<crm:P89F.falls_within>
					<crm:E53.Place rdf:about="Asia_Minor">
						<crm:P2F.has_type>
							<crm:E55.Type rdf:about="region"/>
						</crm:P2F.has_type>
						<crm:P89F.falls_within>
							<crm:E53.Place rdf:about="Asia">
								<crm:P2F.has_type rdf:resource="continent"/>
							</crm:E53.Place>
						</crm:P89F.falls_within>
					</crm:E53.Place>
				</crm:P89F.falls_within>
				<crm:P89F.falls_within>
					<crm:E53.Place rdf:about="Turkey">
						<crm:P2F.has_type rdf:resource="nation"/>
						<crm:P2F.has_type rdf:resource="republic"/>
						<crm:P88F.consists_of rdf:resource="Asia_Minor"/>
						<crm:P88F.consists_of>
							<crm:E53.Place rdf:about="Eathern Thrace">
								<crm:P2F.has_type rdf:resource="region"/>
								<crm:P89F.falls_within rdf:resource="Europe"/>
							</crm:E53.Place>
						</crm:P88F.consists_of>
					</crm:E53.Place>
				</crm:P89F.falls_within>
			</crm:E53.Place>
		</crm:P53F.has_former_or_current_location>
		<crm:P108B.was_produced_by>
			<crm:E12.Production rdf:about="Creation of epitaphios GE34604">
				<crm:P2F.has_type>
					<crm:E55.Type rdf:about="handwork"/>
				</crm:P2F.has_type>
				<crm:P3F.has_note>information is derived from the inscription</crm:P3F.has_note>
				<crm:P4F.has_time-span>
					<crm:E52.Time-Span>
						<crm:P81F.at_least_covering>
							<crm:E61.Time_Primitive rdf:about="1682"/>
						</crm:P81F.at_least_covering>
						<crm:P82F.at_most_within>
							<crm:E61.Time_Primitive rdf:about="1682"/>
						</crm:P82F.at_most_within>
					</crm:E52.Time-Span>
				</crm:P4F.has_time-span>
				<crm:P7F.took_place_at>
					<crm:E53.Place rdf:about="Istanbul">
						<crm:P87F.is_identified_by>
							<crm:E48.Place_Name rdf:about="xxxxxxx"/>
						</crm:P87F.is_identified_by>
						<crm:P2F.has_type rdf:resource="city"/>
						<crm:P89F.falls_within rdf:resource="Turkey"/>
						<crm:P89F.falls_within rdf:resource="Eathern Thrace"/>
					</crm:E53.Place>
				</crm:P7F.took_place_at>
				<crm:P14F.carried_out_by>
					<crm:E21.Person rdf:about="Despoineta">
						<crm:P2F.has_type>
							<crm:E55.Type rdf:about="needle woman"/>
						</crm:P2F.has_type>
					</crm:E21.Person>
				</crm:P14F.carried_out_by>
				<crm:P32F.used_general_technique>
					<crm:E55.Type rdf:about="gold and silver embroidering"/>
				</crm:P32F.used_general_technique>
				<crm:P20F.had_specific_purpose>
					<crm:E7.Activity rdf:about="Order by Georgios, son of Kyriazes">
						<crm:P2F.has_type>
							<crm:E55.Type rdf:about="commercial order"/>
						</crm:P2F.has_type>
						<crm:P14F.carried_out_by rdf:resource="Georgios, son of Kyriazes"/>
						<crm:P20F.had_specific_purpose>
							<crm:E8.Acquisition rdf:about="Donation by Georgios, son of Kyriazes">
								<crm:P2F.has_type>
									<crm:E55.Type rdf:about="gold and silver embroidering"/>
								</crm:P2F.has_type>
								<crm:P24F.transferred_title_of rdf:resource="Epitaphios_GE34604"/>
								<crm:P24F.transferred_title_of>
									<crm:E19.Physical_Object rdf:about="Cross GE34059">
										<crm:P2F.has_type>
											<crm:E55.Type rdf:about="processory cross"/>
										</crm:P2F.has_type>
										<crm:P52F.has_current_owner rdf:resource="Museum Benaki"/>
									</crm:E19.Physical_Object>
								</crm:P24F.transferred_title_of>
								<crm:P23F.transferred_title_from rdf:resource="Georgios, son of Kyriazes"/>
								<crm:P22F.transferred_title_to rdf:resource="Metropolitan_Church_of_the_Greek_Community_of_Ankara"/>
								<crm:P7F.took_place_at rdf:resource="Ankara"/>
							</crm:E8.Acquisition>
						</crm:P20F.had_specific_purpose>
					</crm:E7.Activity>
				</crm:P20F.had_specific_purpose>
				<crm:P10F.falls_within>
					<crm:E7.Activity rdf:about="Despoineta's professional period">
						<crm:P2F.has_type>
							<crm:E55.Type rdf:about="processory cross"/>
						</crm:P2F.has_type>
						<crm:P14F.carried_out_by rdf:resource="Despoineta"/>
						<crm:P4F.has_time-span>
							<crm:E52.Time-Span>
								<crm:P81F.at_least_covering>
									<crm:E61.Time_Primitive rdf:about="1682"/>
								</crm:P81F.at_least_covering>
								<crm:P82F.at_most_within>
									<crm:E61.Time_Primitive rdf:about="1682"/>
								</crm:P82F.at_most_within>
							</crm:E52.Time-Span>
						</crm:P4F.has_time-span>
						<crm:P7F.took_place_at rdf:resource="Istanbul"/>
					</crm:E7.Activity>
				</crm:P10F.falls_within>
			</crm:E12.Production>
		</crm:P108B.was_produced_by>
		<crm:P64F.depicts_concept>
			<crm:E55.Type rdf:about="The Lament"/>
		</crm:P64F.depicts_concept>
		<crm:P65F.shows_visual_item>
			<crm:E34.Inscription rdf:about="Inscription of epitaphios GE34604">
				<crm:P72F.has_language>
					<crm:E56.Language rdf:about="medieval Greek"/>
				</crm:P72F.has_language>
				<crm:P3F.has_note>Inscription text:
Center: «ΔΙΑ ΧΕΙΡΟΣ ΑΧΡΕΙΑΣ ΔΕΣΠΟΙΝΕΤΑΣ, ΗΜ(ων) ΔΕΣΠΟΙΝΗΣ ΔΟΥΛΗΣ, ΦΕΙΛΟΠΟΝΕΙΤΑΙ ΤΟ ΠΑΡΟΝ, ΕΝ ΚΩΝΣΤΑΝΤΙΝΟΥΠΟΛΕΙ»
On the lower side: «ΤΗΝ ΠΑΝΣΕΤΠΤΟΝ ΜΩΡΦΗΝ ΤΗΣ ΣΗΣ ΕΠΙΤΥΜΒΙΟΥ ΧΑΡΑΚΤΗΡΙΣΑΣ Π[ΡΟΣΕ]ΘΗΚΕΝ ΤΗΔΕ Μ(ητρ)ΟΠΟΛΕΙ ΑΓΓ[ΥΡΑ]Σ ΤΗΣ ΠΡ[_]ΣΤ [_] ΚΥΡΙΑΖΗ ΔΕ ΓΟΝΟΣ [ΠΡ]ΟΣΚΥΝΗΤΗΣ ΚΑΙ ΔΟΥΛΟΣ ΣΟΥ, ΘΕΙΕ Θ(εο)Υ ΛΟΓΕ ΓΕ[ΩΡ]Γ[ΙΟΣ]»
On the right: « ΕΝ ΕΤΕΙ Σ(ωτη)ΡΙΩ ΑΧΠΒ..: ΟΤΕ ΕΝ ΤΩ ΤΑΦΩ ΤΩ ΚΕΝΩ, ΥΠΕΡ ΤΟΥ ΠΑΝΤΟΣ ΚΑΤΕΤΕΘΗΣ Ο ΠΟΙΗΤΗΣ | ΤΟΥ ΠΑΝΤΟΣ ΑΔΗΣ Ο ΠΑΓΓΕΛΑΣΤΟΣ ΕΙΔΟΝ ΣΕ ΕΦΡΙΞΕΝ ΟΙ ΜΟΧΛΟΙ ΣΥΝΕΤΡΙΒΗΣΑΝ ΕΘΛΑΣΘΗΣΑΝ ΠΥΛΑΙ ΜΝΗΜΑΤΑ ΕΙΝΗΧΘΗΣΗΣΑΝ, Σ(ωτ)ΕΡ ΑΝΕΒΟΑ ΣΟΙ ΔΟΞΑ, ΤΗ ΟΙΚΟΝΟΜΙΑ ΣΟΥ ΦΙΛ|ΑΝ(θρωπ)Ε.»
On the upper inner zone: Η ΖΩΗ ΕΝ ΤΑΦΩ ΚΑΤΕΤΕΘΗΣ Χ(ριστ)Ε, ΚΑΙ ΑΓΓΕΛΩΝ ΣΤΡΑΤΙΑΙ ΕΞΕΠΛΗΤΤΩΝΤΟ, ΣΥΓΚΑΤΑΒΑΣΙΝ ΔΟΞΑΖΟΥΣΑΙ ΤΗΝ ΣΗΝ.
On the lower inner zone: + ΑΙ ΓΕΝΝΕΑΙ ΠΑΣΣΑΙ ΥΜΝΟΝ ΤΗ ΤΑΦΗ ΣΟΥ ΠΡ[ΟΣΦΕΡΟ]ΜΕΝ ΧΡΙ[ΙΣΤΕ ΜΟΥ .Τ]ΡΙΑΣ ΘΕΕ ΜΟ[Υ ΠΑΤΗΡ ΥΙΟ]Σ ΚΑΙ ΠΝ(ευμ)Α ΕΛΕΗΣΟΝ ΤΟΝ ΚΟΣΜΟΝ.
On the left inner zone: Ο ΕΥΣΧΗΜΟΝ ΙΩΣΗΦ ΑΠΟ ΤΟΥ ΞΥΛΟΥ ΚΑΘΕΛΩΝ ΤΟ ΑΧΡΑΝΤΟΝ ΣΟΥ ΣΩΜΑ ΣΙΝΔΟΝΙ ΚΑΘΑΡΑ ΕΙΛΙΣΑΣ. Εις  την δεξιά: + ΑΞΙΟΝ ΕΣΤΙ ΜΕΓΑΛΛΥΝΕΙΝ ΣΕ ΤΟΝ ΖΩΟΔΟΤΗΝ ΤΟΝ ΕΝ ΤΩ ΣΤ(αυ)ΡΩ ΤΑΣ ΧΕΙΡΑΣ ΕΚΤΕΙΝΑΝΤΑ Κ(αι) ΣΥΝΤΡΙ</crm:P3F.has_note>
			</crm:E34.Inscription>
		</crm:P65F.shows_visual_item>
		<crm:P101F.had_as_general_use>
			<crm:E55.Type rdf:about="epitaphios function"/>
		</crm:P101F.had_as_general_use>
		<crm:P103F.was_intended_for rdf:resource="epitaphios function"/>
		<crm:P43F.has_dimension>
			<crm:E54.Dimension rdf:about="length 1.50 m"/>
		</crm:P43F.has_dimension>
		<crm:P43F.has_dimension>
			<crm:E54.Dimension rdf:about="width 1.12 m"/>
		</crm:P43F.has_dimension>
		<crm:P57F.has_number_of_parts>1 piece</crm:P57F.has_number_of_parts>
		<crm:P45F.consists_of>
			<crm:E57.Material rdf:about="silver thread"/>
		</crm:P45F.consists_of>
		<crm:P45F.consists_of>
			<crm:E57.Material rdf:about="gold thread"/>
		</crm:P45F.consists_of>
		<crm:P45F.consists_of>
			<crm:E57.Material rdf:about="silk thread"/>
		</crm:P45F.consists_of>
	</crm:E23.Iconographic_Object>
</rdf:RDF>


More information about the Crm-sig mailing list