Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- Resource comment "A HTTP-addressable resource whose lifecycle is managed by a LDP server.".
- locn comment "This is a new version of the final draft published by the European Commission in May 2012, revised according to the results of the ISA Core Location Pilot (see Section Change History for the list of changes). It is currently under the control of the Locations and Addresses Community Group, but is not under active development or review. Comments and queries should be sent to that group via public-locadd@w3.org. Terms defined here may be deprecated by that or future groups but will not disappear or their definition change.".
- Address comment "An \"address representation\" as defined in the <a xmlns=\"http://purl.org/oslo/ns/localgov#\" href=\"https://inspire-twg.jrc.ec.europa.eu/inspire-fc.html#_C2538\">data specifications</a> of the EU INSPIRE Directive. The <a xmlns=\"http://purl.org/oslo/ns/localgov#\" href=\"#locn:addressId\">locn:addressId</a> property may be used to link this Address to other representations.".
- Address comment "An \"address representation\" as defined in the INSPIRE Data Specification on Addresses, v3.0.1. The locn:addressId property may be used to link this locn:Address to other representations.".
- Geometry comment "The Geometry Class provides the means to identify a Location as a point, line, polygon, etc. expressed using coordinates in some coordinate reference system.".
- Geometry comment "The locn:Geometry class provides the means to identify a location as a point, line, polygon, etc. expressed using coordinates in some coordinate reference system.".
- address comment "The locn:address property relationship associates any resource with the <a xmlns=\"http://purl.org/oslo/ns/localgov#\" href=\"#locn:Address\">Address</a> Class ".
- address comment "The locn:address property relationship associates any resource with the locn:Address class ".
- addressArea comment "The name or names of a geographic area or locality that groups a number of addressable objects for addressing purposes, without being an administrative unit. This would typically be part of a city, a neighbourhood or village. The domain of locn:addressArea is locn:Address.".
- adminUnitL1 comment "The uppermost administrative unit for the address, almost always a country. The domain of locn:adminUnitL1 is locn:Address and the range is a literal, conceptually defined by the INSPIRE Geographical Name data type.".
- adminUnitL2 comment "The region of the address, usually a county, state or other such area that typically encompasses several localities. The domain of locn:adminUnitL2 is locn:Address and the range is a literal, conceptually defined by the INSPIRE Geographical Name data type.".
- fullAddress comment "The complete address written as a string, with or without formatting. The domain of locn:fullAddress is locn:Address.".
- geographicName comment "<p xmlns=\"http://purl.org/oslo/ns/localgov#\">A geographic name is a proper noun applied to a spatial object. Taking the example used in the <a xmlns=\"http://purl.org/oslo/ns/localgov#\" href=\"http://inspire.jrc.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_GN_v3.0.1.pdf\">INSPIRE document</a> (page 18), the following are all valid geographic names for the Greek capital:</p>\n <ul xmlns=\"http://purl.org/oslo/ns/localgov#\"><li xmlns=\"http://purl.org/oslo/ns/localgov#\">A?n?a (the Greek endonym written in the Greek script)</li><li xmlns=\"http://purl.org/oslo/ns/localgov#\">Athina (the standard Romanisation of the endonym)</li><li xmlns=\"http://purl.org/oslo/ns/localgov#\">Athens (the English language exonym)</li></ul>\n <p xmlns=\"http://purl.org/oslo/ns/localgov#\">For INSPIRE-conformant data, provide the metadata for the geographic name using a skos:Concept as a datatype.</p>".
- geographicName comment "\nA geographic name is a proper noun applied to a spatial object. Taking the example used in the INSPIRE Data Specification on Geographical Names, v3.0.1 (pages 40-42), the following are all valid geographic names for the Greek capital:\n\n- Aθnνa (the Greek endonym written in the Greek script)\n\n- Athína (the standard Romanisation of the endonym)\n\n- Athens (the English language exonym)\n\nFor INSPIRE-conformant data, provide the metadata for the geographic name using a skos:Concept as a datatype.\n".
- geometry comment "Associates any <a xmlns=\"http://purl.org/oslo/ns/localgov#\" href=\"#dcterms:Location\">Location</a> with the locn:Geometry class.".
- geometry comment "Associates any resource with the corresponding geometry.".
- location comment "The location property links any resource to the Location Class. Asserting the location relationship implies only that the domain has some connection to a Location in time or space. It does not imply that the resource is necessarily at that location at the time when the assertion is made.".
- location comment "The location property links any resource to the Location Class. \n Asserting the location relationship implies only that the domain has some connection to a \n Location in time or space. It does not imply that the resource is necessarily at that location \n at the time when the assertion is made.".
- locatorDesignator comment "A number or a sequence of characters that uniquely identifies the locator within the relevant scope(s). The full identification of the locator could include one or more locator designators.\n ".
- poBox comment "The Post Office Box number. The domain of locn:poBox is locn:Address.".
- postCode comment "The post code (a.k.a postal code, zip code etc.). Post codes are common elements in many countries' postal address systems. The domain of locn:postCode is locn:Address.".
- postName comment "The key postal division of the address, usually the city. (INSPIRE's definition is \"One or more names created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.\") The domain of locn:postName is locn:Address.".
- postName comment "The key postal division of the address, usually the city. (INSPIRE's definition is \"One or more names created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.\"). The domain of locn:postName is locn:Address.".
- thoroughfare comment "An address component that represents the name of a passage or way through from one location to another. A thoroughfare is not necessarily a road, it might be a waterway or some other feature. The domain of locn:thoroughfare is locn:Address.".
- ma-ont comment "Created by Tobias Buerger, Jean Pierre Evain and Pierre-Antoine Champin with the RDFS Taskforce within the W3C Media Annotation Working Group.".
- ma-ont comment "THE CONTENT OF THIS MA-ONT.RDF AND DERIVED MA-ONT.TTL FILES PREVAIL OVER THE SPECIFICATION.".
- Agent comment "A person or organisation contributing to the media resource.".
- Collection comment "Any group of media resource e.g. a series.".
- DataTrack comment "Ancillary data track e.g. captioning in addition to video and audio tracks. Specialisation is made through the use of appropriate object properties.".
- Image comment "A still image / thumbnail / key frame related to the media resource or being the media resource itself.".
- Location comment "A location related to the media resource, e.g. depicted in the resource (possibly fictional) or where the resource was created (shooting location), etc.".
- MediaFragment comment "A media fragment (spatial, temporal, track...) composing a media resource. In other ontologies fragment is sometimes referred to as a 'part' or 'segment'.".
- MediaResource comment "An image or an audiovisual media resource, which can be composed of one or more fragment / track.".
- Person comment "A physical person.".
- Rating comment "Information about the rating given to a media resource.".
- TargetAudience comment "Information about The target audience (target region, target audience category but also parental guidance recommendation) for which a media resource is intended.".
- Track comment "A specialisation of MediaFragment for audiovisual content.".
- VideoTrack comment "A specialisation of Track for Video to provide a link to specific data properties such as frameRate, etc. Signing is another possible example of video track. Specialisation is defined through object properties.".
- alternativeTitle comment "Corresponds to 'title.title' in the Ontology for Media Resources with a 'title.type' meaning \"alternative\".".
- creationDate comment "Corresponds to 'date.date' in the Ontology for Media Resources with a 'date.type' meaning \"creationDate\".".
- date comment "Corresponds to date.date in the ontology for Media Resources. Subproperties can be used to distinguish different values of 'date.type'. The recommended range is 'xsd:dateTime' (for compliance with OWL2-QL and OWL2-RL) but other time-related datatypes may be used (e.g. 'xsd:gYear', 'xsd:date'...).".
- description comment "Corresponds to 'description' in the Ontology for Media Resources. This can be specialised by using sub-properties e.g. 'summary' or 'script'.".
- duration comment "Corresponds to 'duration' in the Ontology for Media Resources.".
- fragmentName comment "Corresponds to 'namedFragment.label' in the Ontology for Media Resources.".
- frameHeight comment "Corresponds to 'frameSize.height' in the Ontology for Media Resources, measured in frameSizeUnit.".
- frameRate comment "Corresponds to 'frameRate' in the Ontology for Media Resources, in frame per second.".
- frameSizeUnit comment "Corresponds to 'frameSize.unit' in the Ontology for Media Resources.".
- frameWidth comment "Corresponds to 'frameSize.width' in the Ontology for Media Resources measured in frameSizeUnit.".
- hasCaptioning comment "Corresponds to 'fragment' in the Ontology for Media Resources with a 'fragment.role' meaning \"captioning\". This property can for example point to a spatial fragment, a VideoTrack or a DataTrack. The language of the captioning track can be expressed by attaching a 'hasLanguage' property to the specific track.".
- hasCompression comment "Corresponds to 'compression' in the Ontology for Media Resources.".
- hasContributor comment "Corresponds to 'contributor.contributor' in the Ontology for Media Resources. Subproperties can be used to distinguish different values of 'contributor.role'.".
- hasCreator comment "Corresponds to 'creator.creator' in the Ontology for Media Resources. Subproperties can be used to distinguish different values of 'creator.role'. Note that this property is semantically a subproperty of 'hasContributor'.".
- hasFormat comment "Corresponds to 'format' in the Ontology for Media Resources.".
- hasFragment comment "Corresponds to 'fragment' in the Ontology for Media Resources. Subproperties can be used to distinguish different values of 'fragment.role'.".
- hasGenre comment "Corresponds to 'genre' in the Ontology for Media Resources.".
- hasKeyword comment "Corresponds to 'keyword' in the Ontology for Media Resources.".
- hasLanguage comment "Corresponds to 'language' in the Ontology for Media Resources. The language used in the resource. A controlled vocabulary such as defined in BCP 47 SHOULD be used. This property can also be used to identify the presence of sign language (RFC 5646). By inheritance, the hasLanguage property applies indifferently at the media resource / fragment / track levels. Best practice recommends to use to best possible level of granularity fo describe the usage of language within a media resource including at fragment and track levels.".
- hasPolicy comment "Corresponds to 'policy' in the Ontology for Media Resources. Subproperties can be used to distinguish different values of 'policy.type'.".
- hasPublisher comment "Corresponds to 'publisher' in the Ontology for Media Resources.".
- hasRating comment "Corresponds to 'rating' in the Ontology for Media Resources.".
- hasRatingSystem comment "Corresponds to 'rating.type' in the Ontology for Media Resources.".
- hasRelatedImage comment "Corresponds to 'relation' and in the Ontology for Media Resources with a 'relation.type' meaning \"related image\".".
- hasRelatedLocation comment "Corresponds to 'location' in the Ontology for Media Resources. Subproperties are provided to specify, when possible, the relation between the media resource and the location.".
- hasRelatedResource comment "Corresponds to 'relation' and in the Ontology for Media Resources. Subproperties can be used to distinguish different values of 'relation.type'.".
- hasSigning comment "Corresponds to 'fragment' in the Ontology for Media Resources with a 'fragment.role' meaning \"signing\". This property can for example point to a spatial fragment or a VideoTrack. The sign language of the captioning track can be expressed by attaching a 'hasLanguage' property to the specific track.".
- hasSource comment "Corresponds to 'relation' and in the Ontology for Media Resources with a 'relation.type' meaning \"source\".".
- hasSubtitling comment "Corresponds to 'fragment' in the Ontology for Media Resources with a 'fragment.role' meaning \"subtitling\".".
- hasTargetAudience comment "Corresponds to 'targetAudience' in the Ontology for Media Resources.".
- hasTrack comment "Corresponds to 'fragment' in the Ontology for Media Resources with a 'fragment.role' meaning \"track\".".
- isCopyrightedBy comment "Corresponds to 'copyright.identifier' in the Ontology for Media Resources.".
- locationAltitude comment "Corresponds to 'location.altitude' in the Ontology for Media Resources.".
- locationLatitude comment "Corresponds to 'location.latitude' in the Ontology for Media Resources.".
- locationLongitude comment "Corresponds to 'location.longitude' in the Ontology for Media Resources.".
- locationName comment "Corresponds to 'location.name' in the Ontology for Media Resources.".
- locator comment "Corresponds to 'locator' in the Ontology for Media Resources.".
- mainOriginalTitle comment "Corresponds to 'title.title' in the Ontology for Media Resources with a 'title.type' meaning \"original\".".
- numberOfTracks comment "Corresponds to 'numTracks.number' in the Ontology for Media Resources. Subproperties can be used to distinguish different values of 'numTracks.type'.".
- ratingScaleMax comment "Corresponds to 'rating.max' in the Ontology for Media Resources.".
- ratingScaleMin comment "Corresponds to 'rating.min' in the Ontology for Media Resources.".
- ratingValue comment "Corresponds to 'rating.value' in the Ontology for Media Resources.".
- releaseDate comment "Corresponds to 'date.date' in the Ontology for Media Resources with a 'date.type' meaning \"releaseDate\".".
- samplingRate comment "Corresponds to 'samplingRate' in the Ontology for Media Resources, in samples per second.".
- title comment "Corresponds to 'title.title' in the Ontology for Media Resources. Subproperties can be used to distinguish different values of 'title.type'.".
- trackName comment "Corresponds to 'fragment.name' in the Ontology for Media Resources, for Track fragments.".
- oa comment "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.\n\nThis ontology is a non-normative OWL formalization of the textual OA specification at http://www.openannotation.org/spec/core/20130208/index.html\n\nNote that OWL imports are disabled in the published version in order to reduce external implications, improve OWL 2 Profile conformity and increase interoperability. Some OWL tools might thus misleadingly show this ontology as (re)defining properties like skos:prefLabel.".
- Annotation comment "Typically an Annotation has a single Body (oa:hasBody), which is the comment or other descriptive resource, and a single Target (oa:hasTarget) that the Body is somehow \"about\". The Body provides the information which is annotating the Target. \n\nThis \"aboutness\" may be further clarified or extended to notions such as classifying or identifying with oa:motivatedBy.".
- Choice comment "A multiplicity construct that conveys to a consuming application that it should select one of the constituent resources to display to the user, and not render/use all of them. \n\noa:Choice can be used as the object of the object of the oa:hasBody, oa:hasTarget, oa:hasSelector, oa:hasState, oa:styledBy and oa:hasScope relationships, \n\nThere MUST be 1 or more oa:item relationships for each oa:Choice.\n\nThere SHOULD be exactly 1 default relationship for each Choice.".
- Composite comment "A multiplicity construct that conveys to a consuming application that all of the constituent resources are required for the Annotation to be correctly interpreted. \n\noa:Composite can be used as the object of the object of the oa:hasBody, oa:hasTarget, oa:hasSelector, oa:hasState, oa:styledBy and oa:hasScope relationships, \n\nThere MUST be 2 or more oa:item relationships for each oa:Composite.".
- Motivation comment "The Motivation for creating an Annotation, indicated with oa:motivatedBy, is a reason for its creation, and might include things like oa:replying to another annotation, oa:commenting on a resource, or oa:linking to a related resource.\n\nEach Annotation SHOULD have at least one oa:motivatedBy relationship to an instance of oa:Motivation, which is a subClass of skos:Concept.".
- Selector comment "A resource which describes the segment of interest in a representation of a Source resource, indicated with oa:hasSelector from the Specific Resource. \n\nThis class is not used directly in Annotations, only its subclasses are.\n\nThe nature of the Selector will be dependent on the type of the representation for which the segment is conveyed. The specific type of selector should be indicated using a subclass of oa:Selector.\n\nThe Specifier's description MAY be conveyed as an external or embedded resource (cnt:Content), or as RDF properties within the graph. The description SHOULD use existing standards whenever possible. If the Specifier has an HTTP URI, then its description, and only its description, MUST be returned when the URI is dereferenced.".
- SpecificResource comment "A resource identifies part of another Source resource, a particular representation of a resource, a resource with styling hints for renders, or any combination of these. \n\nThe Specific Resource takes the role of oa:hasBody or oa:hasTarget in an oa:Annotation instead of the Source resource.\n\nThere MUST be exactly 1 oa:hasSource relationship associated with a Specific Resource.\n\nThere MUST be exactly 0 or 1 oa:hasSelector relationship associated with a Specific Resource.\n\nThere MAY be 0 or 1 oa:hasState relationship for each Specific Resource.\n\nIf the Specific Resource has an HTTP URI, then the exact segment of the Source resource that it identifies, and only the segment, MUST be returned when the URI is dereferenced. For example, if the segment of interest is a region of an image and the Specific Resource has an HTTP URI, then dereferencing it MUST return the selected region of the image as it was at the time when the annotation was created. Typically this would be a burden to support, and thus the Specific Resource SHOULD be identified by a globally unique URI, such as a UUID URN. If it is not considered important to allow other Annotations or systems to refer to the Specific Resource, then a blank node MAY be used instead.".
- State comment "A resource which describes how to retrieve an appropriate representation of the Source resource, indicated with oa:hasState from the Specific Resource.\n\nThis class is not used directly in Annotations, only its subclasses are.\n\nThe Specifier's description MAY be conveyed as an external or embedded resource (cnt:Content), or as RDF properties within the graph. The description SHOULD use existing standards whenever possible. If the Specifier has an HTTP URI, then its description, and only its description, MUST be returned when the URI is dereferenced.".
- Style comment "A resource which describes the style in which the selection or resource should be rendered, indicated with oa:styledBy from an oa:Annotation.\n\nThis class is not used directly in Annotations, only its subclasses are.\n\nThe content of the resource provides the rendering hints about the Annotation's constituent resources. \n\nThe Specifier's description MAY be conveyed as an external or embedded resource (cnt:Content), or as RDF properties within the graph. The description SHOULD use existing standards whenever possible. If the Specifier has an HTTP URI, then its description, and only its description, MUST be returned when the URI is dereferenced.".
- Tag comment "A class assigned to the Body when it is a tag, such as a embedded text string with cnt:chars.\n\nTags are typically keywords or labels, and used for organization, description or discovery of the resource being tagged. In the Semantic Web, URIs are used instead of strings to avoid the issue of polysemy where one word has multiple meanings, such usage MUST be indicated using the subclass oa:SemanticTag.\n\nAnnotations that tag resources, either with text or semantic tags, SHOULD also have the oa:tagging motivation to make the reason for the Annotation more clear to applications, and MAY have other motivations as well.".
- TimeState comment "A resource which describes how to retrieve a representation of the Source resource that is temporally appropriate for the Annotation.\n\nThere MUST be at least one of oa:cachedSource or oa:when specified. If there is more than 1, each gives an alternative copy of the representation.".
- annotatedBy comment "The object of the relationship is a resource that identifies the agent responsible for creating the Annotation. This may be either a human or software agent. \n\nThere SHOULD be exactly 1 oa:annotatedBy relationship per Annotation, but MAY be 0 or more than 1, as the Annotation may be anonymous, or multiple agents may have worked together on it.\n\nIt is RECOMMENDED to use these and other FOAF terms to describe agents: foaf:Person, prov:SoftwareAgent, foaf:Organization, foaf:name, foaf:mbox, foaf:openid, foaf:homepage".
- commenting comment "The motivation that represents a commentary about or review of the target resource(s). For example to provide a commentary about a particular PDF.".
- hasBody comment "It links to the description of vagueness/non-vagueness involved in the annotation.".
- hasBody comment "The relationship between oa:Annotation and body. The body is somehow \"about\" the oa:hasTarget of the annotation.\n\nThe Body may be of any media type, and contain any type of content. The Body SHOULD be identified by HTTP URIs unless they are embedded within the Annotation.\n\nEmbedded bodies SHOULD be instances of cnt:ContentAsText and embed their content with cnt:chars. They SHOULD declare their media type with dc:format, and MAY indicate their language using dc:language and a RFC-3066 language tag. \n\nThere is no OA class provided for \"Body\" as a body might be a target of a different annotation. However, there SHOULD be 1 or more content-based classes associated with the body resources of an Annotation, and the dctypes: vocabulary is recommended for this purpose, for instance dctypes:Text to declare textual content.\n".
- hasTarget comment "It links to the entity that has been object of the annotation.".