parthenos-entities/src/main/resources/references/3. Parthenos Entities Model Description v 1.8.docx

Parthenos Entities: Research Infrastructure Model DRAFT

V1.8

FORTH-ICS

First Created: 25/5/2016

Update: 30/8/2106

Document History

Version/date	Date	Changes/approval	Author/Approved by
V 1.0	25/5/2016	Initial version	George, Martin
V 1.1	25/5/2016	Minor Editing	George
V 1.2	2/6/2016	Relation pe27 add	George
V 1.3	7/6/2016	Physical Curation and Hosting Classes removed, changed property names to ‘pp’ format from ‘pe’, added class curated thing	George
V 1.4	7/6/2016	Minor Editing	George
V 1.5	10/6/2016	Alignment with discussions from WP5/6 Joint Meeting in Crete	George
V1.6	11/7/2016	Corrections to document based on feedback from CNR. Corrections and feedback on model from Athina. Check of IsA relations on classes and properties. Fixed where necessary. Added names to all relations and classes in relation description tables. Added shortcut links to all relations for easier use of doc. Added more referred classes and relations from CIDOC CRM and CRMdig. Made extended names for repeated relation names like ‘has part’ in order to conform with Gcube. Added class and relation hierarchy table for ease of navigation of doc + better overview of model.	George, Leonardo Candela, Athina
V1.7	18/8/2016	Added three new properties to the model pp39 is metadata for and pp40 created successor of, pp41 is index of. These three properties are added in order to allow tracking and management of changes in metadata.	Doerr, Bruseker
V1.8	30/8/2016	Added new property pp42 ‘has declarative time’	Bruseker

Parthenos Entities: Research Infrastructure Model DRAFT

The Parthenos Entities (PE) propose an ontological model and RDF schema to encode data of use in supporting the activities and aims of research infrastructures to pool and connect services, software, datasets and to enable users of such services to reach the actors and understand the knowledge generation processes which generated the offered datasets. Research infrastructures integrate highly heterogeneous resources for an often equally heterogeneous public. A central component of the activity of and RI in a digital environment involves building a data model that will support intuitive and accurate recall of information produced within the domain supported. It is the implicit or explicit belief of communities that organize into RIs that the integration of data from different members of the community offers not only the possibility of more efficient research and knowledge sharing but also the asking and answering of new questions by the crossing of data by sections of the community that normally would not consider their data in relation. Within this frame, PE proposes an ontological model that tries to capture the general basic entities deployed in building RI registries which is offered both as an intellectual tool for the checking and generation of such models and also as a means to create a common expression by which data could be shared across research communities, thus creating an RI of RIs. Such an effort is a logical extension of the belief inherent to individual research communities but broadened to an interdisciplinary scale.

PE is modelled as an extension of CIDOC CRM, the ISO standard ontology for cultural heritage data, and CRMdig, an extension of the latter which models provenance information in digitization processes. In this way, the modelling of a minimal metadata set for use in a registry as proposed above can be complimented by full modelling of detailed datasets in order to provide a rich web of data that can be accessed from the starting point of an RI registry. CIDOC CRM with its open extension policy and support of analytic data generated by empirical sciences with regards to the human past provides a suitably general ontology to allow for the integration of data across a wide spread of humanities and scientific disciplines.

PE is being developed in the context of the Parthenos Project, a European funded project.

Table of Contents

Parthenos Entities: Research Infrastructure Model DRAFT 1

Hierarchies 7

Class Hierarchy 7

Relations Hierarchy 8

Classes 10

PE1 Service 10

PE2 Hosting Service 10

PE3 Curating Service 11

PE5 Digital Hosting Service 12

PE6 Software Hosting Service 13

PE7 Data Hosting Service 14

PE8 E-Service 14

PE10 Digital Curating Service 15

PE11Software Curating Service 16

PE12 Data Curating Service 17

PE13 Software Computing E-Service 18

PE14 Software Delivery E-Service 19

PE15 Data E-Service 20

PE16 Curated Software E-Service 21

PE17 Curated Data E-Service 22

PE18 Dataset 22

PE19 Persistent Digital Object 23

PE20 Volatile Digital Object 23

PE21 Persistent Software 24

PE22 Persistent Dataset 25

PE23 Volatile Software 26

PE24 Volatile Dataset 26

PE25 RI Consortium 27

PE26 RI Project 27

PE27 Service Action[DRAFT – do not implement yet] 28

PE28 Curation Plan 28

PE29 Access Point 28

PE30 Digital Object Insert [DRAFT – do not implement yet] 29

PE31 Digital Object Remove [DRAFT – do not implement yet] 29

PE32 Curated Thing 30

Relations 31

PP1 currently offers (currently offered by) 31

PP2 providedby (provides) 31

PP3 requested by (requests) 31

PP4 hosts object (is object hosted by) 31

PP6 hosts digital object (is digital object hosted by) 31

PP7 hosts software object (is software object hosted by) 32

PP8 hosts dataset (is dataset hosted by) 32

PP11 curates volatile digital object (was volatile digital object curated by) 32

PP12 curates volatile software (was volatile software curated by) 32

PP13 curates volatile dataset (was volatile dataset curated by) 33

PP14 runs on request (is run by) 33

PP15 delivers on request (is delivered by) 33

PP16 has persistent digital object part (is persistent digital object part of) 33

PP17 has snapshot (is snapshot of) 34

PP18 has digital object part (is digital object part of) 34

PP19 has persistent software part (is persistent software part of) 34

PP20 has persistent dataset part (is persistent dataset part of) 35

PP21 has software part (is software part of) 35

PP22 has release (is release of) 35

PP23 has dataset part (is dataset part of) 35

PP24 has dataset snapshot (is dataset snapshot of) 36

PP25 is maintained by (maintains) 36

PP28 has designated access point (is designated access point of) 36

PP29 uses access protocol (is access protocol used by) 36

PP31 used curation plan(was curation plan used by) 37

PP32 curates (was curated by) 37

PP33 inserted [Draft – Do not implement yet] 37

PP34 inserted into [Draft – Do not implement yet] 37

PP36 removed [Draft – Do not implement yet] 38

PP37 removed from [Draft – Do not implement yet] 38

PP38 executes (was executed by) [Draft – Do not implement yet] 38

PP39 is metadata for (has metadata) 39

PP40 created successor of (was deprecated by) 39

PP41 is index of (was indexed by) 39

Referred Classes 40

D1 Digital Object 40

D14 Software 40

E7 Activity 40

E21 Person 41

E39Actor 41

E40 Legal Body 42

E65 Creation 42

E70 Thing 42

Referred Relations 44

P1 is identified by (identifies) 44

P9 consists of (forms part of) 44

P14 carried out by (performed) 44

P15 was influenced by (influenced) 45

P16 used specific object (was used for) 45

P33 used specific technique (was used by) 46

P106 is composed of (forms part of) 46

P129 is about (is subject of) 47

P130 shows features of (features are also found on) 47

P147curated (was curated by) 48

Hierarchies

Class Hierarchy

#	IsA Hierarchy	Orig.	Reg?
E7	Activity	CRM	N
PE26	RI Project	PE	Y
PE27	Service Action [Draft]	PE	Y
PE1	Service	PE	Y
PE2	Hosting Service	PE	Y
PE5	Digital Hosting Service	PE	Y
PE6	Software Hosting Service	PE	Y
PE13	Software Computing E-Service	PE	Y
PE16	Curated Software E-Service	PE	Y
PE14	Software Delivery E-Service	PE	Y
PE16	Curated Software E-Service	PE	Y
PE7	Data Hosting Service	PE	Y
PE15	Data E-Service	PE	Y
PE17	Curated Data E-Service	PE	Y
PE3	Curating Service	PE	Y
PE10	Digital Curating Service	PE	Y
PE11	Software Curating Service	PE	Y
PE16	Curated Software E-Service	PE	Y
PE12	Data Curating Service	PE	Y
PE17	Curated Data E-Service	PE	Y
PE8	E-Service	PE	Y
PE13	Software Computing E-Service	PE	Y
PE16	Curated Software E-Service	PE	Y
PE14	Software Delivery E-Service	PE	Y
PE16	Curated Software E-Service	PE	Y
PE15	Data E-Service	PE	Y
PE17	Curated Data E-Service	PE	Y
E65	Creation	CRM	N
E77	Permanent Item	CRM	N
E39	Actor	CRM	Y
E40	Legal Body	CRM	Y
PE25	RI Consortium	PE	Y
E70	Thing	CRM	Y
PE32	Curated Thing	PE	Y
E78	Curated Holding	CRM	Y
PE20	Volatile Digital Object	PE	Y
E71	Man Made Thing	CRM	N
E24	Physical Man Made Thing	CRM	N
E78	Curated Holding	CRM	Y
E28	Conceptual Object	CRM	N
E89	Propositional Object	CRM	N
E73	Information Object	CRM	N
E29	Design or Procedure	CRM	N
PE28	Curation Plan	PE	Y
D1	Digital Object	dig	Y
PE19	Persistent Digital Object	PE	Y
PE21	Persistent Software	PE	Y
PE22	Persistent Dataset	PE	Y
PE20	Volatile Digital Object	PE	Y
PE23	Volatile Software	PE	Y
PE24	Volatile Dataset	PE	Y
PE18	Dataset	PE	Y
PE22	Persistent Dataset	PE	Y
PE24	Volatile Dataset	PE	Y
D14	Software	dig	Y
PE21	Persistent Software	PE	Y
PE23	Volatile Software	PE	Y

