Parthenos Entities: Research Infrastructure Model ongoing

Parthenos Entities: Research Infrastructure Model ongoing

Description:

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.

Status:

Ongoing

Contributors:

Parthenos Project

Description

Show Description Language Namespace
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. en WIP

Contributors

Parthenos Project

Identification

Base URI: https://ontome.net/ns/crmpe/

Project of belonging: CRMpem: An extension of CIDOC CRM to support the data management lifecycle

This namespace is ongoing and can be modified at any time. It is not advisable to use its classes and properties.

Namespaces to which this ongoing namespace refers

Namespace
CIDOC CRM version 7.1.2
CRMdig version 4.0
Referenced:

Labels

Label Language Last updated
Parthenos Entities: Research Infrastructure Model ongoing * en 2023-01-19

* : Standard label for this language

Versions

Parthenos Entities: Research Infrastructure Model ongoing is an ongoing namespace.

Root namespace: Parthenos Entities: Research Infrastructure Model

Published versions

Namespace Publication date
Parthenos Entities: Research Infrastructure Model, version 3.1 2021-06-23

Classes

Identifier Class Last updated Validation status
PE21 Persistent Software 2023-01-23 Validated
PE22 Persistent Dataset 2023-01-23 Validated
PE23 Volatile Software 2023-01-23 Validated
PE24 Volatile Dataset 2023-01-23 Validated
PE25 RI Consortium 2023-01-23 Validated
PE26 RI Project 2023-01-23 Validated
PE28 Curation Plan 2023-01-23 Validated
PE1 Service 2023-01-23 Validated
PE2 Hosting Service 2023-01-23 Validated
PE3 Curating Service 2023-01-23 Validated
PE5 Digital Hosting Service 2023-01-23 Validated
PE7 Data Hosting Service 2023-01-23 Validated
PE8 E-Service 2023-01-23 Validated
PE10 Digital Curating Service 2023-01-23 Validated
PE11 Software Curating Service 2023-01-23 Validated
PE12 Data Curating Service 2023-01-23 Validated
PE13 Software Computing E-Service 2023-01-23 Validated
PE18 Dataset 2023-01-23 Validated
PE14 Software Delivery E-Service 2023-01-23 Validated
PE15 Data E-Service 2023-01-23 Validated
PE16 Curated Software E-Service 2023-01-23 Validated
PE17 Curated Data E-Service 2023-01-23 Validated
PE19 Persistent Digital Object 2023-01-23 Validated
PE20 Volatile Digital Object 2023-01-23 Validated
PE29 Access Point 2023-01-23 Validated
PE32 Curated Thing 2023-01-23 Validated
PE33 E-Access Brokering Service 2023-01-23 Validated
PE34 Team 2023-01-23 Validated
PE35 Project 2023-01-23 Validated
PE36 Competency Type 2023-01-23 Validated
PE37 Protocol Type 2023-01-23 Validated
PE38 Schema 2023-01-23 Validated
PE39 Availability Type 2023-01-23 Validated
PE40 Programing Language 2023-01-23 Validated
PE41 Award Activity 2023-01-23 Validated
PE42 Funding Activity 2023-01-23 Validated
PE43 Encoding Type 2023-01-23 Validated
PE44 Audience Type 2023-01-23 Validated
PE6 Software Hosting Service 2023-01-23 Validated

Properties

