111
results
-
sw-quality - SQuAP Ontology https://w3id.org/squap/ Quality, architecture, and process are considered the keystones of software engineering. ISO defines them in three separate standards. However, their interaction has been poorly studied, so far. The SQuAP model (Software Quality, Architecture, Process) describes twenty-eight main factors that impact on software quality in banking systems, and each factor is described as a relation among some characteristics from the three ISO standards. Hence, SQuAP makes such relations emerge rigorously, although informally. SQaAP-Ont is an OWL ontology that formalises those relations in order to represent and reason via Linked Data about software engineering in a three-dimensional model consisting of quality, architecture, and process characteristics. @en -
sri - Smart Readiness Indicator Vocabulary https://w3id.org/sri A vocabulary specifying concepts and structures needed to represent different data cubes needed for the Smart Readiness Indicator. @en -
seo - The Scientific Events Ontology https://w3id.org/seo The vocabulary allows for the description of data about scientific events such as conferences, symposiums and workshops. @en -
usability - Usability https://w3id.org/usability Ontology 'Usability' created to describe and store information about interactions of user with a software user interface @en -
vair - Vocabulary of AI Risks https://w3id.org/vair VAIR is a taxonomy of AI and risk concepts. @en -
gleif-repex - Global Legal Entity Identifier Foundation Reporting Exception Ontology https://www.gleif.org/ontology/ReportingException/ 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