Relations Hierarchy

#	Hierarchy	Domain	Range	Origin
P1	is identified by	E1 CRM Entity	E41 Appelation	CRM
PP28	has designated access point (is designated access point of)	PE8 E-Service	PE29 Access Point	PE
P9	consists of (forms part of)	E4 Period	E4 Period	CRM
PP1	currently offers (currently offered by)	PE26 RI Project	PE1 Service	PE
PP38	Executes (is executed by)	PE1 Service	PE27 Service Action	PE
P14	carried out by (performed)	E7 Activity	E39 Actor	CRM
PP2	Provided by (provides)	PE1 Service	E39 Actor	PE
PP3	Requested by (requests)	PE27 Service Action	E39 Actor	PE
P15	was influenced by (influenced)	E7 Activity	E1 CRM Entity	CRM
PP25	is maintained by (maintains)	PE26 RI Project	PE25 RI Consortium	PE
P16	used specific object (was used for)	E7 Activity	E70 Thing	CRM
PP4	hosts object (is object hosted by)	PE2 Hosting Service	E70 Thing	PE
PP6	hosts digital object (is digital object hosted by)	PE5 Digital Hosting Service	D1 Digital Object	PE
PP7	hosts software object (is software object hosted by)	PE6 Software Hosting Service	D14 Software	PE
PP8	hosts dataset (is dataset hosted by)	PE7 Data Hosting Service	PE18 Dataset	PE
PP14	runs on request (is run by)	PE13 Software Computing E-Service	D14 Software	PE
PP15	delivers on request (is delivered by)	PE14 Software Delivery E-Service	D14 Software	PE
PP29	uses access protocol (is access protocol used by)	PE8 E-Service	D14 Software	PE
PP40	created successor of (was deprecated by)	E65 Creation	PE22 Persistent Dataset	PE
PP32	curates (is curated by)	PE3 Curating Service	PE32 Curated Thing	PE
PP11	curates volatile digital object (was volatile D/O curated by)	PE10 Digital Curating Service	PE20 Volatile Digital Object	PE
PP12	curates volatile software (was volatile software curated by)	PE11 Software Curating Service	PE23 Volatile Software	PE
PP13	curates volatile dataset (was volatile D/S curated by)	PE12 Data Curating Service	PE24 Volatile Dataset	PE
P147	curated (was curated by)	E87 Curation Activity	E78 Curated Holding	CRM
P33	used specific technique (was used by)	E7 Activity	E29 Design or Procedure	CRM
PP31	used curation plan (was curation plan used by)	PE3 Curating Service	PE28 Curation Plan	PE
P106	is composed of (forms part of)	E90 Symbolic Object	E90 Symbolic Object	CRM
PP16	has persistent D/O part (is persistent D/O part of)	PE19 Persistent Digital Object	PE19 Persistent Digital Object	PE
PP19	has persistent S/W part (is persistent S/W part of)	PE21 Persistent Software	PE21 Persistent Software	PE
PP20	has persistent D/S part (is persistent D/S part of)	PE22 Persistent Dataset	PE22 Persistent Dataset	PE
PP18	has D/O part (is D/O part of)	PE20 Volatile Digital Object	D1 Digital Object	PE
PP21	has S/W part (is S/W part of)	PE23 Volatile Software	D14 Software	PE
PP23	has D/S part (is D/S part of)	PE24 Volatile Dataset	PE18 Dataset	PE
P129	is about (is subject of)	E89 Propositional Object	E1 CRM Entity	CRM
PP39	is metadata for (has metadata)	PE22 Persistent Dataset	D1 Digital Object	PE
P130	shows features of (features also found on)	E70 Thing	E70 Thing	CRM
PP17	has snapshot (is snapshot of)	PE20 Volatile Digital Object	PE19 Persistent Digital Object	PE
PP22	has release (is release of)	PE23 Volatile Software	PE21 Persistent Software	PE
PP24	has dataset snapshot (is dataset snapshot of)	PE24 Volatile Dataset	PE22 Persistent Dataset	PE

Classes

PE1 Service

Class Label	PE1 Service
Subclass of	E7 Activity
Superclass of	PE2 Hosting Service PE3 Curating Service PE8 E-Service
Scope Note	This class comprises declared offers by some instance of E39Actor of their willingness and ability to execute an activity or series of activities at the request of another instance of E39 Actor for the specific benefit of the latter. The identity of a service therefore depends on the individual instance of E39 actor making the offer, the type of activity(ies)offered and/or the type of product resultant from such an activity(ies). An instance of a PE1 Service begins to exist with the declaration of the ability and willingness of an instance of E39 actor to perform the particular set of activities for the benefit of another actor. The instance of PE1 Service ends when either the declared willingness or ability permanently ends. n.b.: this means that the ability may temporarily be interrupted, such as when an actor is on vacation or where the machine on which the service relies is being repaired, without meaning that the service as such has ended. A service need not continually be running in order for it be considered to be continuous, for example a service may be defined to fall within certain working hours. The instance of PE1 Service includes all auxiliary abilities of the same actor to execute the respective activities, but not services provided by third parties in the course of the service provisioning.
Examples	The local car repair shop’s car repair services.

New Direct Properties

Label	Domain	Range	Scope Note
PP38 executes	PE1	PE27	Links to the Service Action carried out in fulfilment of the Service Offer

PE2 Hosting Service

Class Label	PE2 Hosting Service
Subclass of	PE1 Service
Superclass of	PE 5 Digital Hosting Service
Scope Note	This class comprises declared offers by some instance of E39Actorto hold, protect and provide access to one or more objects in a generic sense, either physical or conceptual, at the request of an instance of E39 Actor, where the latter may be the initial party or a second party. An instance of PE2 Hosting Service begins from the moment of agreement between the contracting parties that the host will carry out these holding and protection activities in order to provide access, upon request, to some instance or instances of E70 Thing for the sake of the client. The hosting services continue so long as the hosting actor retains the ability to provide access to the object(s) to the client. The instance of hosting service ends when the host is either no longer willing or able to provide access to the objects that they undertook to hold and protect for the client.
Examples	Amazon cloud hosting of a user’s files [PE5]

New Direct Properties

Label	Domain	Range	Scope Note
PP4Hosts Object	PE2	E70	Link to the object(s) (generic) of which the service is a host

PE3 Curating Service

Class Label	PE3 Curating Service
Subclass of	PE1 Service
Superclass of	PE10 Digital Curating Service
Scope Note	This class comprises declared offers by some instance of E39 Actor of their willingness and ability to engage in a series of selection and organization activities on a collection of objects according to a specified plan. The identity of the curation service is tied to the collection of which it is the curator. A curation service comes into existence for the curation of some determinate collection taken as a whole, and is further determined in its identity by provider of the service and the plan which is adopted in order to carry out the curation. It is, in particular, the nature of the object of curation to be a collection in the sense of a plurality of objects from which parts can be added or removed without the overall identity of that collection being changed. An instance of PE3 Curating Service begins when the curator initiates the selection and organization of a collection of objects under the declared curation plan. The curating service may take over the curation of an existing collection or begin the curation of a new collection. So as long as the curator maintains these selecting and organizing activities of these objects according to the declared plan, the curation activity is considered on-going, regardless of any particular activities or lack thereof at any one time. Should the actor no longer be willing to engage in these activities or the objects be unavailable in a permanent manner, then the instance of PE3 Curating Service is to be considered ended. While curated objects may need to be hosted, this service may or may not be undertaken by the same actor. Therefore hosting can be documented separately and attributed to the appropriate third party actor.
Examples	Curation of the Collection of Ancient Greek Art by Nikolas Papadimitriou at the Museum of Cycladic Art

Inherited / Mapped Properties

Label	Domain	Range	Scope Note
PP31 used curation plan	PE3	PE28	Link to a document indicating the curation plan
PP32 curates	PE3	PE32	Indicates the collection of objects which this service curates

