126
results
-
The General Data Protection Regulation (GDPR) is comprised of several articles, each with points that refer to specific concepts. The general convention of referring to these points and concepts is to quote the specific article or point using a human-readable reference. This ontology provides a way to refer to the points within the GDPR using the EurLex ontology published by the European Publication Office. It also defines the concepts defined, mentioned, and requried by the GDPR using the Simple Knowledge Organization System (SKOS) ontology. @en
-
GDPRov is an OWL2 ontology to express provenance metadata of consent and data lifecycles towards documenting compliance for GDPR. @en
-
AIRO represents AI risk concepts and relations based on the AI Act draft and ISO 31000 standard series. @en
-
The Denotative Description module encodes the characteristics of a cultural property, as detectable and/or detected during the cataloguing process and measurable according to a reference system. Examples include measurements e.g. length, constituting materials e.g. clay, employed techniques e.g. melting, conservation status e.g. good, decent, bad. In this module are used as template the following Ontology Design Patterns: - http://www.ontologydesignpatterns.org/cp/owl/collectionentity.owl - http://www.ontologydesignpatterns.org/cp/owl/classification.owl - http://www.ontologydesignpatterns.org/cp/owl/descriptionandsituation.owl - http://www.ontologydesignpatterns.org/cp/owl/situation.owl @en
-
The Core module represents general-purpose concepts orthogonal to the whole network, which are imported by all other ontology modules (e.g. part-whole relation, classification). @en
-
The Context Description module includes models for the context of a cultural property, in a broad sense: agents (e.g.: author, collector, copyright holder), objects (e.g.: inventories, bibliography, protective measures, other cultural properties, collections etc.), activities (e.g.: surveys, conservation interventions), situations (e.g.: commission, coin issuance, estimate, legal situation) related, involved or involving the cultural property. Thus it represents attributes that do not result from a measurement of features in a cultural property, but are associated with it. @en
-
Ontology for the orchestration of the aerOS continuum. @en
-
Simple ontology for Cloud Computing Services. This ontology allows to define model of prices used in large cloud computing providers such as Google, Amazon, Azure, etc., including options for regions, type of instances, prices specification, etc. @en
-
The scope of the DIO is the domain of design intent or design rationale that needs to be documented while undertaking the design of any artifact @en
-
The DINGO ontology (Data Integration for Grant Ontology) defines the terms of the DINGO vocabulary and provides a machine readable extensible framework to model data relative to projects, funding, project and funding actors, and, notably, funding policies. It is designed to yield high modeling power and elasticity to cope with the huge variety in funding and project practices, which makes it applicable to many areas where funding is an important aspect: first of all research, but also the arts, cultural conservation, and many others. @en
-
Extension to the Data Privacy Vocabulary (DPV) providing additional categories of personal data @en
-
The DNS Security Ontology (DSecO) project is a data model for representing and reasoning on Domain Name System (DNS) data. The ontology is developed using web technologies (e.g. RDF, OWL, SKOS) and is intended as a structure for realizing a DNS Knowledge Graph (KG) for administration and security assessment applications. The model has been developed in collaboration with operational teams, and in connection with third parties linked vocabularies. Alignment with third parties vocabularies is implemented on a per class or per property basis when relevant (e.g. with `rdfs:subClassOf`, `owl:equivalentClass`). Directions for direct instanciation of these vocabularies are provided for cases where implementing a class/property alignment is redundant. Alignment holds for the following vocabulary releases: - [ORG](https://www.w3.org/TR/vocab-org/) 0.8 - [UCO](https://github.com/ucoProject/uco) Release-0.8.0 @en
-
CTRLont specifies concepts and relationships of control actors on a high level @en
-
This ontology defines classes and properties for describing participants, infrastructure, data and services of the International Data Spaces (formerly known as Industrial Data Space). @en
-
This ontology provides the terms necessary to describe the status of traffic lights. @en