3.2 European Virtual Marketplace Framework
37
1. evmpo:assessment: a proposition on the accuracy or performance of an entity
or an a expression of trust in an entity. Corresponding domain ontology: VIVO,
cf. Sect. 3.4.
2. evmpo:calendar_event: a meeting or activity which is scheduled or can be scheduled; this is defined to be equivalent with Vevent from the W3C iCalendar ontology (iCal) with time zones as datatypes, cf. Connolly and Miller [21]. Corresponding domain ontology: OTRAS, cf. Sect. 3.5.
3. evmpo:communication: any message (or an attachment or part of a message) that
is communicated. Corresponding domain ontology: VICO, cf. Sect. 3.5.
4. evmpo:information_content_entity: a journal article, a dataset or a graph. This
concept is defined to be equivalent with IAO_0000030, labelled “information content entity” through rdfs:label, from the Information Artifact Ontology
(IAO), cf. Ceusters [22]. Corresponding domain ontologies: OTRAS and VISO,
cf. Sect. 3.5 and Chap. 4.
5. evmpo:infrastructure: infrastructure of an EVMF-interoperable platform
(e.g. related to data, hardware and software). Corresponding domain ontologies:
MACRO and VISO, cf. Sect. 3.3 and Chap. 4.
6. evmpo:interpreter: this concept is defined to be the same as emmo-semiotics:Interpreter from the nominalist revision of Peirce’s semiotics, based on the
semiotic triad sign—object—interpretant, as included in the EMMO [15, 16];
therein, for any given triad, the interpreter is the entity that carries out the semiosis, taking the sign (a representamen) as an input and producing the interpretant
(another representamen) as an output [16, 23, 24]. Therefore, any potential agent
or communicating entity at EVMF-interoperable infrastructures is an interpreter.
Corresponding domain ontology: VICO, cf. Sect. 3.5.
7. evmpo:material: an amount of a physical substance (or mixture of substances)
that is part of a more comprehensive real-world object; this concept is defined
to be the same as emmo-physicalistic:Material from the EMMO [15, 16]. Corresponding domain ontologies: OSMO and VIVO, cf. Sects. 3.3 and 3.4.
8. evmpo:model: a sign that represents a physical object or process by direct similitude and/or within a mathematical framework; this concept is defined to be the
same as emmo-models:Model from the EMMO [15, 16]. Corresponding domain
ontologies: OSMO, VISO and VOV, cf. Sect. 3.3 and Chap. 4.
9. evmpo:process: the temporal evolution of one or multiple entities. Corresponding domain ontologies: MMTO, OSMO and VISO, cf. Sects. 3.3 and 3.4 as well
as Chap. 4.
10. evmpo:product: a good or service, to be acquired either on a EVMFinteroperable digital marketplace or off-site; services that can be traded on a
digital marketplace are specifically conceptualized by evmpo:tradeable_object.
Corresponding domain ontologies: MACRO, MMTO and OTRAS, cf. Sects. 3.3,
3.4 and 3.5.
11. evmpo:property: a representamen that is determined as an interpretant from
an observation process, involving a specific observer that perceives or measures it; this concept is defined to be the same as emmo-properties:Property
37
1. evmpo:assessment: a proposition on the accuracy or performance of an entity
or an a expression of trust in an entity. Corresponding domain ontology: VIVO,
cf. Sect. 3.4.
2. evmpo:calendar_event: a meeting or activity which is scheduled or can be scheduled; this is defined to be equivalent with Vevent from the W3C iCalendar ontology (iCal) with time zones as datatypes, cf. Connolly and Miller [21]. Corresponding domain ontology: OTRAS, cf. Sect. 3.5.
3. evmpo:communication: any message (or an attachment or part of a message) that
is communicated. Corresponding domain ontology: VICO, cf. Sect. 3.5.
4. evmpo:information_content_entity: a journal article, a dataset or a graph. This
concept is defined to be equivalent with IAO_0000030, labelled “information content entity” through rdfs:label, from the Information Artifact Ontology
(IAO), cf. Ceusters [22]. Corresponding domain ontologies: OTRAS and VISO,
cf. Sect. 3.5 and Chap. 4.
5. evmpo:infrastructure: infrastructure of an EVMF-interoperable platform
(e.g. related to data, hardware and software). Corresponding domain ontologies:
MACRO and VISO, cf. Sect. 3.3 and Chap. 4.
6. evmpo:interpreter: this concept is defined to be the same as emmo-semiotics:Interpreter from the nominalist revision of Peirce’s semiotics, based on the
semiotic triad sign—object—interpretant, as included in the EMMO [15, 16];
therein, for any given triad, the interpreter is the entity that carries out the semiosis, taking the sign (a representamen) as an input and producing the interpretant
(another representamen) as an output [16, 23, 24]. Therefore, any potential agent
or communicating entity at EVMF-interoperable infrastructures is an interpreter.
Corresponding domain ontology: VICO, cf. Sect. 3.5.
7. evmpo:material: an amount of a physical substance (or mixture of substances)
that is part of a more comprehensive real-world object; this concept is defined
to be the same as emmo-physicalistic:Material from the EMMO [15, 16]. Corresponding domain ontologies: OSMO and VIVO, cf. Sects. 3.3 and 3.4.
8. evmpo:model: a sign that represents a physical object or process by direct similitude and/or within a mathematical framework; this concept is defined to be the
same as emmo-models:Model from the EMMO [15, 16]. Corresponding domain
ontologies: OSMO, VISO and VOV, cf. Sect. 3.3 and Chap. 4.
9. evmpo:process: the temporal evolution of one or multiple entities. Corresponding domain ontologies: MMTO, OSMO and VISO, cf. Sects. 3.3 and 3.4 as well
as Chap. 4.
10. evmpo:product: a good or service, to be acquired either on a EVMFinteroperable digital marketplace or off-site; services that can be traded on a
digital marketplace are specifically conceptualized by evmpo:tradeable_object.
Corresponding domain ontologies: MACRO, MMTO and OTRAS, cf. Sects. 3.3,
3.4 and 3.5.
11. evmpo:property: a representamen that is determined as an interpretant from
an observation process, involving a specific observer that perceives or measures it; this concept is defined to be the same as emmo-properties:Property