PE5 Digital Hosting Service

Class Label	PE5 Digital Hosting Service
Subclass of	PE2 Hosting Service
Superclass of	PE6 Software Hosting Service PE7 Data Hosting Service
Scope Note	This class comprises declared offers by some instance of E39Actorto hold, protect and provide access to one or more digital objects at the request of an instance of E39 Actor. The identity of digital hosting is determined by the type of object that the host undertakes to keep and provide access to. The hosting is digital in the sense that the object being held and protected is of a digital nature. Digital hosting does not entail the running of machines and software. An instance of PE5Digital Hosting Service begins from the moment of agreement between the contracting parties that the host will carry out these holding and protection activities in order to provide access, upon request, to some instance or instances of D1Digital Object for the sake of the client. Digital hosting services continue so long as the hosting actor retains the ability to provide access to the hosted object(s) to the client. The instance of hosting service ends when the host is either no longer willing or able to provide access to the object or collection of objects that they undertook to hold and protect for the client.
Examples	Google Art hosting of the digital images of the collections of Mathaf: the Arab Museum of Modern Art

New Direct Properties

Label	Domain	Range	Scope Note
PP6 Hosts Digital Object	PE5	D1	Link to the digital object(s) (generic) of which the service is a host

PE6 Software Hosting Service

Class Label	PE6 Software Hosting Service
Subclass of	PE5 Digital Hosting Service
Superclass of	PE13 Software Computing E-Service PE14 Software Delivery E-Service
Scope Note	This class comprises declared offers by some instance of E39Actor to hold and protect one or more software objects at the request of an instance of E39 Actor. The identity of software hosting is determined by the type of object that the host undertakes to keep and provide access to. The hosting is an instance of PE6 Software Hosting Service, just in case the object or objects which are held and protected are software. Software hosting does not entail the running of machines and software. An instance of PE6 Software Hosting Service begins from the moment of agreement between the contracting parties that the host will carry out these holding and protection activities in order to provide access, upon request, to some instance or instances of D14 Software for the sake of the client. Digital hosting services continue so long as the hosting actor retains the ability to provide access to the hosted object(s) to the client. The instance of hosting service ends when the host is either no longer willing or able to provide access to the object or collection of objects that they undertook to hold and protect for the client.
Examples	Hosting of the “Historical Software Collection” by archive.org

New Direct Properties

Label	Domain	Range	Scope Note
PP7 Hosts Software Object	PE6	D14	Link to the software(s) of which the service is a host

PE7 Data Hosting Service

Class Label	PE7 Data Hosting Service
Subclass of	PE5 Digital Hosting Service
Superclass of	PE15 Data E-Service
Scope Note	This class comprises declared offers by some instance of E39Actor to hold and protect one or more datasets at the request of an instance of E39 Actor. The identity of data hosting is determined by the type of object that the host undertakes to keep and provide access to. The hosting is an instance of PE7 Data Hosting Service, just in case the object or objects which are held and protected are dataset. Data hosting does not entail the running of machines and software. An instance of PE7 Data Hosting Service begins from the moment of agreement between the contracting parties that the host will carry out these holding and protection activities in order to provide access, upon request, to some instance or instances of PE18 Dataset for the sake of the client. Digital hosting services continue so long as the hosting actor retains the ability to provide access to the hosted object(s) to the client. The instance of hosting service ends when the host is either no longer willing or able to provide access to the object or collection of objects that they undertook to hold and protect for the client.
Examples	Archaeological Data Service’s Hosting of project data for the “Church Wilne Deserted Medieval Settlement, Derbyshire”

New Direct Properties

Label	Domain	Range	Scope Note
PP8 Hosts Dataset	PE7	PE18	Link to the dataset(s) of which the service is a host

PE8 E-Service

Class Label	PE8 E-Service
Subclass of	PE1Service
Superclass of	PE13 S/W Computing E-Service PE14 S/W Delivery E-Service PE15 Data E-Service
Scope Note	This class comprises declared offers to provide computing facilities by some instance of an E39 Actor who provisions a hardware/software setup that is able to respond to the use requests of some E39 Actor through automated receipt, manipulation and sending of data. The identity of an instance of PE8 E-Service depends on the particular communication software it runs, the actor maintaining the service active, and the logical communication address for issuing requests to it. An instance of PE8 E-Service comes into existence on the declaration of its offer and the making available of the service through some access point. It ceases to exist just in case the instance of E39 Actor is no longer willing or able to maintain the e-service when, for example an organization ceases to operation entirely, cancels the particular service, or is no longer able to support the software/hardware entailed.
Examples	IBM quantum computing service to quantum computing researchers Offer of community user to SETI project of computational power as part of its grid computing effort

New Direct Properties

Label	Domain	Range	Scope Note
PP28 has designated access point	PE8	PE29	Link to the web address at which the e-service can be accessed
PP29 uses access protocol	PE8	D14	Links the service to the access protocol, considered as a form of software, which it invokes

PE10 Digital Curating Service

Class Label	PE10 Digital Curating Service
Subclass of	PE3 Curating Service
Superclass of	PE11 Software Curating Service PE12 Data Curating Service
Scope Note	This class comprises declared offers by some instance of E39 Actor of their willingness and ability to engage in a series of selection and organization activities on an instance of PE20Volatile Digital Object according to a specified plan. The identity of the instance of PE10 Digital Curation Service is tied to the instance of PE20 Volatile Digital Object of which it is the curation. Instances of PE20 Volatile Digital Object are by their nature composites of different data sources. The curation activity on the volatile digital object in executing its plan for the volatile digital object - some functional goal - ensures the unity of the one volatile digital object and provides it an identity. Thus again, as with physical curation of a collection, it is normal for parts to be added or removed from the volatile digital object without its overall identity changing. It is precisely having this one object of the digital curation service that in turn allows the identification of the service itself, alongside knowledge of the curator and the plan. An instance of PE10 Digital Curating Service begins when the curator initiates the selection and organization of a volatile digital object under the declared curation plan. The curating service may take over the curation of an existing volatile digital object or begin the curation of an entirely new volatile digital object. As long as the curator maintains the will and ability to carry out these selecting and organizing activities according to the declared plan, the curation activity is considered on-going, regardless of any particular activities or lack thereof at any one time. Should the actor no longer be willing to engage in these activities or the volatile digital object be unavailable in a permanent manner, then the instance of PE10 Digital Curating Service is to be considered ended. While curated objects may need to be hosted, this service may or may not be undertaken by the same actor. Therefore hosting can be documented separately and attributed to the appropriate third party actor.
Examples

Properties

Label	Domain	Range	Scope Note
PP11 curates volatile digital object	PE10	PE20	Link to the digital objects which the service curates

PE11Software Curating Service

Class Label	PE11 Software Curating Service
Subclass of	PE10 Digital Curating Service
Superclass of	PE16 Curated Software E-Service
Scope Note	This class comprises declared offers by some instance of E39 Actor of their willingness and ability to engage in a series of selection and organization activities on an instance of PE23 Volatile Software according to a specified plan. The identity of the instance of PE11 Software Curation Service is tied to the instance of PE23 Volatile Software of which it is the curation. Instances of PE23 Volatile Software are by their nature composites of different data sources. The curation activity on the volatile software in executing its plan for the volatile software - some functional goal - ensures its unity and provides it an identity. Thus again, as with physical curation of a collection, it is normal for parts to be added or removed from the volatile software object without its overall identity changing. It is precisely having this one object of the software curation service that, in turn, allows the identification of the service itself, alongside knowledge of the curator and the plan. An instance of PE11Software Curating Service begins when the curator initiates the selection and organization of a volatile software object under the declared curation plan. The curating service may take over the curation of an existing volatile software object or begin the curation of an entirely new volatile software object. As long as the curator maintains the will and ability to carry out these selecting and organizing activities according to the declared plan, the curation activity is considered on-going, regardless of any particular activities or lack thereof at any one time. Should the actor no longer be willing to engage in these activities or the volatile digital object be unavailable in a permanent manner, then the instance of PE11Software Curating Service is to be considered ended. While curated objects may need to be hosted, this service may or may not be undertaken by the same actor. Therefore hosting can be documented separately and attributed to the appropriate third party actor.
Examples

Properties

Label	Domain	Range	Scope Note
PP12 curates volatile software object	PE11	PE23	Link to the volatile software object that is curated by this activity

PE12 Data Curating Service

