1 BIOLOGICAL DOMAIN ONTOLOGIES & BASIC FORMAL ONTOLOGY Barry Smith.
PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies
-
Upload
periclesfp7 -
Category
Data & Analytics
-
view
129 -
download
1
Transcript of PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies
![Page 1: PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies](https://reader034.fdocuments.us/reader034/viewer/2022051709/5874759c1a28ab4a758b6323/html5/thumbnails/1.jpg)
GRANT AGREEMENT: 601138 | SCHEME FP7 ICT 2011.4.3 Promoting and Enhancing Reuse of Information throughout the Content Lifecycle taking account of Evolving Semantics [Digital Preservation]
PERICLES Art & Media Domain Ontologies Panos Mitzias (CERTH/ITI)
![Page 2: PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies](https://reader034.fdocuments.us/reader034/viewer/2022051709/5874759c1a28ab4a758b6323/html5/thumbnails/2.jpg)
◦Upper-level ontology: Linked Resource Model (LRM)
◦Domain ontology: Art and Media, with sub-domainsDigital Video Art (DVA)Software-based Art (SBA)Born-digital Archives (BDA)
Ontologies in PERICLES
![Page 3: PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies](https://reader034.fdocuments.us/reader034/viewer/2022051709/5874759c1a28ab4a758b6323/html5/thumbnails/3.jpg)
Main notions adopted from LRM in the Art and Media ontology:
◦Resource◦Agent◦Activity◦Dependency◦Description
LRM Adoption
![Page 4: PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies](https://reader034.fdocuments.us/reader034/viewer/2022051709/5874759c1a28ab4a758b6323/html5/thumbnails/4.jpg)
◦AbstractResource: Conceptual representation of an entity. ◦ConcreteResource: Concrete realization of an abstract resource.◦AggregatedResource: A set of multiple resources.
Abstract / Concrete / Aggregated Resource
AbstractResource
AggregatedResource
∩
ConcreteResource
ConcreteResource_1
ConcreteResource_2
ConcreteResource_N
realizedAs hasPart
...
AbstractResourcerealizedAs
ConcreteResource
![Page 5: PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies](https://reader034.fdocuments.us/reader034/viewer/2022051709/5874759c1a28ab4a758b6323/html5/thumbnails/5.jpg)
Example - realizedAs
![Page 6: PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies](https://reader034.fdocuments.us/reader034/viewer/2022051709/5874759c1a28ab4a758b6323/html5/thumbnails/6.jpg)
Agent: The “bearer” of change to the ecosystem.i.e. someone or something that brings change to a resource or participates in an activity.
Subclasses*: ◦ HumanAgent (individual, group, organization, etc.)◦ SoftwareAgent (operating system, media player, etc.)
* extensions to LRM
Agent
![Page 7: PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies](https://reader034.fdocuments.us/reader034/viewer/2022051709/5874759c1a28ab4a758b6323/html5/thumbnails/7.jpg)
Activity: Temporal entity that represents an action or set of actions.
Subclasses*: ◦ CreationActivity◦ AcquisitionActivity◦ MigrationActivity◦ etc.
* extensions to LRM
Activity
![Page 8: PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies](https://reader034.fdocuments.us/reader034/viewer/2022051709/5874759c1a28ab4a758b6323/html5/thumbnails/8.jpg)
Dependency
lrm:Resource_1
lrm:Dependency
lrm:Resource_2 lrm:Resource_N...
lrm:Description
lrm:Descriptionlrm:Plan
lrm:Plan
lrm:Resource_Μ...
![Page 9: PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies](https://reader034.fdocuments.us/reader034/viewer/2022051709/5874759c1a28ab4a758b6323/html5/thumbnails/9.jpg)
Example - Data Dependency
![Page 10: PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies](https://reader034.fdocuments.us/reader034/viewer/2022051709/5874759c1a28ab4a758b6323/html5/thumbnails/10.jpg)
◦ HardwareDependencySpecifies hardware requirements for a(n) (Abstract or Concrete or SoftwareAgent or Digital) Resource, or relations among them, in order for the Resource to function properly.
◦ SoftwareDependencyIndicates the dependency of a Resource or Activity on a specific software - name, version, etc.
◦ DataDependencyImplies the requirement of some knowledge, or data or information in order for a(n) (Abstract or Concrete or SoftwareAgent of Digital) Resource to achieve its purpose of existence or function. This kind of data may originate from human input, computer files (e.g. configuration files), network connection, live video, etc.
Dependency Types
![Page 11: PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies](https://reader034.fdocuments.us/reader034/viewer/2022051709/5874759c1a28ab4a758b6323/html5/thumbnails/11.jpg)
Predefined (but extensible) intention types:
◦ conceptual intentionQualifies a dependency as having significance to the artist’s conceptualization of the artwork.
◦ functional intentionQualifies a dependency required for the proper, consistent and complete functioning of the artwork.
◦ compatibility intentionDefines dependencies where different types of software/hardware components can be substituted and still operate satisfactorily together.
Dependency Intentions
![Page 12: PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies](https://reader034.fdocuments.us/reader034/viewer/2022051709/5874759c1a28ab4a758b6323/html5/thumbnails/12.jpg)
Latest version of Art and Media domain ontologies tackle the following:
◦Detailed description of material, actors, activities and entities involved.
◦Information capturing processes performed by a CH related agent for representing the life cycle of digital resources.
◦Significant properties and dependencies, which may indicate relevant risks.
Modelling issues addressed thus far…
![Page 13: PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies](https://reader034.fdocuments.us/reader034/viewer/2022051709/5874759c1a28ab4a758b6323/html5/thumbnails/13.jpg)
Thank you!
![Page 14: PERICLES workshop (London 15 October 2015) - Art & Media Domain Ontologies](https://reader034.fdocuments.us/reader034/viewer/2022051709/5874759c1a28ab4a758b6323/html5/thumbnails/14.jpg)
Demonstrate the three types of dependencies, by following the process below:
1. Introduce already existing resources of domain2. Specify a challenge/risk for a selected resource3. Instantiate and explain the new implemented concepts4. Execute different scenarios5. Discuss results
Description of Evaluation Exercise