96
results
  • attack - MITRE ATT&CK Ontology
    http://w3id.org/sepses/vocab/ref/attack
    An ontology to represent MITRE ATT & CK. This ontology is developed based on the MITRE ATT & CK (https://attack.mitre.org/) @en
  • arp - Arpenteur Ontology
    http://www.arpenteur.org/ontology/Arpenteur.owl
    Arpenteur ontology is dedicated to photogrammetry, archeology and oceanology communities in order to perform tasks such as image processing, photogrammetry and modelling. @en
  • coun - ISO 3166 Country Codes
    http://www.daml.org/2001/09/countries/iso-3166-ont
    Basic properties of a country as defined by ISO 3166 (code and name) @en
  • bbcprov - BBC Provenance Ontology
    http://www.bbc.co.uk/ontologies/provenance
    The provenance ontology supports data management and auditing tasks. It is used to define the different types of named graphs we used in the store (quad store) and enables their association with metadata that allow us to manage, validate and expose data to BBC services @en
  • gn - The Geonames ontology
    http://www.geonames.org/ontology
    The Geonames ontology provides elements of description for geographical features defined in the geonames.org data base @en
  • identity - Ontology of digital identity.
    http://www.identity.org/ontologies/identity.owl
    v.2.0 based on P3P1.0 Specification http://www.w3.org/TR/P3P/ @en
  • geof - Geo Features
    http://www.mindswap.org/2003/owl/geo/geoFeatures20040307.owl
    This ontology contains geographic feature classes and associated properties including classes and properties for describing the spatial location of the geographic feature. The classes and properties have been defined based on an ESRI dataset. @en
  • irw - The Identity of Resources on the Web ontology
    http://www.ontologydesignpatterns.org/ont/web/irw.owl
    This ontology is an evolution of IRE ontology. It describes identification of resources on the Web, through the definition of relationships between resources and their representations on the Web. The requirement is to describe what can be identified by URIs and how this is handled e.g. in form of HTTP requests and reponds. @en
  • ostop - Ordnance Survey Topography Ontology
    http://www.ordnancesurvey.co.uk/ontology/Topography/v0.1/Topography.owl
    The general purpose of this ontology is to provide a library of high level concepts that are used by the other modules within the whole OS Topographic ontology. The ontology also describes the relationships and instances common to more than one module. @en
  • ct - Connectivity types
    http://www.tele.pw.edu.pl/~sims-onto/ConnectivityType.owl
    Defines types of connectivity used in communication and bearer services accessible in certain connectivity. @en
  • ontosec - Ontology Security
    http://www.semanticweb.org/ontologies/2008/11/OntologySecurity.owl
    This ontology covers the domain of security in the field of mobile applications. @en
  • test - Test Metadata
    http://www.w3.org/2006/03/test-description
    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
  • geo - WGS84 Geo Positioning
    http://www.w3.org/2003/01/geo/wgs84_pos
    A vocabulary for representing latitude, longitude and altitude information in the WGS84 geodetic reference datum. @en
  • earl - Evaluation and Report Language
    http://www.w3.org/ns/earl
    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
  • dqv - Data Quality Vocabulary
    http://www.w3.org/ns/dqv
    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