142
results
-
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
-
A vocabulary specifying concepts and structures needed to represent different data cubes needed for the Smart Readiness Indicator. @en
-
An ontology to describe a Semantic-Web Machine Learning System (SWeMLS) @en
-
A vocabulary defining annotations enabling loose coupling between classes and properties in ontologies. Those annotations define with some accuracy the expected use of properties, in particular across vocabularies, without the formal constraints entailed by the use of OWL or RDFS constructions @en
-
A small vocabulary for representing SPARQL endpoint metadata on the web @en
-
An ontology for using languages as resources @en