Class Label	PE12 Data Curating Service
Subclass of	PE10 Digital Curating Service
Superclass of	PE17 Curated Data E-Service
Scope Note	This class comprises declared offers by some instance of E39 Actor of their willingness and ability to engage in a series of selection and organization activities on an instance of PE24 Volatile Dataset according to a specified plan. The identity of the instance of PE12 Data Curating Service is tied to the instance of PE24 Volatile Dataset of which it is the curation. Instances of PE24 Volatile Dataset are by their nature composites of different data sources. The curation activity on the volatile dataset in executing its plan for the volatile software - some functional goal - ensures its unity and provides it an identity. Thus again, as with physical curation of a collection, it is normal for parts to be added or removed from the volatile software object without its overall identity changing. It is precisely having this one object of the software curation service that, in turn, allows the identification of the service itself, alongside knowledge of the curator and the plan. An instance of Data Curating Service begins when the curator initiates the selection and organization of a volatile dataset under the declared curation plan. The curating service may take over the curation of an existing volatile dataset or begin the curation of an entirely new volatile dataset. As long as the curator maintains the will and ability to carry out these selecting and organizing activities according to the declared plan, the curation activity is considered on-going, regardless of any particular activities or lack thereof at any one time. Should the actor no longer be willing to engage in these activities or the volatile digital object be unavailable in a permanent manner, then the instance of Data Curating Service is to be considered ended. While curated objects may need to be hosted, this service may or may not be undertaken by the same actor. Therefore hosting can be documented separately and attributed to the appropriate third party actor.
Examples

Properties

Label	Domain	Range	Scope Note
PP13 curates volatile dataset	PE12	PE24	Link to the volatile software object that is curated by this activity

PE13 Software Computing E-Service

Class Label	PE13 Software Computing E-Service
Subclass of	PE6 Software Hosting Service PE8 E-Service
Superclass of	PE16 Curated Software E-Service
Scope Note	This class comprises instances of offers that are made up of both instances of PE6 Software Hosting and PE8 E-Service while additionally offering the ability and willingness to run a certain software for the requesting instance of E39 Actor. That is to say, the service provider takes on duties of hosting software, running the equipment to provide it, and delivering computing power to run it on request. The identity of this service is likewise composite depending on those factors relevant to instances of PE6 Software Hosting Service and PE8 E-Service, while additionally requiring that we have a clear identity of the software. The software release that the service runs may change without affecting the identity of the overall service, but to retain its identity this change would need to be documented in the access protocol, and to be archived in a log file. If an E39 Actor provides software computing e-services that run more than one software release at the same time, each of these should be documented as a separate instance of PE13 Software Computing E-Service. The processing software is not regarded as part of the service, but as being used by the service. An instance of PE13 Software Computing E-Service comes into existence on the declaration of its offer and the making available of the service along with the software it offers to run through some access point. It ceases to exist just in case the instance of E39 Actor is no longer willing or able to maintain the service when, for example if an organization ceases operation entirely, or the particular service is abandoned, if the software provisioned is permanently unavailable, or the host is no longer able to support the software/hardware entailed in providing the computing service.
Examples	The provisioning of Google Doc Service to clients by Google

Properties

Label	Domain	Range	Scope Note
PP14 runs on request	PE13	D14	This property associates an instance of software computing e-service with the software that it runs when requested.

PE14 Software Delivery E-Service

Class Label	PE14 Software Delivery E-Service
Subclass of	PE6 Software Hosting Service PE8 E-Service
Superclass of	PE16 Curated Software E-Service
Scope Note	This class comprises instances of offers that are made up of both instances of PE6 Software Hosting and PE8 E-Service while additionally offering the ability and willingness to deliver a particular piece of software to the requesting instance of E39 Actor. That is to say, the service provider takes on duties of hosting software, running the equipment to provide it, and delivering software on demand to a client. The identity of this service is likewise composite depending on those factors relevant to instances of PE6 Software Hosting Service and PE8 E-Service, while additionally requiring that we have a clear identity of the software to be delivered. The software release that the service delivers may change without affecting the identity of the overall service, but to retain its identity this change would need to be documented in the access protocol, and to be archived in a log file. If an E39 Actor provides e-services that deliver more than one software release at the same time, each of these should be documented as a separate instance of PE13 Software Computing E-Service. The processing software is not regarded as part of the service, but as being used by the service. An instance of PE14 Software Delivery E-Service comes into existence on the declaration of its offer and the making available of the service along with the software it offers to deliver through some access point. It ceases to exist just in case the instance of E39 Actor is no longer willing or able to maintain the service when, for example if an organization ceases operation entirely, or the particular service is abandoned, if the software provisioned is permanently unavailable, or the host is no longer able to support the software/hardware entailed in providing the computing service.
Examples	The offer of Github to a client to store his/her software and deliver it to other users

Properties

Label	Domain	Range	Scope Note
PP15 delivers on request	PE14	D14	This property associates an instance of software delivery e-service with the software that it delivers when requested.

PE15 Data E-Service

Class Label	PE15 Data E-Service
Subclass of	PE7 Data Hosting Service PE8 E-Service
Superclass of	PE17 Curated Data E-Service
Scope Note	This class comprises instances of offers that are made up of both instances of PE7 Data Hosting and PE8 E-Service while additionally offering the ability and willingness to offer electronic access to one or more datasets to the requesting instance of E39 Actor. That is to say, the service provider takes on duties of both hosting dataset(s) while running the equipment to provide access to the same. The identity of this service is a composite of those factors relevant to instances of PE7Data Hosting Service and PE8 E-Service. An instance of PE15Data E-Service comes into existence on the declaration of its offer and the making available of the service along with the dataset it aims to provide access to through some access point. It ceases to exist just in case the instance of E39 Actor is no longer willing or able to maintain the service when, for example if an organization ceases operation entirely, or the particular dataset is permanently unavailable, or the host is no longer able to support the software/hardware entailed in providing the computing service.
Examples	Offer of the British School at Athens of e-access to the digitized collection of the Byzantine Research Fund

PE16 Curated Software E-Service

Class Label	PE16 Curated Software E-Service
Subclass of	PE11 Software Curating Service PE14 Software Delivery E-Service PE13 Software Computing E-Service
Superclass of	-
Scope Note	This class comprises instances of offers that are made up of both instances of PE11 Software Curating Service and PE14S/W Delivery E-Service or PE13 Software Computing E-Service. Here then we speak of an offer both to curate some software(s), host it and running the equipment enabling its delivery to or running for clients. The identity of an instance of PE16Curated Software E-Service depends thus on the actor providing the service, the software hosted and curated, as well as the particular processing software its E-service component runs, as well as the logical communication address for issuing requests to it. The software release the service delivers or runs may change without affecting the identity of the overall service, but to retain its identity this change would need to be documented in the access protocol, and to be archived in a log file. An instance of PE16 Curated Software E-Service comes into existence on the declaration of its offer and the making available of the service along with the software it curates and delivers/runs through some access point. It ceases to exist just in case the instance of E39 Actor is no longer willing or able to maintain the service when, for example if an organization ceases operation entirely, or the particular service is abandoned, if the software to be hosted and curated is lost, or the host/curator is no longer able to support the software/hardware entailed in providing the delivery service.
Examples	Lyrasis offer of online hosted “Collection Space” collection management software of which they are also the developers/curators

PE17 Curated Data E-Service

Class Label	PE17 Curated Data E-Service
Subclass of	PE12 Data Curating Service PE15 Data E-Service
Superclass of	-
Scope Note	This class comprises instances of offers that are made up of both instances of PE12 Data Curating Service and PE15 Data E-Service. Here then we speak of an offer to curate some volatile dataset, host it and run the equipment necessary in order for clients to be able to access it electronically on demand. The identity of an instance of PE17 Curated Data E-Service depends thus on the actor providing the service, the dataset hosted and curated, the particular processing software its E-service component runs, as well as the logical communication address for issuing requests to it. An instance of PE17 Curated Data E-Service comes into existence on the declaration of its offer and the making available of the service along with the data it curates and provides access to through some access point. It ceases to exist just in case the instance of E39 Actor is no longer willing or able to maintain the service when, for example if an organization ceases operation entirely, or the particular service is abandoned, if the dataset to be hosted and curated is lost, or the host/curator is no longer able to support the software/hardware entailed in providing the delivery service.
Examples	Spotify custom crafted playlist for spotify user

PE18 Dataset

Class Label	PE18 Dataset
Subclass of	D1 Digital Object
Superclass of	PE22 Persistent Dataset PE24 Volatile Dataset
Scope Note	This class comprises identifiable immaterial items that can be represented as sets of bit sequences and whose content contains propositions about the objective world. The identity of an instance of PE18 is determined by its content in bit level encoding alongside its provenance. Any instance of a dataset may be composed of many distinct parts of other identifiable datasets. An aggregate of instances of PE18 dataset is treated as one instance and its parts can be documented as having a part of relation (p106). Datasets in practice are either volatile or persistent.
Examples	The collections database of the Qatar Museum Authority A 3D model of the Asinou Church in Crete

