1 / 14

Interesting Features of the CIDOC CRM

Interesting Features of the CIDOC CRM. Stephen Stead. Paveprime Ltd. Edinburgh July 2007. Interesting Features Outline. Conceptual Modeling Self Documentation Self Logging E29 Design or Procedure Meta Level Empirical Provenance Derivation Chains Inference Chains Research Provenance

lweinstein
Download Presentation

Interesting Features of the CIDOC CRM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interesting Features of the CIDOC CRM Stephen Stead Paveprime Ltd Edinburgh July 2007

  2. Interesting Features Outline • Conceptual Modeling • Self Documentation • Self Logging • E29 Design or Procedure Meta Level • Empirical Provenance • Derivation Chains • Inference Chains • Research Provenance • XML • E55 Type • CRM Development process • Open Questions • Mileage • F-stop

  3. Conceptual Modeling • Use of the CRM as a template for modeling a process or system • Distinct from mapping as there is no data to map (yet) • This model can then be used to design the data capture elements of the system • When data is captured already mapped to the CRM

  4. Conceptual Modeling (2)

  5. Here an E73 Information Object has as a part an E31 Document that documents the E73 Information Object itself Self Documentation

  6. Here an E65 Creation creates an E31 Document that documents the E65 Creation itself Self Logging

  7. Here an E65 Creation follows an E29 Design or Procedure to create a new E29 Design or Procedure E29 Design or Procedure Meta Level

  8. Empirical Provenance • Derivation Chains • Record the precise steps used to create a derivative • This allows • Validation that the derivative is trustworthy for answering the current research question • Discard of intermediate steps • Inference Chains • Same logic could be applied

  9. Research Provenance • When new knowledge is produced as part of a research project it’s provenance, precursors and influences should be captured • Creates a semantic web of derivation chains • Allow assessment of research projects by actual use of the products • Plus the length of the derivation chains produced • Instead of by the volume of material produced or the number of published citations

  10. Here we see the source, influences, motivation and research process captured

  11. <?xml version="1.0" encoding="UTF-8"?> <chi> <E73.Information_Object>photo_1_of_set_1_of_Edward_I_Wax_Reverse <P70B.is_documented_in> <E31.Document>XMP_content_of_photo_1_of_set_1_of_Edward_I_Wax_Reverse <P1F.is_identified_by> <E75.Conceptual_Object_Appellation>11-03-05-11-58-08-#01.xmp </E75.Conceptual_Object_Appellation> </P1F.is_identified_by> </E31.Document> </P70B.is_documented_in> <P106F.is_composed_of> <E31.Document>XMP_content_of_photo_1_of_set_1_of_Edward_I_Wax_Reverse <P106F.is_composed_of> <E31.Document>EXIF_component_of_XMP_content_of_photo_1_of_set_1_of_Edward_I_Wax_Reverse </E31.Document> </P106F.is_composed_of> </E31.Document> </P106F.is_composed_of> <P106F.is_composed_of > <E36.Visual_Item> Visual_content_of_photo_1_of_set_1_of_Edward_I_Wax_Reverse <P138F.represents> <E22.Man-Made_Object>Edward_I_Wax </E22.Man-Made_Object> </P138F.represents> </E36.Visual_Item> </P106F.is_composed_of> <P1F.is_identified_by> <E75.Conceptual_Object_Appellation>11-03-05-11-58-08-#01.tif </E75.Conceptual_Object_Appellation> </P1F.is_identified_by> <P129F.is_about> <E22.Man-Made_Object>Edward_I_Wax </E22.Man-Made_Object> </P129F.is_about> </E73.Information_Object> </chi> <E73.Information_Object id="photo_1_of_set_1_of_Edward_I_Wax_Reverse"> <P70.is_documented_in rev="true"> <E31.Document id="XMP_content_of_photo_1_of_set_1_of_Edward_I_Wax_Reverse"> <P1.is_identified_by> <E75.Conceptual_Object_Appellation>11-03-05-11-58-08-#01.xmp</E75.Conceptual_Object_Appellation> </P1.is_identified_by> </E31.Document> </P70.is_documented_in> <P106.is_composed_of> <E31.Document id="XMP_content_of_photo_1_of_set_1_of_Edward_I_Wax_Reverse"> <P106.is_composed_of > <E31.Document id="EXIF_component_of_XMP_content_of_photo_1_of_set_1_of_Edward_I_Wax_Reverse" /> </P106.is_composed_of> </E31.Document> <E36.Visual_Item id="Visual_content_of_photo_1_of_set_1_of_Edward_I_Wax_Reverse"> <P138.represents> <E22.Man-Made_Object id="Edward_I_Wax" /> </P138.represents> </E36.Visual_Item> </P106.is_composed_of> <P1.is_identified_by> <E75.Conceptual_Object_Appellation>11-03-05-11-58-08-#01.tif</E75.Conceptual_Object_Appellation> </P1.is_identified_by> <P129.is_about> <E22.Man-Made_Object id="Edward_I_Wax" /> </P129.is_about> </E73.Information_Object> XML

  12. E55 Type CRM Development process <P16.1.mode_of_use> <E55.Type>Subject <P2F.has_type> <E55.Type> Type of Mode of use <P2F.has_type> <E55.Type> Type of Type </E55.Type> </P2F.has_type> </E55.Type> </P2F.has_type> </E55.Type> </P16.1.mode_of_use> XML

  13. Open Questions • Mileage • “we traveled 4.3 miles upriver” • Is this the duration (ie E54 Dimension) of the E7 Activity? • F-stop • Is this • Type of Duration (E54 Dimension) • Type of E7 Activity • Type of use (P16.1 mode of use) • If P16.1 can you have more than one P16.1 off a single P16 used specific object • Aural equivalent of E36 Visual Item

More Related