Just to add re the act of 'finding' objects, this is how the CRM-EH model which focusses on archaeological fieldwork works:
An Object is made through some (potentially unknown) Production event, eventually ends up in some archaeological deposit through some (potentially unknown) Deposition event and is subsequently excavated and recorded in context by an archaeologist before being accessioned (ie moved, catalogued, etc - more events) into some archival repository / museum. Atb & hth, Paul. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Stead Sent: 11 June 2013 11:06 To: [email protected]; crm-sig Subject: Re: [Crm-sig] ISSUE: add Activity subclass Discovery (Finding) Vladimir As you know we do/try not to add classes to the model unless it forms an anchor for some properties or is structurally necessary. So what are the new properties that justify the proposed new sub-class? The alternative is just to type an instance of E7 Activity. REgds SdS Stephen Stead Tel +44 20 8668 3075 Mob +44 7802 755 013 E-mail [email protected] LinkedIn Profile http://uk.linkedin.com/in/steads -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Vladimir Alexiev Sent: 11 June 2013 09:57 To: 'crm-sig' Cc: 'Dominic Oldman'; 'Maj, Lec'; [email protected] Subject: [Crm-sig] ISSUE: add Activity subclass Discovery (Finding) Proposal: add subclass of Activity called Discovery (or Finding). Justification: for archaeological objects, quite often we don't have Production data, but we have data about the Discovery of the object (who, when, where). Examples from the wild: 1. BM data has associations such as Excavated by, Found/Acquired by, Excavated/Findspot, etc. In ResearchSpace we map this to a subclass as described above: bmo:EX_Discovery rdfs:subClassOf crm:E7_Activity; rdfs:label "Discovery"; rdfs:comment "The activity of finding, excavating or collecting an object". See here: https://confluence.ontotext.com/display/ResearchSpace/BM+Association+Mapping +v2#BMAssociationMappingv2-FoundBy https://confluence.ontotext.com/display/ResearchSpace/BM+Association+Mapping +v2#BMAssociationMappingv2-Findspot 2. The Fundamental Relations TR (Doerr, Tzompanaki) www.cidoc-crm.org/docs/TechnicalReport429_April2012.pdf uses a made up (non-standardized) class C2.Finding (or C2.Finding_Event) for this purpose. The TR gives a similar justification: "Especially in the archaeological field of study, one is interested in Things found in a certain Place. This place could be a from (history) for this thing especially when the creation place is unknown." 3. CLAROS also singles out the Finding event, but instead of rdf:type (i.e. an RDF class) uses P2_has_type with a blank node: http://data.clarosnet.org/doc:jameel/object/EA1956.1145.ttl crm:P2_has_type _38:Event_FindObject; Here "_38:" indicates the blank node, and its use makes no sense (esp. because it's not present in the data) Best regards! Vladimir _______________________________________________ Crm-sig mailing list [email protected] http://lists.ics.forth.gr/mailman/listinfo/crm-sig _______________________________________________ Crm-sig mailing list [email protected] http://lists.ics.forth.gr/mailman/listinfo/crm-sig
