linked.art Data Model Walkthrough
Download as PPTX, PDF1 like320 views
The document outlines the linked art model, which promotes a linked open data framework for cultural heritage institutions to publish usable data effectively across various organizational platforms. It emphasizes an iterative and collaborative approach to data modeling, focusing on usability and interoperability, while utilizing established ontologies like CIDOC-CRM and associated vocabularies. Key components include classifications, identifiers, and a structure that supports varying data completeness and application use cases.
linked.art Data Model Walkthrough
- 1. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Linked.Art: Linked Open Usable Data Rob Sanderson, David Newbury Semantic Architect, Software & Data Architect J. Paul Getty Trust rsanderson@getty.edu, dnewbury@getty.edu @azaroth42, @workergnome
- 2. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Linked Art Model A Linked Open Data model, designed to work across museums and to enable functional applications. • Homogenized model across many institutions • Supports varying levels of data completeness • Ontology: CIDOC-CRM (plus a little) • Vocabularies: AAT, ULAN, TGN • Focused on Usability
- 3. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Linked Art Model Linked Art enables cultural heritage institutions to easily publish their data for use by both digital research projects and for non-specialist developers. 90% of the use cases of 90% of the organizations, with 10% of the complexity
- 8. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Successful Data Models… • Solve actual challenges, documented as use cases • Using data that is captured and available • Allow consistent description of shared use cases • Allow for addition of further information • Can be productively used • Via easy-to-implement services • With easy-to-implement applications • Provide interoperability with other data • Are clearly documented with relevant examples
- 9. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Successful Data Models… Are developed … • Iteratively • We will not get it right first time • Responsively • We will adapt it in response to feedback • Responsibly • We will consider changes/features carefully • Collaboratively • We will engage with the community and stakeholders
- 10. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Successful Data Models… Focus on the primary resources of concern for the domain Core Classes: • Object • Activity • Person • Place • Time
- 11. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Name, Identifier Data Model: Classes Man Made Object, Physical Object Activity, Beginning / Ending Activities, Transfer Activities, Attribute Assignment Information Object, Visual Item, Linguistic Object Type, Measurement Unit, Material, Language, Currency Actor, Person, Group
- 12. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Some Notes on Classes • Physical Object is used for collections of physical things (due to CIDOC-CRM arcana) • Information Object is used for collections of non-physical things • Internal End of Existence+Activity classes are used, as CIDOC-CRM doesn’t define any (does for Start+Activity) • Name is Appellation + Linguistic Object, as Names almost always have a Language • Internal Payment class is needed as a way to transfer MonetaryAmounts
- 13. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Core Properties • Every resource must have exactly one URI that identifies it. • Every resource must have exactly one class that it instantiates.
- 14. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Shared Pattern: Classification • CIDOC-CRM defines basic classes like ManMadeObject. We need more specialized ones like Painting, Photograph • We use AAT to classify the CRM classes, rather than extending the ontology • Any class can have a classification
- 16. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Shared Pattern: Identifiers Identifiers can be associated with any resource for non LOD identities.
- 18. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Shared Pattern: Label, Names • Every resource can have a single label, intended for simple displays, and one or more Names. • Names are Linguistic Objects and Appellations, and can have parts, intended to capture the full data.
- 20. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Shared Pattern: Statements • A lot of information can be captured only as strings, rather than machine-readable data. • Any resource can have one or more statements associated with it, classified as to the type of statement.
- 22. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Shared Pattern: Partitioning • Almost all classes in CIDOC-CRM can be partitioned into smaller, more granular components Parts of objects Roles, events Sections, segments Geo hierarchy Group structure Name parts Broader / Narrower (not used in linked.art)
- 26. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Object Model: Depicts, Subject, Style
- 30. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Attribute Assignment • Attribute Assignment is a descriptive activity at the documentation level, not an activity that affects the object directly • The assigned resource relates to the assigned_to resource, in some way according to the type
- 32. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedArt& Vocabularies @azaroth42 @workergnome rsanderson; dnewbury @getty.edu Thank You! Rob Sanderson, David Newbury rsanderson@getty.edu, dnewbury@getty.edu @azaroth42, @workergnome
Editor's Notes
- #8: If you only need half of the completeness, you should not be punished in terms of usability. Should be able to get close to the maximum usability for the particular use case’s completeness requirements.