PE19 Persistent Digital Object

Class Label	PE19 Persistent Digital Object
Subclass of	D1 Digital Object
Superclass of	PE21 Persistent Software PE22 Persistent Dataset
Scope Note	This class comprises instances of D1 digital object which are the result of a distinct creation moment in which the whole of the content of the digital object as a propositional set was established and encoded at a bit level, whether this creation moment is known or not. Persistent digital objects are thus identified by their content, bit level encoding and the moment of production as a whole unit of information. An instance of persistent digital object continues to exist so long as one copy of it remains on one carrier which has been maintained without change to its internal content, thus propagating the original condition of the instance.
Examples	Version 5.2 of Microsoft DOS Backup file of the shared drive at FORTH Submitted copy of deliverable 5.1 in word format

Properties

Label	Domain	Range	Scope Note
PP16 has persistent D/O part	PE19	PE19	Indicates the persistent digital object part which is a part of the persistent digital object, used as abstract relation to form restriction for persistent software and dataset relations

PE20 Volatile Digital Object

Class Label	PE20 Volatile Digital Object
Subclass of	D1 Digital Object
Superclass of	PE23 Volatile Software PE24 Volatile Dataset
Scope Note	This class comprises instances of digital objects whose content is subject to continuous change without notice or necessary archiving of intermediate state but which can be considered as one with regards to its provenance in some curation plan that determes its information, goal and subject coverage. At any one point, an instance of PE20 Volatile Digital can be identified by an official snapshot of the actual data stream, an instance of PE19 Persistent Digital Object, taken by the responsible curating authority which has as ancestors any previous snaphosts taken of the data stream. The curator assigns a persistent identifier to the official snapshot and is the only individual who can identify the true representative snapshot. Reference to the content of an instance of PE20 Volatile Digital Object is down by way of the official snapshot.
Examples	The catalogue of iTunes Store music offerings The Archive of Archaeological Data Service UK

Properties

Label	Domain	Range	Scope Note
PP17 has snapshot	PE20	PE19	Indicates the snapshot that is representative of the volatile dataobject according to a curator.
PP18 has volatile D/O part	PE20	D1	Indicates that a volatile data object can have as part some other volatile dataset

PE21 Persistent Software

Class Label	PE21 Persistent Software
Subclass of	D14 Software PE19 Persistent Digital Object
Superclass of
Scope Note	This class compromises instances of digital objects that that can be executed on a computer to perform specific operations. In particular, an instance of PE21 Persistent software is the necessary information to process datasets algorithmically and to transform or integrate datasets in a collaborative infrastructure. The identity of a software depends on its content on the bit-level of encoding. The validity of the results produced by the software’s application depends categorically on its algorithmic correctness. A software release is defined as an instance of software. The software release begins to exist with its provision by the actor who is responsible for producing it. We also include in this category all data structures and formal ontologies that are used to configure the behavior of the software at an infrastructure component level.
Examples	Sketchup

Properties

Label	Domain	Range	Scope Note
PP19 has persistent S/W part	P21	P21	Indicates the persistent software of which the software instance may be composed

PE22 Persistent Dataset

Class Label	PE22 Persistent Dataset
Subclass of	PE18 Dataset PE19 Persistent Digital Object
Superclass of
Scope Note	This class compromises datasets that contain collections of data, records or information kept as a persistent unit of information in the knowledge generation process from primary records up to any level of aggregation or integration. The identity of a dataset is given by its content on the bit-level of encoding and its provenance. Since large datasets have a very small chance to be “reinvented” with another meaning, it is often practical to base the identity of a dataset on the content only, and apply a respective disambiguation of provenance only in case of obviously accidental identity. Different versions of a dataset are regarded as different datasets. Their relation should be defined by metadata describing the derivation process, rather than by version numbers. In general, a dataset may be integrated from different sources of provenance, such as a corpus of inscriptions compiled from different publication or a snapshot of a complete digital library. The integrated dataset may preserve the units of information of the source from which it has taken components. The content of knowledge organization systems, such as gazetteers, author lists, thesauri and formal ontologies of terms at a particular point in time, fall under datasets.
Examples	Records of the Excavations at 198 High Street, Exeter (Exeter archive site 55)

Properties

Label	Domain	Range	Scope Note
PP20 has persistent D/S part	PE22	PE22	Indicates the persistent dataset of which the dataset may be composed
PP39 is metadata for	PE22	D1	Indicates that this instance of PE22 Dataset acts as a metadata set for the range instance of D1 Digital Object.

PE23 Volatile Software

Class Label	PE23 Volatile Software
Subclass of	D14 Software PE20 Volatile Digital Object
Superclass of
Scope Note	This class comprise software that is in the process of active development volatile software class is comprised of instances of the working copy of some software in development. The software in development is the necessary information to perform specific operations. The identity of an instance of PE23 Volatile Software depends on the unity provided it by the instance of PE11 Software Curating Service responsible for it, that provides it its unity of purpose. The PE11 Software Curating Service is responsible for the creation of instances of PE21 Persistent Software which are the official release of this development stream and the ability to find and run its instructions at some time.
Examples	Source code of development of Sketchup

Properties

Label	Domain	Range	Scope Note
PP21 has S/W part	PE23	D14	Indicates the software, persistent or volatile, that forms a part of this volatile software
PP22 has Release	PE23	PE21	Indicates the persistent software version released at some point which stands as an identifier and usable product from the volatile software production

PE24 Volatile Dataset

Class Label	PE24 Volatile Dataset
Subclass of	PE18 Dataset PE20 Volatile Digital Object
Superclass of
Scope Note	This class comprises datasets that are changed without notice or archiving of intermediate states but maintained by an instance of PE12 Data Curating Service. The identity of a volatile dataset is enabled by the unity given to it by curation programme that operates on it, that bequeaths the volatile dataseta common information goal and subject coverage. In order for an instance of PE24 Volatile Dataset to be referenceable it is necessary for the official curator to take snapshots, creating instances of PE22 Persistent Data Set which can be assigned and official identifier and referenced. Volatile datasets are typically whole databases or mash-ups with active data feeds.
Examples	Ancient World Online Blogspot curated by Charles Jones

Properties

Label	Domain	Range	Scope Note
PP23 has D/S Part	PE24	PE18	Indicates the datasets, volatile or persistent, that form part of the volatile dataset
PP24 has dataset snapshot	PE24	PE22	Indicates the representative snapshot of the volatile dataset created at some point to stand as an identifier for the whole volatile dataset

PE25 RI Consortium

Class Label	PE25 RI Consortium
Subclass of	E40 Legal Body
Superclass of
Scope Note	This class comprises special groups of actors who come together for the purpose of supporting a research infrastructure project. An RI Consortium can be composed of all other types of actors including other RI Consortiums. An RI Consortium is identified by its commonality of purpose and not by its membership at any one time. The group comes into existence with the agreement to maintain some collective project. So long as the group continues to support the common RI project and is non-empty the consortium continues to exist.
Examples	Parthenos Consortium Ariadne Consortium Clarin Consortium

Properties

Label	Domain	Range	Scope Note
PP25 is maintained by	PE26	PE25	Indicates the RI project of which the consortium is the maintainer and chief supporter

PE26 RI Project

Class Label	PE26 RI Project
Subclass of	E7 Activity
Superclass of
Scope Note	This class comprises instances of collaborative enterprise undertaken over a period of time by an instance of PE25 RI Consortium with the intention of supporting research activities by providing a number of services to instances of E39 Actor. The project’s existence depends on the continued maintenance by some consortium. It ends when there is no consortium left to maintain it.
Examples	Parthenos Project Ariadne Project Clarin Project

PE27 Service Action[DRAFT – do not implement yet]

Class Label	PE27 Service Action
Subclass of	E7 Activity
Superclass of
Scope Note	This class comprises instances of actions taken out in the performance of a request to a service to fulfill its function. This class is a holding class to model actions undertaken in response to service requests. Please DO NOT model.
Examples

PE28 Curation Plan

Class Label	PE28 Curation Plan
Subclass of	E29 Design or Procedure
Superclass of
Scope Note	This class comprises instances of plans that guide curation projects and which provide the information necessary to understand the intention and overall aim of an actor in carrying out some instances of PE3 Curating Service.
Examples

PE29 Access Point

Class Label	PE29 Access Point
Subclass of	E51 Contact Point
Superclass of
Scope Note	This class comprises instances of web addresses and network addresses by which e-services can be accessed.
Examples

PE30 Digital Object Insert [DRAFT – do not implement yet]

