135
results
  • The Ishikawa ontology aims to provide a data and view model to manage data encoded in Ishikawa diagrams which are also known as fishbone or cause and effect diagram (CED). Ishikawa diagrams result from (iterative) workshops. Thus, the ontology includes the basic modelling of workshops to create Ishikawa diagrams. @en
  • The Level of Information Need (LOIN) Ontology is defined for specifying information requirements for delivery of data in a buildings' life cycle. The LOIN ontology is based on the standard BS EN 17412-1 (2020). Furthermore, it is extended with vocabulary for connecing Information Delivery Specifications (IDS) and Information containers for linked document delivery (ICDD) as per ISO 21597-1 (2020). @en
  • This is the Neural Network Ontology. Designed by the AIFB (http://www.aifb.kit.edu/web/Web_Science) @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
  • An ontology for describing software and their links to inputs, outputs and variables. The ontology extends schema.org and codemeta vocabularies @en
  • A reference implementation of the OntoUML metamodel in OWL. @en
  • Used for indexing, searching and comparing Open Source Hardware projects @en
  • The process execution ontology is a proposal for a simple extension of both the [W3C Semantic Sensor Network](https://www.w3.org/TR/vocab-ssn/) and the [Semantic Actuator Network](https://www.irit.fr/recherches/MELODI/ontologies/SAN.owl) ontology cores. @en
  • The Procedural Knowledge Ontology (PKO) addresses the Procedural Knowledge (PK) domain, and models procedures, their executions, and related resources and agents. @en
  • An ontology to model accountability of AI systems which use machine learning. @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
  • The Evaluation ontology describes evaluation of [`seas:Property`ies](https://w3id.org/seas/Property). There may be: - direct evaluations, or - qualified evaluations. @en
  • This ontology defines common evaluation interpretation concepts for statistics. @en
  • An ontology to describe a Semantic-Web Machine Learning System (SWeMLS) @en