156
results
-
This is the provenance module of Materials Design Ontology. @en
-
INTRO is an ontology for the fields of literary studies, art studies and intermediality studies for the representation of intertextual, interpictorial, and intermedial relations. It enables the presentation and categorization of diverse features of both textual and pictorial origin and their linking. Its subject area includes the scholarly discourse on these texts/images, interrelations, and features, insofar as research results are also understood as texts with features and relations. @en
-
Metadata for Ontology Description and publication @en
-
The ISO Property (ISOProps) ontology maps the data model of the ISO 23386 for the describing, creating, and maintenance of properties in interconnected data dictionaries. The namespace for ISOProps terms is [https://w3id.org/isoprops](https://w3id.org/isoprops) The preferred prefix for the ISOProps namespace is `isoprops`. ## Ontology Overview  ## Assigning an ISOProps Property to a Feature of Interest  ## Relation between DCAT vocabulary and the ISOProps ontology  @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
-
An ontology for metadata about legal texts represented using the LegalHTML format @en
-
A reference implementation of the OntoUML metamodel in OWL. @en
-
An ontology for describing software and their links to inputs, outputs and variables. The ontology extends schema.org and codemeta vocabularies @en
-
Specification of the metadata used to describe models in the OntoUML/UFO Catalog. @en
-
Patient Generated Health Data (PGHD) refer to health data collected by patient or their relatives. This ontology seeks to capture information about the data, the provenance and data quality associated with PGHD shared with an EHR. @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
-
Ontology with metadata needed to generate documentation of datasets, distributions, profiles, etc. in RiverBench @en
-
Ontology for describing datasets and profiles in the RiverBench benchmark suite. @en
-
OWL 2 ontology modeling the 3GPP RAN standardization document lifecycle (Tdoc, Resolution, CR, LS, Section, Spec, TechnicalReport, TRImpact, Meeting, Company, WorkingGroup). Designed from RAN1 competency questions and validated by cross-WG instantiation against RAN2-RAN5 with no additional process-layer classes required. Also declares six entity-layer classes (RRCParameter, CapabilityItem, Feature, Procedure, PerformanceRequirement, ConformanceTest) modeling spec-body entities: ASN.1 IEs, UE capability items, named standardization features, protocol procedures, performance requirements, and conformance test specifications. @en
-
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