Domain Identifier Property Range Last updated Validation status
Digital Curating Service – PE10 PP11 curates volatile digital object (is volatile digital object curated by) Volatile Digital Object – PE20 2023-01-19 Validated
Software Curating Service – PE11 PP12 curates volatile software (is volatile software curated by) Volatile Software – PE23 2023-01-19 Validated
Volatile Dataset – PE24 PP41 is index of (is indexed by) Digital Object – D1 2023-01-19 Validated
Service – PE1 PP42 has declarative time Time Primitive – E61 2023-01-19 Validated
Project – PE35 PP43 supported project activity (is project activity supported by) Activity – E7 2023-01-19 Validated
Activity – E7 PP60 had intended geographic scope (was intended geographic scope of) Place – E53 2023-01-19 Validated
Activity – E7 PP59 had intended audience (was intended audience of) Audience Type – PE44 2023-01-19 Validated
Digital Object – D1 PP58 is encoded with (is encoding of) Encoding Type – PE43 2023-01-19 Validated
Funding Activity – PE42 PP57 provided funding amount (was funding provided by) Monetary Amount – E97 2023-01-19 Validated
Award Activity – PE41 PP56 awarded for (was award of) CRM Entity – E1 2023-01-19 Validated
Award Activity – PE41 PP55 awarded (was thing awarded by) Thing – E70 2023-01-19 Validated
Award Activity – PE41 PP54 had awardee (was awardee of) Actor – E39 2023-01-19 Validated
Award Activity – PE41 PP53 had awarder (was awarder of) Actor – E39 2023-01-19 Validated
Software – D14 PP52 is programmed with (is used to programme) Programing Language – PE40 2023-01-19 Validated
Service – PE1 PP51 has availability (is availability of) Availability Type – PE39 2023-01-19 Validated
Digital Object – D1 PP50 accessible at (provides access to) Access Point – PE29 2023-01-19 Validated
E-Service – PE8 PP49 provides access point (is access point provided by) Access Point – PE29 2023-01-19 Validated
E-Service – PE8 PP48 uses protocol parameter (is protocol parameter of) Schema – PE38 2023-01-19 Validated
E-Service – PE8 PP47 has protocol type (is protocol type of) Protocol Type – PE37 2023-01-19 Validated
E-Access Brokering Service – PE33 PP46 brokers access to (has access brokered by) E-Service – PE8 2023-01-19 Validated
Service – PE1 PP45 has competency (is competency of) Competency Type – PE36 2023-01-19 Validated
Project – PE35 PP44 has maintaining team (is maintaining team of) Team – PE34 2023-01-19 Validated
RI Project – PE26 PP1 currently offers (is currently offered by) Service – PE1 2023-01-19 Validated
Service – PE1 PP2 provided by (provides) Actor – E39 2023-01-19 Validated
Hosting Service – PE2 PP4 hosts object (is object hosted by) Thing – E70 2023-01-19 Validated
Digital Hosting Service – PE5 PP6 hosts digital object (is digital object hosted by) Digital Object – D1 2023-01-19 Validated
Software Hosting Service – PE6 PP7 hosts software object (is software object hosted by) Software – D14 2023-01-19 Validated
Data Hosting Service – PE7 PP8 hosts dataset (is dataset hosted by) Dataset – PE18 2023-01-19 Validated
Data Curating Service – PE12 PP13 curates volatile dataset (is volatile dataset curated by) Volatile Dataset – PE24 2023-01-19 Validated
Software Computing E-Service – PE13 PP14 runs on request (is run by) Software – D14 2023-01-19 Validated
Software Delivery E-Service – PE14 PP15 delivers on request (is delivered by) Software – D14 2023-01-19 Validated
Persistent Digital Object – PE19 PP16 has persistent digital object part (is persistent digital object part of) Persistent Digital Object – PE19 2023-01-19 Validated
Volatile Digital Object – PE20 PP17 has snapshot (is snapshot of) Persistent Digital Object – PE19 2023-01-19 Validated
Volatile Digital Object – PE20 PP18 has digital object part (is digital object part of) Digital Object – D1 2023-01-19 Validated
Persistent Software – PE21 PP19 has persistent software part (is persistent software part of) Persistent Software – PE21 2023-01-19 Validated
Persistent Dataset – PE22 PP20 has persistent dataset part (is persistent dataset part of) Persistent Dataset – PE22 2023-01-19 Validated
Volatile Software – PE23 PP21 has software part (is software part of) Software – D14 2023-01-19 Validated
Volatile Software – PE23 PP22 has release (is release of) Persistent Software – PE21 2023-01-19 Validated
Volatile Dataset – PE24 PP23 has dataset part (is dataset part of) Dataset – PE18 2023-01-19 Validated
Volatile Dataset – PE24 PP24 has dataset snapshot (is dataset snapshot of) Persistent Dataset – PE22 2023-01-19 Validated
RI Project – PE26 PP25 has maintaining RI (is maintaining RI of) RI Consortium – PE25 2023-01-19 Validated
E-Service – PE8 PP28 has designated access point (is designated access point of) Access Point – PE29 2023-01-19 Validated
E-Service – PE8 PP29 uses access protocol (is access protocol used by) Software – D14 2023-01-19 Validated
Curating Service – PE3 PP31 uses curation plan (is curation plan used by) Curation Plan – PE28 2023-01-19 Validated
Curating Service – PE3 PP32 curates (is curated by) Curated Thing – PE32 2023-01-19 Validated
Persistent Dataset – PE22 PP39 is metadata for (has metadata) Digital Object – D1 2023-01-19 Validated
Creation – E65 PP40 created successor of (is deprecated by) Persistent Dataset – PE22 2023-01-19 Validated

