Matches in LOV for { ?s <http://purl.org/dc/elements/1.1/description> ?o. }
- B4fc6c4bdd6f4a2226a66b468137b93fd description "If you change this, you have to tell the W3C SemWeb AD\n folk, including Dan Connolly; so agreed 5 Jun 2001.\n TimBl takes this as being met by a mail to sw-team.".
- Ba339557babbd897a90033085179119ad description "One thing to figure out is whether or not this tells us what we want; that is, does this imply that we must have at least one property of humanCreator, which could be either hasAuthor or hasEditor?".
- Beb18fa47fcc673c7cf62e0194878edac description "One thing to figure out is whether or not this tells us what we want; that is, does this imply that we must have at least one property of humanCreator, which could be either hasAuthor or hasEditor?".
- ns description "Common Tag RDF vocabulary, described using W3C RDF Schema. Common Tags allows documents and document fragments (any resource which can be identified by a URI) to be labeled with keywords and URIs, unambigiously idenfying the concepts covered by the resource.".
- expression description "OntoMedia (Ontology for Media) has been designed to describe the interactions occurring in multimedia.".
- space description "The OntoMedia Space representation denotes areas of landscape. Expands on the AKT location ontology".
- being description "OntoMedia (Ontology for Media) has been designed to describe the interactions occurring in multimedia.".
- trait description "OntoMedia (Ontology for Media) has been designed to describe the traits of entities.".
- date description "OntoMedia (Ontology for Media) Date Component has been designed to describe the different ways of marking time in media.".
- courseware description "The ReSIST Courseware Ontology represents the various eduacational courses and resources within the ReSIST project".
- 50kGazetteer description "An ontology describing the 50K Gazetteer.".
- spatialrelations description "An ontology describing basic spatial relations.".
- ocd description "L'ontologia Camera dei deputati è stata creata per descrivere tutte le risorse (persone, eventi, documenti) sia storiche che correnti, connesse alla Camera e alla sua attività".
- basic description "An OWL representation of (some of) the basic types described in ISO 19103:2005, required as primitives in other ontologies based on ISO 19100 series standards. ".
- geometry description "An OWL representation of part of the model for geometry and space from ISO 19107:2003 Geographic Information - Spatial Schema".
- temporal description "An OWL representation of part of the model for Temporal objects and reference systems from ISO 19108:2002 Geographic Information - Temporal Schema".
- feature description "An OWL representation of part of the General Feature Model described in ISO 19109 and the General Feature Instance model described in Annex C of ISO 19156:2011".
- dataquality description "An OWL representation of parts of the Geographic Metadata model described in ISO 19115:2003 with Corrigendum 2006 - DQ Package".
- extent description " An OWL representation of parts of the Geographic Metadata model described in ISO 19115:2003 with Corrigendum 2006 - EX Package".
- lineage description "An OWL representation of parts of the Geographic Metadata model described in ISO 19115:2003 with Corrigendum 2006 - LI Package".
- metadata description "An OWL representation of parts of the Geographic Metadata model described in ISO 19115:2003 with Corrigendum 2006 - MD Package".
- basic description "This ontology establishes classes corresponding to stereotypes used in ISO-conformant models, as used in the rules for conversion of the ISO TC 211 Harmonized Model from the UML to OWL representations".
- observation description "An OWL representation of the Observation Schema described in clause 6 of ISO 19156:2011 Geographic Information - Observations and Measurements".
- sampling description "An OWL representation of the Sampling Features Schema described in clauses 8-10 of ISO 19156:2011 Geographic Information - Observations and Measurements".
- op description "A general purpose ontology for observable properties. The ontology supports description of both qualitative and quantitative properties. The allowed scale or units of measure may be specified. A property may be linked to substances-or-taxa and to features or realms, if they play a role in the definition. ".
- oad description "An ontology for the description of archival data (OAD, “Ontology of Archival Description”) using the Web Ontology Language (OWL). This ontology represents the classes and properties needed to expose the archival resources as linked data.".
- custody description "Le classi production e custody sono state inserite per descrivere il rapporto tra una risorsa archivistica e una entità (CPF), volendo esplicitare anche le date di relazione verso un soggetto produttore o un conservatore, gestendo in questo modo ad esempio anche i cambi di custodia".
- production description "Le classi production e custody sono state inserite per descrivere il rapporto tra una risorsa archivistica e una entità (CPF), volendo esplicitare anche le date di relazione verso un soggetto produttore o un conservatore, gestendo in questo modo ad esempio anche i cambi di custodia".
- triple-access-control description "TripleAccessControl extension for WebAccessControl".
- voc description "NiceTag Ontology is an ontology which describes as generally as possible tags or rather tag actions understood as a speech acts occurring on the Web".
- voc description "NiceTag es una ontología que describe de la manera mas general posible las etiquetas, o mejor las acciones de etiquetado, como actos de habla en la Web".
- voc description "NiceTag est une ontologie décrivant le plus généralement possible les tags ou plutôt les actes de taguer comme des actes de langage survenant sur le Web".
- voc description "NiceTag is een ontologie die zo algemeen mogelijk tags beschrijft, of meer precies de handeling van het taggen. NiceTag beschrijft de handeling van het taggen als een op het web plaats vindende taalhandeling.".
- voc description "NiceTag è un'ontologia che descrive nel modo più generale possibile le tag, o meglio le azioni di tagging, come atti linguistici nel Web".
- v2 description "A vocabulary to model context-aware presentation knowledge for RDF User Interfaces.".
- v2 description "A vocabulary to describe the access policies which protect an RDF data store.".
- terms description "This ontology models and represents Term entities from Nature Publishing Group.".
- ns description "Ontology for representing OnlinePresence.".
- SmartHomeWeather.owl description "A ontology defining weather-related concepts and properties being relevant to smart home systems that provide predictive control.".
- nif-core description "For a more concise description about NIF, we refer the reader to the ISWC 2013 in Use paper: Integrating NLP using Linked Data by Sebastian Hellmann, Jens Lehmann, Sören Auer, and Martin Brümmer available at: http://svn.aksw.org/papers/2013/ISWC_NIF/public.pdf Also the NLP2RDF project page (http://nlp2rdf.org) provides more general documentation and pointers.\n The NIF 2.0 Core Ontology (http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#) provides classes and properties to describe the relations between substrings, text, documents by assigning URIs to strings. These URIs can then be used as subjects in RDF triples and therefore they can be annotated easily. The NIF 2.0 Core Specification defines how such URIs are created and used: http://persistence.uni-leipzig.org/nlp2rdf/specification/core.html and it makes sense to read this document first, so you can understand the definitions in this ontology better. \n \n The main class in this ontology is nif:String, which is the class of all words over the alphabet of Unicode characters (sometimes called Σ∗). We built NIF upon the Unicode Normalization Form C, as this follows the recommendation of the RDF standard for rdf:Literal. Indices are to be counted in code units as is common in most programming language and SPARQL engines ( see 17.4.3.2 STRLEN and 17.4.3.3 SUBSTR on http://www.w3.org/TR/sparql11-query/). \n \n Each URI Scheme (nif:URIScheme) used to address strings is a subclass of nif:String and puts further restrictions over the syntax of the URIs. For example, instances of type nif:RFC5147String have to adhere to the Syntax and Semantics of RFC 5147 (http://tools.ietf.org/html/rfc5147). Users of NIF can create their own URI schemes by subclassing nif:String and providing documentation on the Web in the rdfs:comment field.\n \n Another important subclass of nif:String is the nif:Context OWL class. This class is assigned to the whole string of the text (i.e. all characters). The purpose of an individual of this class is special, because the string of this individual is used to calculate the indices for all substrings. Therefore, all substrings have to have a relation nif:referenceContext pointing to an instance of nif:Context. Furthermore, the datatype property nif:isString can be used to include the reference text as a literal within the RDF as is required for the web service scenario. An example of NIF Core can be seen on the top left of the example Figure. \n\t\n\tOntology models\n\tThis ontology is split in different complimentary parts:\n\t* a terminological model (containing rdfs:comment, rdfs:label, rdfs:subClassOf, rdfs:subPropertyOf, rdfs:range and rdfs:domain statements)\n\t* an inference model (containing owl:TransitiveProperty, owl:hasKey), see nif-core-inf.ttl\n\t* a validation model (containing owl:FunctionalProperty, owl:DisjointWith), see nif-core-val.ttl\n\t* a Stanford profile model (containing a more complex structure)\n\tAn overview is given at the bottom of: http://persistence.uni-leipzig.org/nlp2rdf/ \n\n\tFeedback\n\tIf you'd like to leave feedback, please open an issue on GitHub (https://github.com/NLP2RDF/ontologies/issues) and read the README (https://github.com/NLP2RDF/ontologies#readme) or write an email to the mailing list: http://lists.informatik.uni-leipzig.de/mailman/listinfo/nlp2rdf\n\n\tVersioning process is explained here: http://persistence.uni-leipzig.org/nlp2rdf/specification/version.html Changelog is written to rdfs:comment (resource level versioning).\n".
- nif-core description nif-core-ontology_web.png.
- rlog description "We built this ontology by looking at log4j version 1.2 and version 2 beta: http://logging.apache.org/log4j/2.x/manual/layouts.html, http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html \n\tIs this complete? No! But it will be sufficient for most use cases, please feel free to extend and adapt the ontology, if you need more. \n Loglevels: TRACE, DEBUG, INFO, WARN, ERROR and FATAL\n \n Feedback\n\tIf you'd like to leave feedback, please open an issue on GitHub (https://github.com/NLP2RDF/ontologies/issues) and read the README (https://github.com/NLP2RDF/ontologies#readme) or write an email to the mailing list: http://lists.informatik.uni-leipzig.de/mailman/listinfo/nlp2rdf\n\n\tVersioning process is explained here: http://persistence.uni-leipzig.org/nlp2rdf/specification/version.html\n \n Changelog:\n * 1.0.0 initial version\n * 1.0.1 added Error Code class and errcode property\n * 1.1.0 change Error Code class to Status Code\n ".
- aws description "Meteorological sensor ontology (sensor types)".
- definitionURI description "URI that contains an authoritative definition of the referent thing".
- name description "human-readable word or sequence of words by which a thing is known".
- symbol description "short symbolic name".
- event.owl description "\n\t\tThis ontology deals with the notion of reified events---\n\t\tevents seen as first-class objects. It only defines one\n\t\tconcept: Event, which may have agents (actively\n\t\tparticipating), factors (passively participating), products,\n\t\tand a location in space and time. \n\n\t\tRegarding the ontological status of event tokens, they are seen\n\t\tas the way cognitive agents classify space/time regions\n\t".
- universaltimeline description "The timeline one can addresss \"the 1st of July, 2007\"".
- arch description "An RDF vocabulary for describing archival collections and the names associated with them".
- b2bo description "B2BO - Business to Business Ontology it's vocabulary, which is designed to describe documents exchanged in B2B processes. \n\nAim of this vocabulary is to give an ability to create B2B document in standard, which allows exchange documents between B2B entities, e.g. VAT invoice or offer. Most users not familiar with OWL, RDF and others Semantic Web technologies should treat this ontology as a formal, readable for machine language description of electronic business documents. Referring to EDI standard, B2BO gives opportunity not only to exchange documents, but make it possible to describe information in a manner that allows you to compare and processing offers and product specifications. \n\nNOTICE!\nThis ontology has been created under the laws in force in Poland, and in the case of documents that are not legally defined you should treat this like recommendation or proposal. You should not define document based only on this document, make sure that you document is always lawful. As a developers, we'll make everything we can to keep this standard in good conditions, but remember - you take responsibilities for your documents!".
- biotop.owl description "BioTop Website:\nhttp://purl.org/biotop\n\n\nSee related articles at:\n\nhttp://www.google.com/search?q=Schulz+BioTop+site:www.ncbi.nlm.nih.gov/pmc/articles+ontology+OR+ontologies".
- biotop.owl description "Upper-Level ontology for Biology and Medicine. Compatible with BFO, DOLCE, and the UMLS Semantic Network (mapping files available)".
- frapo description "FRAPO is an ontology for use to describe research project administrative information and to work with CRIS (Current Research Information Systems). It can be used for the characterization of grant applications, funding bodies, projects, project partners, etc. It can also be used to describe other types of projects, for example building projects and educational projects. \n\nFRAPO imports FOAF and is designed to work with SCoRO, the Scholarly Contributions and Roles Ontology (http://purl.org/spar/scoro/), which is used to characterize the contributions and time-limited roles that may exist between agents such as people and organizations and entities such as projects, research investigations or research outputs. \n\nFaBiO, the FRBR-alightned bibliographic ontology (http://purl.org/spar/fabio/), provides terms for documents of relevance, such as grant applications, project plans, project reports, datasets and journal articles, which are therefore not included within FRAPO.\n\nFRAPO is not intended to describe the details of research investigations enabled by funded research projects, nor their component studies and assays, which are the domain of a complementary ontology, ISA-RDF (under development - add URL).".
- InfrastructureEntity description "owl:equivalentClass cerif:InfrastructureEntity .".
- Output description "Ontology terms and definitions for most publishable project outputs are given as 'Expression' classes in FaBiO, the FRBR-aligned Bibliographic Ontology, e.g. fabio:JournalArticle, fabio:DataSet. For 'deliverables', use frapo:Deliverable. For material outputs, use frapo:MaterialOutput.".
- Repository description "May also be described as an archive, or as a database.".
- donates description "Range constraints have been removed from this object property to permit it to be used in unforeseen ways.".
- employs description "This property should not be used for the other meaning of 'employ', meaning to use something, e.g. 'He employed great skill . . .'/".
- enables description "Domain and range constraints have been removed from this object property to permit it to be used in unforeseen ways.".
- hasOutput description "Domain and range constraints have been removed from this object property to permit it to be used in unforeseen ways.".
- hasPersonalIdentifier description "owl:equivalentProperty <http://purl.org/spar/datacite/hasPersonalIdentifier> .".
- hasPersonalIdentifier description "owl:equivalentProperty <http://purl.org/spar/scoro/hasPersonalIdentifier> .".
- isPurchasedBy description "Domain constraints have been removed from this object property to permit it to be used in unforeseen ways.".
- isSupportedBy description "This property is not intended for use to describe mechanical or physical support, as in 'The statue is supported by the plinth'.".
- purchasesFrom description "Domain and range constraints on this object property have been relaxed to permit it to be used in unforeseen ways.".
- supplies description "Domain constraints on this object property have been relaxed to permit it to be used in unforeseen ways.".
- supports description "This property is not intended for use to describe mechanical or physical support, as in 'The plinth supports the statue'.".
- followedBy description "Given the list (I[1], I[2], ... , I[i-1], I[i], I[i+1], ... , I[n-1], I[n]), the item I[i] is followed by I[i+1], ... , I[n-1] and I[n].".
- nextItem description "Given the list (I[1], I[2], ... , I[i-1], I[i], I[i+1], ... , I[n-1], I[n]), the next item of I[i] is I[i+1].".
- precededBy description "Given the list (I[1], I[2], ... , I[i-1], I[i], I[i+1], ... , I[n-1], I[n]), the item I[i] is preceded by I[i-1], ... , I[2] and I[1].".
- previousItem description "Given the list (I[1], I[2], ... , I[i-1], I[i], I[i+1], ... , I[n-1], I[n]), the previous item of I[i] is I[i-1].".
- size description "CO defines the size of a collection as the sum of the number of times entities that are part of the collection appear in it. This means that co:size considers how much each entity is involved by a particular collection, i.e.:\n- the size of the set {a, b, c} is three\n- the size of the bag [a, a, b, b, b, c] is five\n- the size of the list (a, b, c, b, a, b, c, c) is seven".
- dcmitype description "The Dublin Core Types namespace provides URIs for the entries of the DCMI Type Vocabulary. Entries are declared using RDF Schema language to support RDF applications. The Schema will be updated according to dc-usage decisions.".
- DCMIType description "The DCMI Type Vocabulary provides a general, cross-domain list of\n\t approved terms that may be used as values for the Resource Type\n\t element to identify the genre of a resource.".
- library description "These are \"library\" extension terms intended for use with Schema.org".
- core description "The Modular and Unified Tagging Ontology (MUTO) is an ontology for tagging and folksonomies. It is based on a thorough review of earlier tagging ontologies and unifies core concepts in one consistent schema. It supports different forms of tagging, such as common, semantic, group, private, and automatic tagging, and is easily extensible.".
- bibtex description "Transformation of bibTeX into an OWL ontology".
- hasAuthor description "This is tricky due to the fact that order is not (generally) preserved in RDF documents. The problem arises when you want to have an author list where the order is _extremely_ important. How shall we do that? Perhaps we want to define \"hasPrimaryAuthor\", \"hasSecondaryAuthor\", \"hasTertiaryAuthor\", and \"hasRemainingAuthors\", or something of that sort. This will be have to given more thought.".
- hasInstitution description "This could be an object property that refers to an external set of institution instances.".
- hasJournal description "This could optionally be an object property, whereby the range would refer to an external set of journal instances, thus providing standardized abbreviations for different bibliographic styles.".
- hasPublisher description "This is a case where an ObjectProperty might be a better choice, where the range is some set of publisher names defined in another ontology. That would allow all of the metadata for the publisher to be incorporated as needed.".
- hasSchool description "As with \"hasPublisher\", this could be an ObjectProperty that refers to an external set of school instances.".
- core description "The Association Ontology specification provides basic properties \nfor describing specific associations to something, e.g. a context, an occasion, a genre or a mood, and enables furthermore, a mechanism to \nlike/rate and feedback these associations in context to something on/ for the Semantic Web. This document contains a RDF description \nof the Association Ontology.".
- core description "A vocabulary for describing cognitive pattern within contexts, their temporal dynamics and their origins".
- core description "The Counter Ontology specification provides basic concepts and properties \nfor describing a general counter concept and some important sub counters, e.g. an event counter, on/ for \nthe Semantic Web. This document contains a RDF description of the Counter Ontology.".
- core description "The Information Service Ontology Specification provides basic concepts and properties \nfor describing different information services, e.g. Wikipedia, MusicBrainz, Freebase or Discogs, on/ for \nthe Semantic Web. This document contains a RDF description of the Information Service Ontology.".
- mo description "\n The Music Ontology Specification provides main concepts and \n properties fo describing music (i.e. artists, albums and tracks) \n on the Semantic Web. \n ".
- core description "The Ordered Lists Ontology Specification provides basic concepts and properties \nfor describing ordered lists as semantic graph. This document contains a RDF description of the Ordered Lists Ontology\nas proposed by Samer Abdallah.".
- core description "The Play Back Ontology specification provides basic concepts and properties \nfor describing concepts that are related to the play back domain, e.g. an playlist, play back count and skip counter \non/ for the Semantic Web. This document contains a RDF description of the Play Back Ontology.".
- core description "A vocabulary for describing the ontology design pattern of property reification. That means the semantic relation of \na \"shortcut relation\" (subject, predicate, object) with its detailed description of the relationship.".
- core description "The Recommendation Ontology specification provides basic concepts and properties \nfor describing recommendations on/ for the Semantic Web. This document contains a RDF description of the Recommendation Ontology.".
- storyline description "An ontology to represent News Storylines.".
- core description "A vocabulary for describing preferences (interests) within contexts, their temporal dynamics and their origin".
- core description "A vocabulary for describing weightings and their referenced scales.".
- pav description "PAV supplies terms for distinguishing between the different roles of the agents contributing content in current web based systems: contributors, authors, curators and digital artifact creators. The ontology also provides terms for tracking provenance of digital entities that are published on the web and then accessed, transformed and consumed. In order to support broader interoperability, PAV specializes the general purpose W3C PROV provenance model (PROV-O).\n\nPAV distinguishes between the data related to the digital artifact - named Provenance - and those related to the actual knowledge creation and therefore to the intellectual property aspects – named Authoring. The Versioning axis describes the evolution of digital entities in time.\n\nUsing PAV, descriptions can define the authors that originate or gave existence to the work that is expressed in the digital resource (pav:authoredBy); curators (pav:curatedBy) who are content specialists responsible for shaping the expression in an appropriate format, and contributors (super-property pav:contributedBy) that provided some help in conceiving the resource or in the expressed knowledge creation/extraction.\n\nThese provenance aspects can be detailed with dates using pav:curatedOn, pav:authoredOn, etc. Further details about the creation activities, such as different authors contributing specific parts of the resource at different dates are out of scope for PAV and should be defined using vocabularies like PROV-O and additional intermediate entities to describe the different states.\n\nFor resources based on other resources, PAV allows specification of direct retrieval (pav:retrievedFrom), import through transformations (pav:importedFrom) and sources that were merely consulted (pav:sourceAccessedAt). These aspects can also define the agents responsible using pav:retrievedBy, pav:importedBy and pav:sourceAccessedBy.\n\nVersion number of a resource can be given with pav:version, the previous version of the resource with pav:previousVersion, and any other earlier versions with pav:hasEarlierVersion. Unversioned, 'mutable' resources can specify their current version as a snapshot resource using pav:hasCurrentVersion and list the earlier versions using pav:hasVersion.\n\nThe creation of the digital representation (e.g. an RDF graph or a .docx file) can in many cases be different from the authorship of the content/knowledge, and in PAV this digital creation is specified using pav:createdBy, pav:createdWith and pav:createdOn.\n\nPAV specializes terms from W3C PROV-O (prov:) and DC Terms (dcterms:), however these ontologies are not OWL imported as PAV can be used independently. The \"is defined by\" links indicate where those terms are included from. See http://www.w3.org/TR/prov-o and http://dublincore.org/documents/2012/06/14/dcmi-terms/ for more details. See http://purl.org/pav/mapping/dcterms For a comprehensive SKOS mapping to DC Terms.\n\nPAV 2 is based on PAV 1.2 but in a different namespace ( http://purl.org/pav/ ). Terms compatible with 1.2 are indicated in this ontology using owl:equivalentProperty.\n\nThe ontology IRI http://purl.org/pav/ always resolve to the latest version of PAV 2. Particular versionIRIs such as http://purl.org/pav/2.1 can be used by clients to force imports of a particular version - note however that all terms are defined directly in the http://purl.org/pav/ namespace.\n\nThe goal of PAV is to provide a lightweight, straight forward way to give the essential information about authorship, provenance and versioning, and therefore these properties are described directly on the published resource. As such, PAV does not define any classes or restrict domain/ranges, as all properties are applicable to any online resource.\n\n--\n\nCopyright 2008-2014 Massachusetts General Hospital; Harvard Medical School; Balboa Systems; University of Manchester\n\nLicensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.".
- pav description pav-overview.svg.
- channel description "\"An RSS information channel.\"".
- biro description "BiRO, the Bibliographic Reference Ontology, is an ontology structured according to the FRBR model to define bibliographic records (as subclasses of frbr:Work) and bibliographic references (as subclasses of frbr:Expression), and their compilations into bibliographic collections such as library catalogues, and into bibliographic lists such as reference lists in journal articles, respectively.\n\nIt provides a logical system for relating an individual bibliographic reference, such as appears in the reference list of a published article (which may lack the title of the cited article, the full names of the listed authors, or indeed the full list of authors):\n- to the full bibliographic record for that cited article, which in addition to missing reference fields may also include the name of the publisher, and the ISSN or ISBN of the publication;\n- to collections of bibliographic records such as library catatlogues; and\n- to bibliographic lists, such as reference lists.".
- biro description BiRO.png.
- BibliographicCollection description "A bibliographic collection is composed only of items containing bibliographic records. Moreover, it cannot be part of other bibliographic collections, and it is realized only by bibliographic lists.".