Class Label	PE30 Digital Object Insert
Subclass of	D7 Digital Machine Event E79 Part Addition
Superclass of
Scope Note	This class comprises activities which result in the augmentation of a volatile digital object through the addition of some instance of a P20 Persistent Digital Object. The act is effectuated through a digital event which alters the target volatile digital object by adding to its aggregate whole some defined persistent digital object. The resulting effect does not change the overall identity of the volatitle digital object which is added to, but allows for the partial documentation of additions to the aggregate composition of the volatile digital object whose identity can only be ascertained through knowledge of the overall digital curation activity and its plan. Nevertheless, the documentation of such inserts allows for reasoning on the history and development of the curated volatile digital object. Instances of PE30 Digital Object Insert are not ususally systematically recorded, but may be done for significant events.
Examples	Insertion of excavation archive records relative to Knossos collections material into collections management system of the British School at Athens. Insertion of Beatle back catalogue into the Spotify music collections.

Properties

Label	Domain	Range	Scope Note
PP33 inserted	PE30	PE19	Indicates a persistent digital object which is the source object of insertion by the digital object insert event
PP34 inserted into	PE30	PE20	Indicates the volatile digital object into which an identifiable persistent object was added by the digital insert event

PE31 Digital Object Remove [DRAFT – do not implement yet]

Class Label	PE31 Digital Object Remove
Subclass of	D7 Digital Machine Event E80 Part Removal
Superclass of
Scope Note	This class comprises activities which result in the diminution of a volatile digital object through the removal of some instance of a P20 Persistent Digital Object. The act is effectuated through a digital event which alters the target volatile digital object by adding to its aggregate whole some defined persistent digital object. The resulting effect does not change the overall identity of the volatitle digital object which is added to, but allows for the partial documentation of additions to the aggregate composition of the volatile digital object whose identity can only be ascertained through knowledge of the overall digital curation activity and its plan. Nevertheless, the documentation of such inserts allows for reasoning on the history and development of the curated volatile digital object. Instances of PE30 Digital Object Insert are not ususally systematically recorded, but may be done for significant events.
Examples	Removal of Prince related material from the Youtube streaming service on request of the artist formerly known as Prince.

Properties

Label	Domain	Range	Scope Note
PP36 removed	PE31	PE19	Indicates a persistent digital object which is the target for removal by the digital object removal event
PP37 removed from	PE31	PE20	Indicates the volatile digital object from which the digital object removal event removed a persisent digital object

PE32 Curated Thing

Class Label	PE32 Curated Thing
Subclass of	E70 Thing
Superclass of	E78 Curated Holding PE20 Volatile Digital Object
Scope Note	This class comprises aggregations of instances of either E18 Physical Thing or of PE20 Volatile Digital Object that are assembled and maintained by one or more instances of E39 Actor over time for a specific purpose and audience, and according to a particular collection development plan. Items may be added or removed from an instance of P32 Curated Thing in pursuit of this plan. The instance of PE32 Curated Thing gets identity not through a physical togetherness of things, nor through a concatentation of information objects, but rather through the deliberate management of the curated thing according to a plan.
Examples

Relations

PP1 currently offers (currently offered by)

Relation Label	PP1 currently offers (currently offered by)
Subrelation of	P9 consists of (forms part of)
Superrelation of	-
Domain	PE26 RI Project
Range	PE1 Service
Scope	Allows research infrastructure project to be linked to the services it presently offers
Examples

PP2 providedby (provides)

Relation Label	PP2 provided by (provides)
Subrelation of	P14 carried out by (performed)
Superrelation of	-
Domain	PE1 Service
Range	E39 Actor
Scope	Indicates the intention and willingness of an actor to carry out some service
Examples

PP3 requested by (requests)

Relation Label	PP3 requested by (requests)
Subrelation of	p14 carried out by (performed)
Superrelation of	-
Domain	PE27 Service Action
Range	E39 Actor
Scope	Allows the recording of a request by some actor for some service action.
Examples

PP4 hosts object (is object hosted by)

Relation Label	PP4 hosts object (is object hosted by)
Subrelation of	P16 used specific object (was used for)
Superrelation of	PP6 hosts digital object (is digital object hosted by)
Domain	PE2 Hosting Service
Range	E70 Thing
Scope	Indicates the generic relation of provision of some hosting service of an object of any kind.
Examples

PP6 hosts digital object (is digital object hosted by)

Relation Label	PP6 hosts digital object (is digital object hosted by)
Subrelation of	PP4 hosts object (is object hosted by)
Superrelation of	PP7 hosts software object (is software object hosted by) PP8 hosts dataset (is dataset hosted by)
Domain	PE5 Digital Hosting Service
Range	D1 Digital Object
Scope	Indicates the relation of provision of a hosting service of a digital object of any kind.
Examples

PP7 hosts software object (is software object hosted by)

Relation Label	PP7 hosts software object (is software object hosted by)
Subrelation of	PP6 hosts digital object (is digital object hosted by)
Superrelation of	-
Domain	PE6 Software Hosting Service
Range	D14 Software
Scope	Indicates the relation of provision of some hosting service of a software object.
Examples

PP8 hosts dataset (is dataset hosted by)

Relation Label	PP8 hosts dataset (is dataset hosted by)
Subrelation of	PP6 hosts digital object (is digital object hosted by)
Superrelation of	-
Domain	PE7 Data Hosting Service
Range	PE18 Dataset
Scope	Indicates the relation of provision of some hosting service of a dataset object.
Examples

PP11 curates volatile digital object (was volatile digital object curated by)

Relation Label	PP11 curates volatile digital object (was volatile digital object curated by)
Subrelation of	PP32 curates (was curated by)
Superrelation of	PP12 curates volatile software (was volatile software curated by) PP13 curates volatile dataset (was volatile D/S curated by)
Domain	PE10 Digital Curating Service
Range	PE20 Volatile Digital Object
Scope	This property associates an instance of digital curating service with the digital object of which it is the curation activity.
Examples

PP12 curates volatile software (was volatile software curated by)

Relation Label	PP12 curates volatile software (was volatile software curated by)
Subrelation of	PP11 curates volatile digital object (was volatile digital object curated by)
Superrelation of	-
Domain	PE11 Software Curating Service
Range	PE23 Volatile Software
Scope	This property associates an instance of software curating service with the software of which it is the curation activity.
Examples

PP13 curates volatile dataset (was volatile dataset curated by)

Relation Label	PP13 curates volatile dataset (was volatile dataset curated by)
Subrelation of	PP11 curates volatile digital object (was volatile digital object curated by)
Superrelation of	-
Domain	PE12 Data Curating Service
Range	PE24 Volatile Dataset
Scope	This property associates an instance of data curating service with the volatile dataset of which it is the curation activity.
Examples

PP14 runs on request (is run by)

Relation Label	PP14 runs on request (is run by)
Subrelation of	P16 used specific object (was used for)
Superrelation of	-
Domain	PE13 Software Computing E-Service
Range	D14 Software
Scope	This property associates an instance of software computing e-service with the software that it runs when requested.
Examples

PP15 delivers on request (is delivered by)

Relation Label	PP15 delivers on request (is delivered by)
Subrelation of	P16 used specific object (was used for)
Superrelation of	-
Domain	PE14 Software Delivery E-Service
Range	D14 Software
Scope	This property associates an instance of software delivery e-service with the software that it delivers when requested.
Examples

PP16 has persistent digital object part (is persistent digital object part of)

Relation Label	PP16 has persistent D/O part (is persistent D/O part of)
Subrelation of	P106 is composed of (forms part of)
Superrelation of	PP19 has persistent software part (is persistent software part of) PP20 has persistent dataset part (is persistent dataset part of)
Domain	PE19 Persistent Digital Object
Range	PE19 Persistent Digital Object
Scope	This property associates an instance of PE19 Persistent Digital Object with a structural part of that instance which is, in turn, also an instance of PE19 Persistent Object. An instance of PE19 Persistent Digital Object can only have parts which are themselves also instances of PE19. This is in juxtaposition to PE20 Volatile Digital Object which may have parts which are themselves either instances of P20 Volatile Digital Object or P19 Persistent Digital Object.
Examples

PP17 has snapshot (is snapshot of)

Relation Label	PP17 has snapshot (is snapshot of)
Subrelation of	P130 shows features of (features are also found on)
Superrelation of	PP22 has release (is release of) PP24 has dataset snapshot (is dataset snapshot of)
Domain	PE20 Volatile Digital Object
Range	P19 Persistent Digital Object
Scope	This property associates an instance of PE20 Volatile Digital Object with an instances of PE19 Persistent Object which at any one point stands as an official version of the overall data stream.
Examples

PP18 has digital object part (is digital object part of)

