139
results
-
Lemon: The lexicon model for ontologies is designed to allow for descriptions of lexical information regarding ontological elements and other RDF resources. Lemon covers mapping of lexical decomposition, phrase structure, syntax, variation, morphology, and lexicon-ontology mapping. @en
-
An ontology for natural language terms description, including scripts, languages and meanings. The Lexvo.org ontology is still under development and may not be able to address all needs. Please also consider using the Lingvoj Ontology and the GOLD ontology, whereever appropriate. @en
-
The Linked SPARQL Queries Vocabulary (LSQ(V)), defined using RDF(S) and OWL, provides a machine readable vocabulary to help describe queries in SPARQL logs and their statistics. The vocabulary builds upon the SPIN vocabulary and the Service Description vocabulary. @en
-
This is (the start of) an event-based model of the W3C process; e.g. RECdd is the class of Recommendation Director's Decisions; i.e. messages to w3c-ac-members announcing a new W3C Recommendation. @en
-
An RDF vocabulary for relating SW vocabulary terms to their status. @en
-
OWL definition of the RDF Concrete Syntax for the Semantic Web Rule Language @en
-
Gleaning Resource Descriptions from Dialects of Languages Vocabulary @en
-
This ontology aims at defining the Quality Assurance Framework by collecting the test development experience of W3C Working Groups and summarizing the work done about tests and metadata. @en
-
ADMS is a profile of DCAT, used to describe semantic assets (or just 'Assets'), defined as highly reusable metadata (e.g. xml schemata, generic data models) and reference data (e.g. code lists, taxonomies, dictionaries, vocabularies) that are used for eGovernment system development. @en
-
Ontology for Certificates and crypto stuff. @en
-
This document describes the RDFS vocabulary description used in the Metadata Vocabulary for Tabular Data along with the default JSON-LD Context. @en
-
The Data Quality Vocabulary (DQV) is seen as an extension to DCAT to cover the quality of the data, how frequently is it updated, whether it accepts user corrections, persistence commitments etc. When used by publishers, this vocabulary will foster trust in the data amongst developers. @en
-
This vocabulary is for describing relationships between standards/specifications, profiles of them and supporting artifacts such as validating resources. This model starts with [http://dublincore.org/2012/06/14/dcterms#Standard](dct:Standard) entities which can either be Base Specifications (a standard not profiling any other Standard) or Profiles (Standards which do profile others). Base Specifications or Profiles can have Resource Descriptors associated with them that defines implementing rules for the it. Resource Descriptors must indicate the role they play (to guide, to validate etc.) and the formalism they adhere to (dct:format) to allow for content negotiation. A vocabulary of Resource Roles are provided alongside this vocabulary but that list is extensible. @en
-
EARL is a vocabulary, the terms of which are defined across a set of specifications and technical notes, and that is used to describe test results. The primary motivation for developing this vocabulary is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor-neutral and platform-independent format. It also provides reusable terms for generic quality assurance and validation purposes. @en
-
The Open Annotation Core Data Model specifies an interoperable framework for creating associations between related resources, annotations, using a methodology that conforms to the Architecture of the World Wide Web. This ontology is a non-normative OWL formalization of the textual OA specification at http://www.openannotation.org/spec/core/20130208/index.html @en