Relations

Filter by

Source Relation Target Last updated Type
Service – PE1 rdfs:subClassOf Activity – E7 2023-01-19 ClassesRelation-HierarchyAssociation
Hosting Service – PE2 rdfs:subClassOf Service – PE1 2023-01-19 ClassesRelation-HierarchyAssociation
Curating Service – PE3 rdfs:subClassOf Service – PE1 2023-01-19 ClassesRelation-HierarchyAssociation
Digital Hosting Service – PE5 rdfs:subClassOf Hosting Service – PE2 2023-01-19 ClassesRelation-HierarchyAssociation
Software Hosting Service – PE6 rdfs:subClassOf Digital Hosting Service – PE5 2023-01-19 ClassesRelation-HierarchyAssociation
Data Hosting Service – PE7 rdfs:subClassOf Digital Hosting Service – PE5 2023-01-19 ClassesRelation-HierarchyAssociation
E-Service – PE8 rdfs:subClassOf Service – PE1 2023-01-19 ClassesRelation-HierarchyAssociation
Digital Curating Service – PE10 rdfs:subClassOf Curating Service – PE3 2023-01-19 ClassesRelation-HierarchyAssociation
Software Curating Service – PE11 rdfs:subClassOf Digital Curating Service – PE10 2023-01-19 ClassesRelation-HierarchyAssociation
Data Curating Service – PE12 rdfs:subClassOf Digital Curating Service – PE10 2023-01-19 ClassesRelation-HierarchyAssociation
Software Computing E-Service – PE13 rdfs:subClassOf Software Hosting Service – PE6 2023-01-19 ClassesRelation-HierarchyAssociation
Software Computing E-Service – PE13 rdfs:subClassOf E-Service – PE8 2023-01-19 ClassesRelation-HierarchyAssociation
Software Delivery E-Service – PE14 rdfs:subClassOf Software Hosting Service – PE6 2023-01-19 ClassesRelation-HierarchyAssociation
Software Delivery E-Service – PE14 rdfs:subClassOf E-Service – PE8 2023-01-19 ClassesRelation-HierarchyAssociation
Data E-Service – PE15 rdfs:subClassOf Data Hosting Service – PE7 2023-01-19 ClassesRelation-HierarchyAssociation
Data E-Service – PE15 rdfs:subClassOf E-Service – PE8 2023-01-19 ClassesRelation-HierarchyAssociation
Curated Software E-Service – PE16 rdfs:subClassOf Software Curating Service – PE11 2023-01-19 ClassesRelation-HierarchyAssociation
Curated Software E-Service – PE16 rdfs:subClassOf Software Delivery E-Service – PE14 2023-01-19 ClassesRelation-HierarchyAssociation
Curated Software E-Service – PE16 rdfs:subClassOf Software Computing E-Service – PE13 2023-01-19 ClassesRelation-HierarchyAssociation
Curated Data E-Service – PE17 rdfs:subClassOf Data Curating Service – PE12 2023-01-19 ClassesRelation-HierarchyAssociation
Curated Data E-Service – PE17 rdfs:subClassOf Data E-Service – PE15 2023-01-19 ClassesRelation-HierarchyAssociation
Dataset – PE18 rdfs:subClassOf Digital Object – D1 2023-01-19 ClassesRelation-HierarchyAssociation
Persistent Digital Object – PE19 rdfs:subClassOf Digital Object – D1 2023-01-19 ClassesRelation-HierarchyAssociation
Volatile Digital Object – PE20 rdfs:subClassOf Curated Thing – PE32 2023-01-19 ClassesRelation-HierarchyAssociation
Volatile Digital Object – PE20 rdfs:subClassOf Digital Object – D1 2023-01-19 ClassesRelation-HierarchyAssociation
Persistent Software – PE21 rdfs:subClassOf Software – D14 2023-01-19 ClassesRelation-HierarchyAssociation
Persistent Software – PE21 rdfs:subClassOf Persistent Digital Object – PE19 2023-01-19 ClassesRelation-HierarchyAssociation
Persistent Dataset – PE22 rdfs:subClassOf Dataset – PE18 2023-01-19 ClassesRelation-HierarchyAssociation
Persistent Dataset – PE22 rdfs:subClassOf Persistent Digital Object – PE19 2023-01-19 ClassesRelation-HierarchyAssociation
Volatile Software – PE23 rdfs:subClassOf Software – D14 2023-01-19 ClassesRelation-HierarchyAssociation
Volatile Software – PE23 rdfs:subClassOf Volatile Digital Object – PE20 2023-01-19 ClassesRelation-HierarchyAssociation
Volatile Dataset – PE24 rdfs:subClassOf Dataset – PE18 2023-01-19 ClassesRelation-HierarchyAssociation
Volatile Dataset – PE24 rdfs:subClassOf Volatile Digital Object – PE20 2023-01-19 ClassesRelation-HierarchyAssociation
RI Consortium – PE25 rdfs:subClassOf Team – PE34 2023-01-19 ClassesRelation-HierarchyAssociation
RI Project – PE26 rdfs:subClassOf Project – PE35 2023-01-19 ClassesRelation-HierarchyAssociation
Curation Plan – PE28 rdfs:subClassOf Design or Procedure – E29 2023-01-19 ClassesRelation-HierarchyAssociation
Access Point – PE29 rdfs:subClassOf Appellation – E41 2023-01-19 ClassesRelation-HierarchyAssociation
Curated Thing – PE32 rdfs:subClassOf Thing – E70 2023-01-19 ClassesRelation-HierarchyAssociation
Curated Holding – E78 rdfs:subClassOf Curated Thing – PE32 2023-01-19 ClassesRelation-HierarchyAssociation
E-Access Brokering Service – PE33 rdfs:subClassOf E-Service – PE8 2023-01-19 ClassesRelation-HierarchyAssociation
Team – PE34 rdfs:subClassOf Group – E74 2023-01-19 ClassesRelation-HierarchyAssociation
Project – PE35 rdfs:subClassOf Activity – E7 2023-01-19 ClassesRelation-HierarchyAssociation
Competency Type – PE36 rdfs:subClassOf Type – E55 2023-01-19 ClassesRelation-HierarchyAssociation
Protocol Type – PE37 rdfs:subClassOf Type – E55 2023-01-19 ClassesRelation-HierarchyAssociation
Schema – PE38 rdfs:subClassOf Software – D14 2023-01-19 ClassesRelation-HierarchyAssociation
Availability Type – PE39 rdfs:subClassOf Type – E55 2023-01-19 ClassesRelation-HierarchyAssociation
Programing Language – PE40 rdfs:subClassOf Type – E55 2023-01-19 ClassesRelation-HierarchyAssociation
Award Activity – PE41 rdfs:subClassOf Activity – E7 2023-01-19 ClassesRelation-HierarchyAssociation
Funding Activity – PE42 rdfs:subClassOf Award Activity – PE41 2023-01-19 ClassesRelation-HierarchyAssociation
Encoding Type – PE43 rdfs:subClassOf Type – E55 2023-01-19 ClassesRelation-HierarchyAssociation
Audience Type – PE44 rdfs:subClassOf Type – E55 2023-01-19 ClassesRelation-HierarchyAssociation
currently offers (is currently offered by) – PP1 rdfs:subPropertyOf consists of (forms part of) – P9 2023-01-19 PropertiesRelation-HierarchyAssociation
provided by (provides) – PP2 rdfs:subPropertyOf carried out by (performed) – P14 2023-01-19 PropertiesRelation-HierarchyAssociation
hosts object (is object hosted by) – PP4 rdfs:subPropertyOf used specific object (was used for) – P16 2023-01-19 PropertiesRelation-HierarchyAssociation
hosts digital object (is digital object hosted by) – PP6 rdfs:subPropertyOf hosts object (is object hosted by) – PP4 2023-01-19 PropertiesRelation-HierarchyAssociation
hosts software object (is software object hosted by) – PP7 rdfs:subPropertyOf hosts digital object (is digital object hosted by) – PP6 2023-01-19 PropertiesRelation-HierarchyAssociation
hosts dataset (is dataset hosted by) – PP8 rdfs:subPropertyOf hosts digital object (is digital object hosted by) – PP6 2023-01-19 PropertiesRelation-HierarchyAssociation
curates volatile digital object (is volatile digital object curated by) – PP11 rdfs:subPropertyOf curates (is curated by) – PP32 2023-01-19 PropertiesRelation-HierarchyAssociation
curates volatile software (is volatile software curated by) – PP12 rdfs:subPropertyOf curates volatile digital object (is volatile digital object curated by) – PP11 2023-01-19 PropertiesRelation-HierarchyAssociation
curates volatile dataset (is volatile dataset curated by) – PP13 rdfs:subPropertyOf curates volatile digital object (is volatile digital object curated by) – PP11 2023-01-19 PropertiesRelation-HierarchyAssociation
runs on request (is run by) – PP14 rdfs:subPropertyOf used specific object (was used for) – P16 2023-01-19 PropertiesRelation-HierarchyAssociation
delivers on request (is delivered by) – PP15 rdfs:subPropertyOf used specific object (was used for) – P16 2023-01-19 PropertiesRelation-HierarchyAssociation
has persistent digital object part (is persistent digital object part of) – PP16 rdfs:subPropertyOf is composed of (forms part of) – P106 2023-01-19 PropertiesRelation-HierarchyAssociation
has snapshot (is snapshot of) – PP17 rdfs:subPropertyOf shows features of (features are also found on) – P130 2023-01-19 PropertiesRelation-HierarchyAssociation
has digital object part (is digital object part of) – PP18 rdfs:subPropertyOf is composed of (forms part of) – P106 2023-01-19 PropertiesRelation-HierarchyAssociation
has persistent software part (is persistent software part of) – PP19 rdfs:subPropertyOf has persistent digital object part (is persistent digital object part of) – PP16 2023-01-19 PropertiesRelation-HierarchyAssociation
has persistent dataset part (is persistent dataset part of) – PP20 rdfs:subPropertyOf has persistent digital object part (is persistent digital object part of) – PP16 2023-01-19 PropertiesRelation-HierarchyAssociation
has software part (is software part of) – PP21 rdfs:subPropertyOf has digital object part (is digital object part of) – PP18 2023-01-19 PropertiesRelation-HierarchyAssociation
has release (is release of) – PP22 rdfs:subPropertyOf has snapshot (is snapshot of) – PP17 2023-01-19 PropertiesRelation-HierarchyAssociation
has dataset part (is dataset part of) – PP23 rdfs:subPropertyOf has digital object part (is digital object part of) – PP18 2023-01-19 PropertiesRelation-HierarchyAssociation
has dataset snapshot (is dataset snapshot of) – PP24 rdfs:subPropertyOf has snapshot (is snapshot of) – PP17 2023-01-19 PropertiesRelation-HierarchyAssociation
has maintaining RI (is maintaining RI of) – PP25 rdfs:subPropertyOf has maintaining team (is maintaining team of) – PP44 2023-01-19 PropertiesRelation-HierarchyAssociation
has designated access point (is designated access point of) – PP28 rdfs:subPropertyOf is identified by (identifies) – P1 2023-01-19 PropertiesRelation-HierarchyAssociation
uses access protocol (is access protocol used by) – PP29 rdfs:subPropertyOf used specific object (was used for) – P16 2023-01-19 PropertiesRelation-HierarchyAssociation
uses curation plan (is curation plan used by) – PP31 rdfs:subPropertyOf used specific technique (was used by) – P33 2023-01-19 PropertiesRelation-HierarchyAssociation
curated (was curated by) – P147 rdfs:subPropertyOf curates (is curated by) – PP32 2023-01-19 PropertiesRelation-HierarchyAssociation
is metadata for (has metadata) – PP39 rdfs:subPropertyOf is about (is subject of) – P129 2023-01-19 PropertiesRelation-HierarchyAssociation
created successor of (is deprecated by) – PP40 rdfs:subPropertyOf has created (was created by) – P94 2023-01-19 PropertiesRelation-HierarchyAssociation
supported project activity (is project activity supported by) – PP43 rdfs:subPropertyOf consists of (forms part of) – P9 2023-01-19 PropertiesRelation-HierarchyAssociation
has maintaining team (is maintaining team of) – PP44 rdfs:subPropertyOf was motivated by (motivated) – P17 2023-01-19 PropertiesRelation-HierarchyAssociation
has competency (is competency of) – PP45 rdfs:subPropertyOf had general purpose (was purpose of) – P21 2023-01-19 PropertiesRelation-HierarchyAssociation
has protocol type (is protocol type of) – PP47 rdfs:subPropertyOf used object of type (was type of object used in) – P125 2023-01-19 PropertiesRelation-HierarchyAssociation
uses protocol parameter (is protocol parameter of) – PP48 rdfs:subPropertyOf used specific object (was used for) – P16 2023-01-19 PropertiesRelation-HierarchyAssociation
had awarder (was awarder of) – PP53 rdfs:subPropertyOf carried out by (performed) – P14 2023-01-19 PropertiesRelation-HierarchyAssociation
had awardee (was awardee of) – PP54 rdfs:subPropertyOf carried out by (performed) – P14 2023-01-19 PropertiesRelation-HierarchyAssociation
awarded (was thing awarded by) – PP55 rdfs:subPropertyOf used specific object (was used for) – P16 2023-01-19 PropertiesRelation-HierarchyAssociation
awarded for (was award of) – PP56 rdfs:subPropertyOf was motivated by (motivated) – P17 2023-01-19 PropertiesRelation-HierarchyAssociation
is encoded with (is encoding of) – PP58 rdfs:subPropertyOf has type (is type of) – P2 2023-01-19 PropertiesRelation-HierarchyAssociation
had intended audience (was intended audience of) – PP59 rdfs:subPropertyOf had general purpose (was purpose of) – P21 2023-01-19 PropertiesRelation-HierarchyAssociation

Notes

Show Note Type Language Entity

Comments

List of mismatches with reference namespaces

Entities listed here are not correctly associated with your reference namespaces. They are displayed in red in your ongoing namespace. They may not be available in the version of the selected space. Or you may not have selected any version of a reference namespace.
Please make the necessary corrections before proceeding.

Type of relation Entity Namespace Error type