Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- version comment "This version of this document (eg number, date, etc). A string".
- rec54 comment "$Id: rec54.rdf,v 1.20 2014-06-12 11:03:50 denis Exp $".
- TMO_0011 comment "Examples: connection table, fragment, pharmacophore.".
- TMO_0172 comment "A variant DNA region is a DNA region of which variants with altered sequence exist in different individuals of the same species or in different samples of the same individual (e.g., genetic variation within an individual, such as mutations in a cancerous tumor). The number of nucleotide residues in different variants can differ (e.g., because of insertions and deletions).".
- TMO_0215 comment "A DNA region is a part of a DNA molecule that is made up of a continous chain of deoxyribonucleotide residues.".
- TMO_0228 comment "A part of a molecular entity or a set of molecular entities. It can be made up of several non-connected sub-parts, potentially on separate molecular entities.".
- owl comment "\n This ontology partially describes the built-in classes and\n properties that together form the basis of the RDF/XML syntax of OWL 2.\n The content of this ontology is based on Tables 6.1 and 6.2\n in Section 6.4 of the OWL 2 RDF-Based Semantics specification,\n available at http://www.w3.org/TR/owl2-rdf-based-semantics/.\n Please note that those tables do not include the different annotations\n (labels, comments and rdfs:isDefinedBy links) used in this file.\n Also note that the descriptions provided in this ontology do not\n provide a complete and correct formal description of either the syntax\n or the semantics of the introduced terms (please see the OWL 2\n recommendations for the complete and normative specifications).\n Furthermore, the information provided by this ontology may be\n misleading if not used with care. This ontology SHOULD NOT be imported\n into OWL ontologies. Importing this file into an OWL 2 DL ontology\n will cause it to become an OWL 2 Full ontology and may have other,\n unexpected, consequences.\n ".
- AllDifferent comment "The class of collections of pairwise different individuals.".
- AllDisjointClasses comment "The class of collections of pairwise disjoint classes.".
- AllDisjointProperties comment "The class of collections of pairwise disjoint properties.".
- AnnotationProperty comment "The class of annotation properties.".
- AsymmetricProperty comment "The class of asymmetric properties.".
- Axiom comment "The class of annotated axioms for which the RDF serialization consists of an annotated subject, predicate and object.".
- Class comment "The class of OWL classes.".
- DataRange comment "The class of OWL data ranges, which are special kinds of datatypes. Note: The use of the IRI owl:DataRange has been deprecated as of OWL 2. The IRI rdfs:Datatype SHOULD be used instead.".
- DatatypeProperty comment "The class of data properties.".
- DeprecatedClass comment "The class of deprecated classes.".
- DeprecatedProperty comment "The class of deprecated properties.".
- FunctionalProperty comment "The class of functional properties.".
- InverseFunctionalProperty comment "The class of inverse-functional properties.".
- IrreflexiveProperty comment "The class of irreflexive properties.".
- NamedIndividual comment "The class of named individuals.".
- NegativePropertyAssertion comment "The class of negative property assertions.".
- Nothing comment "This is the empty class.".
- ObjectProperty comment "The class of object properties.".
- Ontology comment "The class of ontologies.".
- OntologyProperty comment "The class of ontology properties.".
- ReflexiveProperty comment "The class of reflexive properties.".
- Restriction comment "The class of property restrictions.".
- SymmetricProperty comment "The class of symmetric properties.".
- Thing comment "".
- Thing comment "Identité numérique, agents et données.".
- Thing comment "The class of OWL individuals.".
- TransitiveProperty comment "The class of transitive properties.".
- allValuesFrom comment "The property that determines the class that a universal property restriction refers to.".
- differentFrom comment "The property that determines that two given individuals are different.".
- sameAs comment "The property that determines that two given individuals are equal.".
- topDataProperty comment "The data property that relates every individual to every data value.".
- topObjectProperty comment "The object property that relates every two individuals.".
- topObjectProperty comment "hasIssuer".
- wgs84_pos comment "Recent changes to this namespace:\n$Log: wgs84_pos.rdf,v $\nRevision 1.22 2009/04/20 15:00:30 timbl\nRemove the time bits which have been deal with elsewhere eg in iCal.\n\nRevision 1.21 2009/04/20 12:52:47 timbl\ntry again\n\nRevision 1.20 2009/04/20 12:42:11 timbl\nAdd Event (edited ages ago and never checked in), and location (following discussion http://chatlogs.planetrdf.com/swig/2009-04-20#T12-36-09)\n\nRevision 1.19 2009/04/20 12:36:31 timbl\nAdd Event (edited ages ago and never checked in), and location (following discussion http://chatlogs.planetrdf.com/swig/2009-04-20#T12-36-09)\n\nRevision 1.18 2006/02/01 22:01:04 danbri\nClarified that lat and long are decimal degrees, and that alt is decimal metres about local reference ellipsoid\n\nRevision 1.17 2004/02/06 17:38:12 danbri\nFixed a bad commit screwup\n\nRevision 1.15 2003/04/19 11:24:08 danbri\nFixed the typo even more.\n\nRevision 1.14 2003/04/19 11:16:56 danbri\nfixed a typo\n\nRevision 1.13 2003/02/19 22:27:27 connolly\nrelaxed domain constraints on lat/long/alt from Point to SpatialThing\n\nRevision 1.12 2003/01/12 01:41:41 danbri\nTrying local copy of XSLT doc.\n\nRevision 1.11 2003/01/12 01:20:18 danbri\nadded a link to morten's xslt rdfs viewer.\n\nRevision 1.10 2003/01/11 18:56:49 danbri\nRemoved datatype range from lat and long properties, since they would\nhave required each occurance of the property to mention the datatype.\n\nRevision 1.9 2003/01/11 11:41:31 danbri\nAnother typo; repaired rdfs:Property to rdf:Property x4\n\nRevision 1.8 2003/01/11 11:05:02 danbri\nAdded an rdfs:range for each lat/long/alt property,\nhttp://www.w3.org/2001/XMLSchema#float\n\nRevision 1.7 2003/01/10 20:25:16 danbri\nLonger rdfs:comment for Point, trying to be Earth-centric and neutral about\ncoordinate system(s) at the same time. Feedback welcomed.\n\nRevision 1.6 2003/01/10 20:18:30 danbri\nAdded CVS log comments into the RDF/XML as an rdfs:comment property of the\nvocabulary. Note that this is not common practice (but seems both harmless\nand potentially useful).\n\n\nrevision 1.5\ndate: 2003/01/10 20:14:31; author: danbri; state: Exp; lines: +16 -5\nUpdated schema:\nAdded a dc:date, added url for more info. Changed the rdfs:label of the\nnamespace from gp to geo. Added a class Point, set as the rdfs:domain of\neach property. Added XML comment on the lat_long property suggesting that\nwe might not need it (based on #rdfig commentary from implementors).\n\nrevision 1.4\ndate: 2003/01/10 20:01:07; author: danbri; state: Exp; lines: +6 -5\nFixed typo; several rdfs:about attributes are now rdf:about. Thanks to MortenF in\n#rdfig for catching this error.\n\nrevision 1.3\ndate: 2003/01/10 11:59:03; author: danbri; state: Exp; lines: +4 -3\nfixed buglet in vocab, added more wgs links\n\nrevision 1.2\ndate: 2003/01/10 11:01:11; author: danbri; state: Exp; lines: +4 -4\nRemoved alt from the as-a-flat-string property, and switched from\nspace separated to comma separated.\n\nrevision 1.1\ndate: 2003/01/10 10:53:23; author: danbri; state: Exp;\nbasic geo vocab".
- Point comment "A point, typically described using a coordinate system relative to Earth, such as WGS84.".
- Point comment "A point, typically described using a coordinate system relative to Earth, such as WGS84.".
- Point comment "Uniquely identified by lat/long/alt. i.e.\n\nspaciallyIntersects(P1, P2) :- lat(P1, LAT), long(P1, LONG), alt(P1, ALT),\n lat(P2, LAT), long(P2, LONG), alt(P2, ALT).\n\nsameThing(P1, P2) :- type(P1, Point), type(P2, Point), spaciallyIntersects(P1, P2).".
- Point comment "Uniquely identified by lat/long/alt. i.e.\n\nspaciallyIntersects(P1, P2) :- lat(P1, LAT), long(P1, LONG), alt(P1, ALT),\n lat(P2, LAT), long(P2, LONG), alt(P2, ALT).\n\nsameThing(P1, P2) :- type(P1, Point), type(P2, Point), spaciallyIntersects(P1, P2).".
- SpatialThing comment "Anything with spatial extent, i.e. size, shape, or position.\n e.g. people, places, bowling balls, as well as abstract areas like cubes.".
- SpatialThing comment "Anything with spatial extent, i.e. size, shape, or position.\n e.g. people, places, bowling balls, as well as abstract areas like cubes.".
- lat comment "The WGS84 latitude of a SpatialThing (decimal degrees).".
- lat comment "The WGS84 latitude of a SpatialThing (decimal degrees).".
- location comment "The relation between something and the point, \n or other geometrical thing in space, where it is. For example, the realtionship between\n a radio tower and a Point with a given lat and long.\n Or a relationship between a park and its outline as a closed arc of points, or a road and\n its location as a arc (a sequence of points).\n Clearly in practice there will be limit to the accuracy of any such statement, but one would expect\n an accuracy appropriate for the size of the object and uses such as mapping .".
- location comment "The relation between something and the point, \n or other geometrical thing in space, where it is. For example, the realtionship between\n a radio tower and a Point with a given lat and long.\n Or a relationship between a park and its outline as a closed arc of points, or a road and\n its location as a arc (a sequence of points).\n Clearly in practice there will be limit to the accuracy of any such statement, but one would expect\n an accuracy appropriate for the size of the object and uses such as mapping .".
- location comment "The relation between something and the point, or other geometrical thing in space, where it is.".
- long comment "The WGS84 longitude of a SpatialThing (decimal degrees)".
- long comment "The WGS84 longitude of a SpatialThing (decimal degrees).".
- ns comment "This vocabulary was created in the FOAF project, based on experience with FOAF, Dublin Core and other early RDF vocabularies. Deployment experience shows that changing namespace URIs is expensive and unrewarding, so this vocabulary provides terms to support in-place evolution of structured data vocabularies. By indicating status at the level of terms rather than vocabularies, dictionary-style, fine grained improvements become easier. Different organizations and parties can agree or disagree on the status of a vocabulary term; however the status published alongside the term may deserve special attention. Future work could include patterns for citing announcements and decisions, or using SKOS to decentralise the extension of the basic status levels.".
- swrl comment "RDF Schema definition of the RDF Concrete Syntax for the Semantic Web Rule Language".
- Atom comment "common superclass".
- BuiltinAtom comment "consists of a builtin and a List of arguments".
- ClassAtom comment "consists of a classPredicate and argument1".
- DataRangeAtom comment "consists of a dataRange and argument1".
- DatavaluedPropertyAtom comment "consists of a propertyPredicate (owl:DatatypeProperty), argument1 (owl:Thing), and argument2 (rdfs:Literal)".
- Imp comment "implication (rule)".
- IndividualPropertyAtom comment "consists of a propertyPredicate (owl:ObjectProperty), argument1 (owl:Thing), and argument2 (owl:Thing)".
- Variable comment "indicate that a URI is being used as a variable".
- IFD comment "An Image File Directory".
- date comment "a date information. Usually saved as YYYY:MM:DD (HH:MM:SS) format in Exif data, but represented here as W3C-DTF format".
- dateAndOrTime comment "An attribute relating to Date and/or Time".
- exifAttribute comment "A property that connects an IFD to one of its entries. Super property which integrates all Exif tags.".
- geo comment "Geometric data such as latitude, longitude and altitude. Usually saved as rational number.".
- gpsInfo comment "An attribute relating to GPS information".
- height comment "Height of an object".
- ifdPointer comment "A tag that refers a child IFD".
- imageConfig comment "An attribute relating to Image Configuration".
- imageDataCharacter comment "An attribute relating to image data characteristics".
- imageDataStruct comment "An attribute relating to image data structure".
- interopInfo comment "An attribute relating to Interoperability. Tags stored in\nInteroperability IFD may be defined dependently to each Interoperability rule.".
- length comment "Length of an object. Could be a subProperty of other general schema.".
- meter comment "A length with unit of meter".
- mm comment "A length with unit of mm".
- pictTaking comment "An attribute relating to Picture-Taking Conditions".
- pimInfo comment "An attribute relating to print image matching".
- recOffset comment "An attribute relating to recording offset".
- relatedFile comment "Tag Relating to Related File Information".
- resolution comment "a rational number representing a resolution. Could be a subProperty of other general schema.".
- seconds comment "a mesurement of time length with unit of second".
- tag_number comment "The Exif tag number".
- userInfo comment "An attribute relating to User Information".
- versionInfo comment "An attribute relating to Version".
- width comment "Width of an object".
- InformationResource comment "A resource which has the property that all of its essential characteristics can be conveyed in a message".
- RDFGraph comment "a\n set of RDF triples".
- RootNode comment "the root of the tree in the XPath data\n model".
- Transformation comment "an InformationResource that specifies\n a transformation from a set of XML documents to RDF graphs".
- TransformationProperty comment "a FunctionalProperty that relates\n XML document root nodes to\n RDF graphs".
- transformationProperty comment "relates a transformation to the algorithm\n specified by the property that computes an RDF graph from an XML\n document node".
- Concept comment "<p xmlns=\"http://www.w3.org/ns/radion#\">The Conceptual Model includes a 'Code' datatype that \n is used by several classes. This is expressed using the <a href=\"http://www.w3.org/TR/skos-primer/\">SKOS vocabulary</a> with\n a particular 'code' usually being a skos:Concept that is part of a scheme. \n The intention is that the skos:Concept class be used as follows;</p><ul>\n <li>for the content property, use skos:notation</li>\n <li>the 'list' property will be taken care of by means of the skos:inScheme property;</li>\n <li>the list agency property is likely to be applied to the scheme as a whole for which dcterms:creator is appropriate;</li>\n <li>the list version property can be fulfilled using schema:version (see <a href=\"http://schema.org/CreativeWork\">http://schema.org/CreativeWork</a>)</li></ul>\n ".
- Concept comment "A SKOS concept can be viewed as an idea or notion; a unit of thought. However, what constitutes a unit of thought is subjective, and this definition is meant to be suggestive, rather than restrictive.\n\nThe notion of a SKOS concept is useful when describing the conceptual or intellectual structure of a knowledge organization system, and when referring to specific ideas or meanings established within a KOS.\n\nNote that, because SKOS is designed to be a vehicle for representing semi-formal KOS, such as thesauri and classification schemes, a certain amount of flexibility has been built in to the formal definition of this class.".
- Concept comment "super class of ISO ThesaurusConcept\n\nThe mandatory attribute identifier may be mapped to the Dublin Core property dc:identifier.\nAttributes or associations not detailed below typically are mapped to dc: (or dct:) properties:\n- dct:created\n- dct:modified".
- ConceptScheme comment "A SKOS concept scheme can be viewed as an aggregation of one or more SKOS concepts. Semantic relationships (links) between those concepts may also be viewed as part of a concept scheme. This definition is, however, meant to be suggestive rather than restrictive, and there is some flexibility in the formal data model stated below.\n\nThe notion of a concept scheme is useful when dealing with data from an unknown source, and when dealing with data that describes two or more different knowledge organization systems.".
- ConceptScheme comment "super class of ISO Thesaurus\n\nThe mandatory attribute identifier may be mapped to the Dublin Core property dc:identifier. A typical representation of a thesaurus should document a (scoped) relationship between an identifier of this thesaurus and the URI of the RDF Concept Scheme URI.\n\nThe mandatory attribute lang can be mapped to either of the Dublin Core properties dc:language or dct:language. The value space is defined by RFC 4646. For multilingual thesaurus, one lang attribute is needed per supported language.\n\nTypically these can be mapped to the corresponding Dublin Core dc: (or dct:) properties:\n- dc:contributor\n- dc:coverage\n- dc:creator\n- dct:created\n- dct:modified\n- dc:date\n- skos:definition\n- dc:format\n- dc:publisher\n- dc:relation, dct:relation or a specialization\n- dc:rights\n- dc:source\n- dc:subject\n- dc:title\n- dc:type\n\nThe association \"hasVersion\" is discussed in the Version_History section of the mapping documentation (http://www.niso.org/schemas/iso25964/correspondencesSKOS/).".