PERICLES project partner Panos Mitzias (CERTH/ITI) introduces the work done in the area of domain ontologies for Art & Media.

1. 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)

2. ◦Upper-level ontology: Linked Resource Model (LRM)
◦Domain ontology: Art and Media, with sub-domains
Digital Video Art (DVA)
Software-based Art (SBA)
Born-digital Archives (BDA)
Ontologies in PERICLES

3. Main notions adopted from LRM in the Art and Media ontology:
◦Resource
◦Agent
◦Activity
◦Dependency
◦Description
LRM Adoption

4. ◦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
...
AbstractResource
realizedAs
ConcreteResource

5. Example - realizedAs

6. 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

7. Activity: Temporal entity that represents an action or set of
actions.
Subclasses*:
◦ CreationActivity
◦ AcquisitionActivity
◦ MigrationActivity
◦ etc.
* extensions to LRM
Activity

8. Dependency
lrm:Resource_1
lrm:Dependency
lrm:Resource_2 lrm:Resource_N
...
lrm:Description
lrm:Descriptionlrm:Plan
lrm:Plan
lrm:Resource_Μ
...

9. Example - Data Dependency

10. ◦ HardwareDependency
Specifies 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.
◦ SoftwareDependency
Indicates the dependency of a Resource or Activity on a specific software - name, version, etc.
◦ DataDependency
Implies 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

11. Predefined (but extensible) intention types:
◦ conceptual intention
Qualifies a dependency as having significance to the artist’s conceptualization of the artwork.
◦ functional intention
Qualifies a dependency required for the proper, consistent and complete functioning of the artwork.
◦ compatibility intention
Defines dependencies where different types of software/hardware components can be substituted and still
operate satisfactorily together.
Dependency Intentions

12. 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…

13. Thank you!

14. Demonstrate the three types of dependencies, by following the
process below:
1. Introduce already existing resources of domain
2. Specify a challenge/risk for a selected resource
3. Instantiate and explain the new implemented concepts
4. Execute different scenarios
5. Discuss results
Description of Evaluation Exercise