Relation Label	PP18 has digital object part (is digital object part of)
Subrelation of	P106 is composed of (forms part of)
Superrelation of	PP21 has software part (is software part of) PP23 has dataset part (is dataset part of)
Domain	PE20 Volatile Digital Object
Range	D1 Digital Object
Scope	This property associates an instance of PE20 Volatile Digital Object with a structural part of that instance. This structural part may be another instance of D1 Digital object, be it also a PE20 Volatile Digital Object or in fact be an instance of PE19 Persistent Object.
Examples

PP19 has persistent software part (is persistent software part of)

Relation Label	PP19 has persistent software part (is persistent software part of)
Subrelation of	PP16 has persistent digital object part (is persistent digital object part of)
Superrelation of	-
Domain	PE21 Persistent Software
Range	PE21 Persistent Software
Scope	This property associates an instance of PE21 Persistent Software with a structural part of that instance which is, in turn, also an instance of PE21 Persistent Software.
Examples

PP20 has persistent dataset part (is persistent dataset part of)

Relation Label	PP20 has persistent dataset part (is persistent dataset part of)
Subrelation of	PP16 has persistent digital object part (is persistent digital object part of)
Superrelation of	-
Domain	PE22 Persistent Dataset
Range	PE22 Persistent Dataset
Scope	This property associates an instance of PE22 Persistent Dataset with a structural part of that instance which is, in turn, also an instance of PE22 Persistent Dataset.
Examples

PP21 has software part (is software part of)

Relation Label	PP21 has software part (is software part of)
Subrelation of	PP18 has digital object part (is digital object part of)
Superrelation of	-
Domain	PE23 Volatile Software
Range	D14 Software
Scope	This property associates an instance of PE23 Volatile Software with a structural part of that instance. This structural part will be an instance of D14 Software and can be either of its subclasses, PE21 Persistent Software of PE23 Volatile Software.
Examples

PP22 has release (is release of)

Relation Label	PP22 has release (is release of)
Subrelation of	PP17 has snapshot (is snapshot of)
Superrelation of	-
Domain	PE23 Volatile Software
Range	PE21 Persistent Software
Scope	This property associates an instance of PE23Volatile Softwarewith an instances of PE21 PersistentSoftware which at any one point stands as an official version of that software development stream.
Examples

PP23 has dataset part (is dataset part of)

Relation Label	PP23 has dataset part (is dataset part of)
Subrelation of	PP18 has digital object part (is digital object part of)
Superrelation of	-
Domain	PE24 Volatile Dataset
Range	PE18 Dataset
Scope	This property associates an instance of PE24 Volatile Dataset with a structural part of that instance. This structural part will be an instance of PE18 Dataset and can be either of its subclasses, PE22 Persistent Dataset of PE24 Persistent Dataset.
Examples

PP24 has dataset snapshot (is dataset snapshot of)

Relation Label	PP24 has dataset snapshot (is dataset snapshot of)
Subrelation of	PP17 has snapshot (is snapshot of)
Superrelation of	-
Domain	PE24 Volatile Dataset
Range	PE22 Persistent Dataset
Scope	This property associates an instance of PE24Volatile Dataset with an instances of PE22 Persistent Dataset which at any one point stands as an official version of that dataset.
Examples

PP25 is maintained by (maintains)

Relation Label	PP25 is maintained by (maintains)
Subrelation of	P15 was influenced by (influenced)
Superrelation of	-
Domain	PE26 RI Project
Range	PE25 RI Consortium
Scope	This property indicates the relation that exists between an instance of PE25 RI Consortium and some instance of PE26 RI Project, where the instance of PE25 is the responsible group of actors who maintain and suPPort the instance of PE26.
Examples

PP28 has designated access point (is designated access point of)

Relation Label	PP28 has designated access point (is designated access point of)
Subrelation of	P1 is identified by (identifies)
Superrelation of	-
Domain	PE8 E-Service
Range	PE29 Access Point
Scope	Links an instance of a PE8 E-Service to the web address at which the e-service can be accessed.
Examples

PP29 uses access protocol (is access protocol used by)

Relation Label	PP29 uses access protocol (is access protocol used by)
Subrelation of	P16 used specific object (was used for)
Superrelation of	-
Domain	PE8 E-Service
Range	D14 Software
Scope	Links an instance of PE8 E-Service with the instance of D14 software which encodes the access protocol by which the e-service is to be accessed.
Examples

PP31 used curation plan(was curation plan used by)

Relation Label	PP31 used curation plan (was curation plan used by)
Subrelation of	P33 used specific technique (was used by)
Superrelation of	-
Domain	PE3 Curating Service
Range	PE28 Curation Plan
Scope	Links an instance of PE3 Curation Service with the plan that organizes this activity
Examples

PP32 curates (was curated by)

Relation Label	PP32 curates (was curated by)
Subrelation of
Superrelation of	P147 curated (was curated by) PP11 curates volatile digital object (was volatile D/O curated by)
Domain	PE3 Curating Service
Range	PE32 Curated Thing
Scope	Links an instance of PE3 Curation Service with the object or objects for which it provides curation services.
Examples

PP33 inserted [Draft – Do not implement yet]

Relation Label	PP33 inserted
Subrelation of	L10 and or p111
Superrelation of	-
Domain	PE30 Digital Object Insert
Range	PE19 Persistent Digital Object
Scope	Links an instance of PE30 Digital Insert Event to the persistent digital object which is the source object for insertion by this event
Examples

PP34 inserted into [Draft – Do not implement yet]

Relation Label	PP34 inserted into
Subrelation of	L11 and or p110
Superrelation of	-
Domain	PE30 Digital Object Insert
Range	PE20 Volatile Digital Object
Scope	Links an instance of PE30 Digital Insert Event to the volatile digital object which is the target object for insertion by this event
Examples

PP36 removed [Draft – Do not implement yet]

Relation Label	PP36 removed
Subrelation of	L10 and or p113
Superrelation of	-
Domain	PE31
Range	PE19
Scope	Links an instance of PE31 Digital Remove Event to the persistent digital object which is the target object for removal by this event
Examples

PP37 removed from [Draft – Do not implement yet]

Relation Label	PP37 removed from
Subrelation of	L11 and or p112
Superrelation of	-
Domain	PE31 Digital Object Remove
Range	PE20 Volatile Digital Object
Scope	Links an instance of PE31 Digital Insert Event to the volatile digital object which is the source object for removal by this event
Examples

PP38 executes (was executed by) [Draft – Do not implement yet]

Relation Label	PP38 executes
Subrelation of	P9 consists of (forms part of)
Superrelation of	-
Domain	PE1Service
Range	PE27 Service Action
Scope	Links an instance of PE1 Service to a PE27 Service Action which is executed at the request of some actor
Examples

PP39 is metadata for (has metadata)

Relation Label	PP39 is metadata for (has metadata)
Subrelation of	P129 is about (is subject of)
Superrelation of	-
Domain	PE22 Persistent Dataset
Range	D1 Digital Object
Scope	Relates an instance of PE22 Persistent Dataset to some other instance of D1 Digital Object for which it plays the role of metadata. This relation establishes that the function of the information contained in the domain instance of PE22 is to described the information contained in the range instance of D1.
Examples

PP40 created successor of (was deprecated by)

Relation Label	PP40 created successor of (was deprecated by)
Subrelation of	P16 used specific object (was used for)
Superrelation of	-
Domain	E65 Creation
Range	PE22 Persistent Dataset
Scope	Relates an instance of E65 Creation to an instance of E22 Persistent Dataset that is acting as a metadata set. The latter E22 Persistent Dataset is referred to in the act of creation, specifically as the object of some correction. It is thus deprecated in the act of creation of some new instance of E22 Persistent Dataset. The new instance can be considered the successor of this deprecated dataset. The most recent successor, all things being equal, represents the present state of knowledge.
Examples

PP41 is index of (was indexed by)

Relation Label	PP41 is index of (was indexed by)
Subrelation of
Superrelation of	-
Domain	PE24 Volatile Dataset
Range	D1 Digital Object
Scope	Relates an instance of PE24 to an instance of D1 Digital object in the capacity of being an index for the latter.
Examples

PP42 has declarative time (was declarative time of)

Relation Label	PP42 has declarative time (was declarative time of)
Subrelation of
Superrelation of	-
Domain	PE1 Service
Range	E61 Time Primitive
Scope	Relates an instance of PE1 Service to a time spand during which the service provider declares the service is, will be, has been in effect.
Examples

Referred Classes

D1 Digital Object

