74
results
-
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
-
Information about authentication providers which might be identity providers or other services such as ones providing JSON Web Tokens. @en
-
The NORIA-O project is a data model for IT networks, events and operations information. The ontology is developed using web technologies (e.g. RDF, OWL, SKOS) and is intended as a structure for realizing an IT Service Management (ITSM) Knowledge Graph (KG) for Anomaly Detection (AD) and Risk Management 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: - [BBO](https://hal.archives-ouvertes.fr/hal-02365012/) 1.0.0 - [BOT](https://w3id.org/bot/) 0.3.2 - [DevOps-Infra](https://oeg-upm.github.io/devops-infra/) 1.0.0 - [FOLIO](https://github.com/IBCNServices/Folio-Ontology) 1.0.0 - [ORG](https://www.w3.org/TR/vocab-org/) 0.8 - [PEP](https://w3id.org/pep/) 1.1 - [SEAS](https://w3id.org/seas/) 1.1 - [SLOGERT](https://sepses.ifs.tuwien.ac.at/ns/log/index-en.html) 1.1.0 - [UCO](https://github.com/ucoProject/uco) Release-0.8.0 @en
-
This ontology defines feature of interest and their properties, as an extension of the core classes of the SSN ontology (https://www.w3.org/ns/ssn/). A feature of interest is an abstraction of a real world phenomena (thing, person, event, etc). A feature of interest is then defined in terms of its properties, which are qualifiable, quantifiable, observable or operable qualities of the feature of interest. Alignments to other ontologies are proposed in external documents: - [SSNAlignment](https://w3id.org/seas/SSNAlignment) proposes an alignment to the [SSN ontology](http://www.w3.org/ns/ssn/). - [QUDTAlignment](https://w3id.org/seas/QUDTAlignment) proposes an alignment to the [QUDT ontology](http://qudt.org/). @en
-
## RDF Presentation and RDF Presentation Negotiation An RDF graph can be presented in several ways, using different media types. Examples of RDF media types include `application/rdf+xml`, `text/turtle`, `application/json+ld`. Today, most of the content consumed/produced/published, on the Web is not presented in RDF. In the Web of Things, HTTP servers and clients would rather exchange lightweight documents, potentially binary. Currently, most existing RDF Presentations generically apply to any RDF graph, at the cost of being heavy text-based documents. Yet, lightweight HTTP servers/clients could be better satisfied with consuming/producing/publishing lightweight documents, may its structure be application-specific. @en
-
An ontology to model accountability of generic systems. @en
-
An ontology to model accountability of AI systems which use machine learning. @en
-
The Procedural Knowledge Ontology (PKO) addresses the Procedural Knowledge (PK) domain, and models procedures, their executions, and related resources and agents. @en
-
RDF-STaX is an OWL 2 DL ontology that enables describing the types of RDF streams and defines relations between them. @en
-
The vocabulary allows for the description of data about scientific events such as conferences, symposiums and workshops. @en
-
Ontology 'Usability' created to describe and store information about interactions of user with a software user interface @en
-
Ontology for representing exceptions to reporting of parents, for entities registered with a Legal Entity Identifier. The Global Legal Identifier System (GLEIS) requires that legal entities with an LEI provide information on their ultimate and direct accounting consolidating parents. Relationship reporting is mandatory with exceptions allowed for certain well-defined reasons. This ontology provides a simple structure for recording reasons for each exception by LEI. @en
-
Ontology that defines core concepts for representing YANG servers, including connection details and the available YANG datastores, along with operations for retrieving YANG data from a YANG server. The goal of this ontology is to enable the declarative and abstract of the interactions with YANG servers for monitoring and configuration purposes. In this sense, the ontology can become the basis for building a knowledge graph from YANG data obtained from YANG servers. @en
-
This ontology is for use in describing Workspaces. Workspaces are places where data is stored and associated policies of privacy. A given application typically stores information in several different workspaces, some being user private, some shared, and some public. it is crucial that the user has easy control over the destiny of information. @en