Data Portal @ linkeddatafragments.org

Matches in LOV for { ?s <http://purl.org/dc/terms/description> ?o. }

• terms description "This ontology is a translation of the General Transit Feed Specification towards URIs. Its intended use is creating an exchange platform where the Linked GTFS model can be used as a start to get the right data into the right format.".
• geo-deling description "Dette er et vokabular for administrativ inndeling av Norge, matrikkelen, steder og andre geografiske ting.".
• geo-deling description "Dette er et vokabular for administrativ inndeling av Norge, matrikkelen, steder og andre geografiske ting.".
• geo-deling description "Vocabulary describing the administrative subdivision of Norway".
• terms description "<div>\n <p>The TRANSIT schema is based on the General Transit Feed Specification published by Google.</p>\n <p><figure><img src=\"/transit/core-classes.png\"></img><br></br>Figure: Transit Vocabulary Core Classes (<a href=\"http://vocab.org/transit/core-classes.png\">PNG version</a>, <a href=\"http://vocab.org/transit/core-classes.svg\">SVG version</a>)</figure></p>\n <p>Please see <a href=\"https://github.com/iand/vocab-transit\">https://github.com/iand/vocab-transit</a> for the master version of this vocabulary.</p>\n </div>".
• terms description "A vocabulary for describing transit systems and routes".
• terms description "A small vocabulary for describing whisky varieties".
• communication description "This vocabulary is intended to describe all the aspects which are needed to communicate incident related information for fire department services".
• communication description "This vocabulary is intended to describe all the aspects which are needed to communicate incident related information for fire department services".
• vrank description "The Vocabulary for Ranking (vRank) is an RDF Schema vocabulary for materializing ranking computations.".
• vrank description "The Vocabulary for Ranking (vRank) is an RDF Schema vocabulary for materializing ranking computations.".
• terms description "The AGLS Metadata Terms Namespace provides URIs for the AGLS Metadata Terms Vocabulary in the context of AGLS Metadata Standard, a set of metadata properties and associated usage guidelines to improve the visibility, manageability and interoperability of online information and services. Vocabulary terms are declared using RDF Schema language to support RDF applications. It will be updated according to AGLS Working Group decisions.".
• terms description "The AGLS Metadata Terms Namespace provides URIs for the AGLS Metadata Terms Vocabulary. Vocabulary terms are declared using RDF Schema language to support RDF applications. The AGLS Metadata Terms form a richer vocabulary, which is intended to facilitate discovery of resources. It will be updated according to AGLS Working Group decisions.".
• portal description "The AKT Reference Ontology has been designed to support the AKT-2 demonstrator (\"AKTive Portal\"), and subsequent activities. The ontology, designed by the AKT-2 group and codified by Enrico Motta, extends Version 1.".
• support description "The AKT Reference Ontology has been designed to support the AKT-2 demonstrator (\"AKTive Portal\"), and subsequent activities".
• bbc description "The BBC ontology is used to describe BBC concepts in the store. For example, the BBC divisions (products) publishing linked data and interfacing with the triplestore, the platforms for which we produce content and the web documents that publish or are relevant to the BBC's content.".
• cms description "An ontology to represent the content management systems and their interaction with the triplestore.".
• coreconcepts description "The generic BBC ontology for people, places,events, organisations, themes which represent things that make sense across the BBC. This model is meant to be generic enough, and allow clients (domain experts) link their own concepts".
• creativework description "This ontology defines the terms required to describe the creative works produced by the BBC and their associated metadata.".
• provenance description "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".
• sport description "A simple ontology for representing competitive sports events.".
• biopax-level3.owl description "The goal of the BioPAX group is to develop a common exchange format for biological pathway data. More information is available at http://www.biopax.org. This ontology is freely available under the LGPL license".
• blterms description "Some useful terms for describing bibliographic resources that other models did not include. Version 1.4: brings the description for this schema in line with \"Metadata recommendations for Linked Open Vocabulairies\", version 1.1.; dct:license replaced by cc:license and the value changed from http://www.opendatacommons.org/licenses/pddl/1.0/ to http://creativecommons.org/publicdomain/mark/1.0/; various typos corrected. Version 1.4.1: added links to previous schema versions".
• blterms description "This schema describes properties and classes defined to facilitate the description of bibliographic resources and their relationships to other entities. The properties and classes defined by this schema supplement properties and classes from other ontologies. A diagram of the full model as used by the British Library is available at: http://www.bl.uk/bibliographic/datafree.html".
• cidoc-crm description "This is the encoding approved by CRM-SIG in the meeting 21/11/2012 as the official current version for the CIDOC CRM namespace. Note that this is NOT a definition of the CIDOC CRM, but an encoding derived from the authoritative release of the CIDOC CRM v5.0.4 on http://www.cidoc-crm.org/official_release_cidoc.html".
• iso-3166-ont description "Basic properties of a country as defined by ISO 3166 (code and name)".
• demlab.owl description "The ontology has been developed in the framework of the Dem@Care project for representing the experimentation protocol towards diagnostic support and assessment of Dementia in a controlled environment. The aim of the protocol is to provide a brief overview of their health status of the participants during consultation (cognition, behaviours and function), and to correlate the system (sensor) data with the data collected using typical dementia care assessment tools.".
• ebucore description "Combined with the EBU Class Conceptual Data Model (CCDM) of simple business objects, EBUCore provides the appropriate framework for descriptive and technical metadata for use in Service Oriented Architectures and also in audiovisual ontologies for semantic web and linked data developments.".
• ebucore description "The EBUCore has been\n designed to make users benefit from the flexibility of RDF to adapt the names of Classes and\r\n properties to their respective needs. This means users are welcome to add their own subclasses\r\n (e.g. to define the most appropriate BusinessObjects or Resources or Agents) and subproperties.".
• ebucore description "The EBUCore ontology now includes the new EBUCore 3D object audio model (ADM).".
• v1 description "An Ontology for Consumer Electronics Products and Services".
• eclap description "The ECLAP vocabulary provide classes and properties for the description of multimedia content related with performing arts.".
• pattern description "An ontology defining formally patterns for segmenting a document into atomic components, in order to be manipulated independently and re-flowed in different contexts.".
• tvc description "A pattern for the description of scenarios that involve entities having some value during a particular time and within a particular context.".
• cito-functions description "CiTOFunctions is an ontology that provides a classification for citations. In particular, it classifies CiTO properties (each defining a particular citational act)".
• vagueness description "The Vagueness Ontology (VO) allows one to specify vagueness characterisations of the TBox entities of an ontology.".
• edm description "The Europeana Data Model (EDM) is aimed at being an integration medium for collecting, connecting and enriching the descriptions provided by Europeana data providers.".
• ontology description "The Geonames ontologies provides elements of description for geographical features, in particular those defined in the geonames.org data base".
• ontology description "The Geonames ontology provides elements of description for geographical features defined in the geonames.org data base".
• ns description "Marl is a standardised data schema designed to annotate and describe subjective opinions expressed on the web or in particular Information Systems.".
• ns description "Marl is an ontology designed to use for publishing the results of the opinion mining process in a form of structured data on the Web. The goal is to unify the access the numerical approximation of the opinion concept and allow extensive reasoning and search over multiple resources from different content providers.".
• ns description "Onyx is a vovabulary designed designed to annotate and describe the emotions expressed by user-generated content on the web or in particular Information Systems.".
• ns description "Onyx is an ontology designed to use for publishing the results of the emotion mining process in a form of structured data on the Web. The goal is to unify the access the numerical approximation of the emotion concept and allow extensive reasoning and search over multiple resources from different content providers.".
• tags description "An ontology that let users define relationships between Tag objects and URIs of Semantic Web resources".
• marinetlo.owl description "MarineTLO is a top-level ontology for the marine domain (also applicable to the terrestrial domain).".
• marinetlo.owl description "MarineTLO is a top-level ontology for the marine domain (also applicable to the terrestrial domain).".
• VoID_Extension_Schema.owl description "An extension of W3C VoID that is able to represent these metrics for expressing the Connectivity Metrics of a Semantic Warehouse.".
• VoID_Extension_Schema.owl description "An extension of W3C VoID that is able to represent these metrics for expressing the Connectivity Metrics of a Semantic Warehouse.".
• music description "A vocabulary, or music ontology, to describe classical music and performances. Classes (categories) for musical works, events, instruments and performers, as well as related properties are defined. Make sure to distinguish musical works (e.g. Opera) from performance events (Opera_Event), or works (String_Quartette) from performer (StringQuartetEnsemble in this vocab), whose natural language terms are used interchangeblly. The present version experiments more precise model to describe a musical work, its representations (performances, scores, etc) and a musical event to present a representation (a concert). Includes 30 keys as individuals.".
• music description "音楽作品、楽器、演奏情報を記述するためのボキャブラリ。Opera_Event（演奏）とOpera（作品）や、String_Quartette（作品）とStringQuartetEnsemble（団体）のように、日常語では両方の意味に使われるクラスの区別に注意。このバージョンでは、音楽作品、その表現（演奏、楽譜など）とイベント（演奏会）をより精密にモデリングするべく実験中。".
• whois description "A vocabulary to describe a person's profile and history".
• lmf description "Specification of Lexical Markup Framework (ISO 24613 rev 14)".
• lexinfo description "An ontology of types, values and properties to be used with the lemon model, partially derived from ISOcat.".
• lexinfo description "Version 2.0 of LexInfo Ontology, based on Lemon".
• olca description "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".
• ontology description "An ontology for using languages as resources".
• semio.rdf description "A vocabulary to describe signs in a semiotic approach".
• semio.rdf description "An ontology of signs".
• dtype description "The ontology 'dtype' provides a specification of simple data types such as enumerations. These are needed in support of the conversion of XML Schemas and UML Models to OWL. Codelists are also defined in 'dtype'.".
• vaem description "The purpose of VAEM is to provide, by import, a foundation for commonly needed resources when building an ontology.".
• Aspect description "Aspect is used to distinguish among sets of features of a domain or subject area. The term is borrowed from \"aspect-oriented\" programming, where it is used to separate concerns. An ontology may be characterized by this dimension so as to parition features that are orthogonal. For example, in a systems ontology there may be aspects for \"structure\", \"function\", \"behavior\" and \"interface\" or \"interoperability\". A viewpoint can be distinguished by \"aspects\". For example the \"information viewpoint\" of an application can be partitioned into separate graphs for the \"security\", \"operational\" and\"data retention\" aspects.".
• CatalogEntry description "VAEM Governed Object class is a placeholder for concepts that are fully defined by the voag:GovernedObject concept hierarchy for building a catalog of ontologies and graphs".
• Dimension description "A dimension identifies a separation of concens that serves as a way to categorize an ontology graph. In VAEM, the notion of \"Dimension\" is partitioned into \"Aspect\", \"Discipline\", \"Domain\" and \"Viewpoint\".".
• Discipline description "A discipline is a specific area of work or study. Examples of disciplines in the engineering domain are electrical engineering, mechanical engineering and, in the financial domain, risk assessment, investment analysis. In VAEM, discipline is used as a dimension for characterizing an ontology graph".
• Domain description "A domain is a subject area of interest. Examples of domains are \"enterprise\", \"process\", \"organization\" and \"system\". In VAEM, \"Domain\" is used as a dimension for characterizing an ontology graph".
• GraphMetaData description "\"vaem:GraphMetaData\" defines basic metadata for the registration and publishing of a graph. For specificaiton of governance the vocabulary \"VOAG\" may be used.".
• GraphRole description "GraphRole is used to characterize how a graph of resources participates in an ontology set. For example, a graph can be a schema, vocabulary, dataset, script, or ruleset".
• Party description "A \"Party\" is a generalization for an actor that may be realized as a person, organizaiton or named role.".
• Viewpoint description "Viewpoint is used to denote how a set of resources, or an individual resource, is relevant to a context of use. The term \"viewpoint\" is adopted from the ISO RM-ODP specifications and its more recent use in enterprise architecture descriptions. The RM-ODP introducesd the concept of viewpoint to describe a system from a particular set of concerns. RM-ODP defines five viewpoints. Together they provide a complete description of a system: enterprise viewpoint, information viewpoint, computational viewpoint, engineering viewpoint, and technology viewpoint. In VAEM, \"Viewpoint\" is used as a dimension for characterizing an ontology graph. The viewpoints of an ontology may not always correpsond directly to those of a system but the idea of describing a subject area of interest from distinct viewpoints is still relevant. A viewpoint can be further distinguished by \"aspects\". For example the \"information viewpoint\" of an application can be partitioned into separate graphs for the \"security\", \"operational\" and\"data retention\" aspects.".
• VocabularyGraph description "An RDF/OWL Graph that is a controlled set of instances.".
• acronym description "The property \"vaem:acronym\" provides a common way to define a commonly used abbreviation on a resource".
• date description "The property \"vaem:date\" is intended for general use as the name implies. The range of the property is set as \"vaem:dateUnion\" so as to allow a value to have a number of forms from a year only to a full timestamp. The property is also the parent of all dates so that queries can be made for any date on an ontology".
• dateCreated description "The property \"vaem:dateCreated\" is intended for general use as the name implies. The range of the property is set as \"vaem:dateUnion\" so as to allow a value to have a number of forms from a year only to a full timestamp".
• filePrefix description "The property \"vaem:filePrefix\" is for specifying a preferred file prefix for a graph. For example a schema graph may be given the file prefix \"SCHEMA\" followed by an underscore \"_\".".
• hasAspect description "The property \"vaem:hasAspect\" is used to distinguish among sets of features of a domain or subject area. The term is borrowed from \"aspect-oriented\" programming, where it is used to separate concerns. An ontology may be characterized by this dimension so as to parition features that are orthogonal. For example, in a systems ontology we can distinguish aspects for \"structure\", \"function\", \"behavior\" and \"interface\". The property is an \"rdf:Property\" to allow both scalar and object values".
• hasDimension description "The property \"vaem:hasDimension\" is used categorize an ontology. In VAEM, the property is used to characterize an ontology graph.".
• hasDiscipline description "The property \"vaem:hasDiscipline\" is used to indicate relevance of a set of resources, or a resource itself, to a specific discipline of work or study. Examples of disciplines in the engineering domain are electrical engineering, mechanical engineering and, in the financial domain, risk assessment, investment analysis. In VAEM, the property is used as a dimension for characterizing an ontology graph. The property is an \"rdf:Property\" to allow both scalar and object values".
• hasDomain description "The property \"vaem:hasDomain\" is used to specify how a set of resources, or an individual resource is grounded in a domain, that is, a subject area of interest. Examples of domains are \"enterprise\", \"process\", \"organization\" and \"system\". In VAEM, the property is used as a dimension for characterizing an ontology graph. The property is an \"rdf:Property\" to allow both scalar and object values".
• hasGraphRole description "The property \"lms:hasGraphRole\" is used to characterize how a resource participates in an ontology set. The property is used to specify the role that a graph plays, for example, an ontology graph can be a schema, vocabulary, dataset, script, or ruleset".
• hasIdentifier description "The property \"vaemhasIdentifier\" is intended for general use as a means to specifiy a unique reference to something. This is an object property that is a sub-property of \"vame:id\"".
• hasLicenseType description "The property \"vaem:hasLicenseType\" points to an entry in the VOAG ontology for licenses".
• hasMetadata description "The property \"hasMetadata\" is used to reference a metadata information structure.".
• hasSteward description "A property that is used to refer to a \"Steward\", that is, the party or role that is responsible for maintaining an asset, in the case of VAEM, an ontology graph.".
• hasViewpoint description "The property \"vaem:hasViewpoint\" is used to denote how a set of resources, or an individual resource, is relevant to a context of use. The term \"viewpoint\" is adopted from the ISO RM-ODP specifications and its more recent use in enterprise architecture descriptions. In VAEM, the property is used as a dimension for characterizing an ontology graph. The property is an \"rdf:Property\" to allow both scalar and object values".
• id description "The property \"vaem:id\" is intended for general use as a means to specifiy an identifier. The type of this property is intentionally set to \"rdf:Property\" so that use of the property can allow both object and scaler values. For this reason, the property is rangeless".
• intent description "The property \"vaem:intent\" is used to outline a statement of purpose. This typically expresses one or more desired outcomes".
• lastUpdated description "The property \"vaem:lastUpdated\" is intended for general use as the name implies. The range of the property is set as \"vaem:dateUnion\" so as to allow a value to have a number of forms from a year only to a full timestamp".
• latestPublishedVersion description "The property \"vaem:latestPublishedVersion\"is a URL to documentation for the latest version of a graph.".
• name description "The property \"vaem:name\" is intended for general use. In many cases \"rdfs:label\" could be used give names to resources. In the case where compliance with a specific naming rule is needed, \"vaem:name\" allows a resource to carry a name that is used in more specific contexts.".
• namespace description "The property \"vaem:namespace\" is the onotlogy URI with which a graph is primarily associated. The intent is to allow multiple graphs to define statements for resources in the same Ontology namespace. For example, a foundation level graph with the base URI of \"http://www.somesite.com/1.0/schema/OurOntology\" may define general concepts for \"OurOntology\". Another graph with the base URI \"http://www.somesite.com/1.0/schema/level2/OurOntology\" may add more specific details to the same \"OurOntology\". Each of these two graphs would carry the same value for \"vaem:namespace\", that is, \"http://www.somesite.com/schema/OurOntology\". In other words, an ontology URI is the URI associated with the resources of a controlled namespace. On the other hand the graph URIs (the base URIs) identify the graphs that hold resources that make up an ontology".
• namespacePrefix description "The property \"vaem:namespacePrefix\" specifes a short handle or label for the URI of an Ontology. Multiple graphs can define statements for resources in the same Ontololgy namespace. For example, a foundation level graph with the base URI of \"http://www.somesite.com/1.0/schema/OurOntology\" may define general concepts for \"OurOntology\". Another graph with the base URI \"http://www.somesite.com/1.0/schema/level2/OurOntology\" may add more specific details to the same \"OurOntology\". Each of these two graphs would carry the same value for \"vaem:namespacePrefix\", for this example, perhaps, \"ourOntology\"".
• previousPublishedVersion description "The property \"vaem:previousPublishedVersion\"is a URL to documentation for the previous version of a graph.".
• rdfxmlFileURL description "The property \"vaem:rdfxmlFileURL\" is used to provide a link to the location of the ontology's RDF/XML file".
• revision description "The property \"vaem:revision\" is a property intended for general use as the name implies.".
• specificity description "The property \"vaem:specificity\" is intended to specify the level of detail of an ontology. The values that can be set for this property are restriced to an integer from 1 to 5. An ontology at level 1 has concepts of more general applicability than one at level 5. By having graphs at different levels of specificity it is possible to support greater modularity for selective imports".
• turtleFileURL description "The property \"vaem:turtleFileURL\" is used to provide a link to the location of the ontology's turtle file".
• url description "The property \"vaem:url\" is intended for general use as the name implies. The range of the property is set as an XSD URI".
• withAttributionTo description "The property \"vaem:withAttributionTo\" is an annotation property that is either used to hold either a string or a reference to an instance of \"voag:Attribution\", from the VOAG ontology".
• v1 description "MADS/RDF (Metadata Authority Description Schema in RDF) is a knowledge organization system (KOS) designed for use with controlled values for names (personal, corporate, geographic, etc.), thesauri, taxonomies, subject heading systems, and other controlled value lists".
• v1 description "This ontology identifies the classes and properties used to describe preservation metadata in RDF.".

• first
• previous
• next