Class Label	D1 Digital Object
Subclass of	E73 Information Object
Superclass of	PE19 Persistent Digital Object PE20 Volatile Digital Object D14 Software PE18 Dataset
Scope Note	This class comprises identifiable immaterial items that can be represented as setsof bit sequences, such as data sets, e-texts, images, audio or video items, software,etc., and are documented as single units. Any aggregation of instances of D1 Digital Object into a whole treated as single unit is also regarded as an instance of D1 Digital Object. This means that for instance, the content of a DVD, an XML file on it, and an element of this file, are regarded as distinct instances of D1 Digital Object,mutually related by the P106 is composed of (forms part of) property. A D1 Digital Object does not depend on a specific physical carrier, and it can exist on one or more carriers simultaneously.
Examples
External Ontology Origin	CRMdig 3.2.1

D14 Software

Class Label	D14 Software
Subclass of	D1 Digital Object
Superclass of	PE21 Persistent Software PE23 Volatile Software
Scope Note	This class comprises software codes, computer programs, procedures and functions that are used to operate a system of digital objects.
Examples
External Ontology Origin	CRMdig 3.2.1

E7 Activity

Class Label	E7 Activity
Subclass of	E5 Event
Superclass of	PE1 Service PE26 RI Project PE27 Service Action
Scope Note	This class comprises actions intentionally carried out by instances of E39 Actor that result in changes of state in the cultural, social, or physical systems documented. This notion includes complex, composite and long-lasting actions such as the building of a settlement or a war, as well as simple, short-lived actions such as the opening of a door.
Examples
External Ontology Origin	CIDOC CRM 6.2.1

E21 Person

Class Label	E21 Person
Subclass of	E39 Actor E20 Biological Object
Superclass of
Scope Note	This class comprises real persons who live or are assumed to have lived. Legendary figures that may have existed, such as Ulysses and King Arthur, fall into this class if the documentation refers to them as historical figures. In cases where doubt exists as to whether several persons are in fact identical, multiple instances can be created and linked to indicate their relationship. The CRM does not propose a specific form to support reasoning about possible identity.
Examples
External Ontology Origin	CIDOC CRM 6.2.1

E39Actor

Class Label	E39 Actor
Subclass of	E77 Persistent Item
Superclass of	E21 Person E74 Group
Scope Note	This class comprises people, either individually or in groups, who have the potential to perform intentional actions of kinds for which someone may be held responsible. The CRM does not attempt to model the inadvertent actions of such actors. Individual people should be documented as instances of E21 Person, whereas groups should be documented as instances of either E74 Group or its subclass E40 Legal Body.
Examples
External Ontology Origin	CIDOC CRM 6.2.1

PP27 has designated contact	PE39	E39	Link to the actor whom is designated as the contact point for this service (may or may not be the actor who offers the service, may or may not form a member of the group or institution that provides a service)

E40 Legal Body

Class Label	E40 Legal Body
Subclass of	E74 Group
Superclass of	PE25 RI Consortium
Scope Note	This class comprises institutions or groups of people that have obtained a legal recognition as a group and can act collectively as agents. This means that they can perform actions, own property, create or destroy things and can be held collectively responsible for their actions like individual people. The term 'personne morale' is often used for this in French.
Examples
External Ontology Origin	CIDOC CRM 6.2.1

E65 Creation

Class Label	E65 Creation
Subclass of	E7 Activity
Superclass of
Scope Note	This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
Examples
External Ontology Origin	CIDOC CRM 6.2.1

Properties

Label	Domain	Range	Scope Note
PP40 created successor of	E65	PE22	Indicates the relation between the act of creation and a metadata set that is corrected in the act of creation.

E70 Thing

Class Label	E70 Thing
Subclass of	E77 Persistent Item
Superclass of	PE32 Curated Thing
Scope Note	This general class comprises discrete, identifiable, instances of E77 Persistent Item that are documented as single units, that either consist of matter or depend on being carried by matter and are characterized by relative stability. They may be intellectual products or physical things. They may for instance have a solid physical form, an electronic encoding, or they may be a logical concept or structure.
Examples
External Ontology Origin	CIDOC CRM 6.2.1

Referred Relations

P1 is identified by (identifies)

Relation Label	P1 is identified by (identifies)
Subrelation of	-
Superrelation of	PP28 has designated access point (is designated access point of)
Domain	E1 CRM Entity
Range	E41 Appellation
Scope	This property describes the naming or identification of any real world item by a name or any other identifier. This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
Examples
External Ontology Origin	CIDOC CRM 6.2.1

P9 consists of (forms part of)

Relation Label	P9 consists of (forms part of)
Subrelation of	-
Superrelation of	PP1 currently offers (currently offered by)
Domain	E4 Period
Range	E4 Period
Scope	This property associates an instance of E4 Period with another instance of E4 Period that is defined by a subset of the phenomena that define the former. Therefore the space time volume of the latter must fall within the space time volume of the former. This property is transitive.
Examples
External Ontology Origin	CIDOC CRM 6.2.1

P14 carried out by (performed) 

Relation Label	P14 carried out by (performed)
Subrelation of	-
Superrelation of	PP2 provided by (provides) PP3 requested by (requests)
Domain	E7 Activity
Range	E39 Actor
Scope	This property describes the active participation of an E39 Actor in an E7 Activity. It implies causal or legal responsibility. The P14.1 in the role of property of the property allows the nature of an Actor’s participation to be specified.
Examples
External Ontology Origin	CIDOC CRM 6.2.1

P15 was influenced by (influenced) 

Relation Label	P15 was influenced by (influenced)
Subrelation of	-
Superrelation of	PP25 is maintained by (maintains)
Domain	E7 Activity
Range	E1 CRM Activity
Scope	This is a high level property, which captures the relationship between an E7 Activity and anything that may have had some bearing upon it. The property has more specific sub properties.
Examples
External Ontology Origin	CIDOC CRM 6.2.1

P16 used specific object (was used for) 

Relation Label	P16 used specific object (was used for)
Subrelation of	-
Superrelation of	PP4 hosts object (is object hosted by) PP14 runs on request (is run by) PP15 delivers on request (is delivered by) PP29 uses access protocol (is access protocol used by)
Domain	E7 Activity
Range	E70 Thing
Scope	This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an E7 Activity. This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer. Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use.
Examples
External Ontology Origin	CIDOC CRM 6.2.1

P33 used specific technique (was used by) 

 

Relation Label	P33 used specific technique (was used by)
Subrelation of	-
Superrelation of	PP31 used curation plan (was curation plan used by)
Domain	E7 Activity
Range	E29 Design or Procedure
Scope	This property identifies a specific instance of E29 Design or Procedure in order to carry out an instance of E7 Activity or parts of it. The property differs from P32 used general technique (was technique of) in that P33 refers to an instance of E29 Design or Procedure, which is a concrete information object in its own right rather than simply being a term or a method known by tradition. Typical examples would include intervention plans for conservation or the construction plans of a building.
Examples
External Ontology Origin	CIDOC CRM 6.2.1

  

P106 is composed of (forms part of) 

Relation Label	P106 is composed of (forms part of)
Subrelation of	-
Superrelation of	PP16 has persistent digital object part (is persistent digital object part of) PP18 has digital object part (is digital object part of)
Domain	E90 Symbolic Object
Range	E90 Symbolic Object
Scope	This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. This property is transitive
Examples
External Ontology Origin	CIDOC CRM 6.2.1

P129 is about (is subject of)

Relation Label	P129 is about (is subject of)
Subrelation of	-
Superrelation of	PP39 is metadata about (has metadata)
Domain	E89 Propositional Object
Range	E1 CRM Entity
Scope	This property documents that an E89 Propositional Object has as subject an instance of E1 CRM Entity. This differs from P67 refers to (is referred to by), which refers to an E1 CRM Entity, in that it describes the primary subject or subjects of an E89 Propositional Object.
Examples
External Ontology Origin	CIDOC CRM 6.2.1

P130 shows features of (features are also found on)

Relation Label	P130 shows features of (features are also found on)
Subrelation of	-
Superrelation of	PP17 has snapshot (is snapshot of)
Domain	E70 Thing
Range	E70 Thing
Scope	This property generalises the notions of "copy of" and "similar to" into a directed relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. If the reason for similarity is a sort of derivation process, i.e., that the creator has used or had in mind the form of a particular thing during the creation or production, this process should be explicitly modelled. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons.
Examples
External Ontology Origin	CIDOC CRM 6.2.1

P147curated (was curated by)

Relation Label	P147 curated (was curated by)
Subrelation of	PP32 curates (is curated by)
Superrelation of	-
Domain	E87 Curation Activity
Range	E78 Collection
Scope	This property associates an instance of E87 Curation Activity with the instance of E78 Collection or collections with that is subject of that curation activity following some implicit or explicit curation plan.
Examples
External Ontology Origin	CIDOC CRM 6.2.1