Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- altLabel comment "Simple or basic super property of ISO hasNonPreferredLabel\n\nApplies if the value of \"hasNonPreferredLabel\" is of class SimpleNonPreferredTerm with the Boolean attribute \"hidden\" either absent or with value false.".
- altLabel comment "The range of skos:altLabel is the class of RDF plain literals.".
- altLabel comment "skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.".
- broader comment "Broader concepts are typically rendered as parents in a concept hierarchy (tree).".
- broaderTransitive comment "Can be used to derive ISO hasTopConcept (which is different from skos:hasTopConcept).\n\nThe ISO hasTopConcept can be derived in SKOS from skos:broaderTransitive where the object of skos:broaderTransitive is a concept having the property skos:topConceptOf (i.e., a ThesaurusConcept having topConcept = true).".
- exactMatch comment "skos:exactMatch is disjoint with each of the properties skos:broadMatch and skos:relatedMatch.".
- hiddenLabel comment "Simple or basic super property of ISO hasNonPreferredLabel\n\nApplies if the value of \"hasNonPreferredLabel\" is of class SimpleNonPreferredTerm with the Boolean attribute \"hidden\" having value true.".
- hiddenLabel comment "The range of skos:hiddenLabel is the class of RDF plain literals.".
- hiddenLabel comment "skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.".
- inScheme comment "Super property of ISO isPartOf\n\nApplies to any ISO 25964 \"isPartOf\" relation that targets the Thesaurus. Subjects of the skos:inScheme statements can be ISO 25964’s ThesaurusConcept, ConceptGroup, and ThesaurusArray.\n\nOnly applies to ISO 25964 \"contains\" statements having a Thesaurus [ConceptScheme] as subject.".
- inScheme comment "This property expresses the fact that a concept is a part of a scheme.".
- mappingRelation comment "These concept mapping relations mirror semantic relations, and the data model defined below is similar (with the exception of skos:exactMatch) to the data model defined for semantic relations. A distinct vocabulary is provided for concept mapping relations, to provide a convenient way to differentiate links within a concept scheme from links between concept schemes. However, this pattern of usage is not a formal requirement of the SKOS data model, and relies on informal definitions of best practice.".
- member comment "ISO\n- hasMemberArray\n- hasMemberConcept\n- hasAsMember\nNote: SKOS S39 (any concept in a List of a skos:memberList is also a value of skos:member).\n\nBy definition, used to represent members of a thesaurus Array or of a thesaurus Group.\n\nAn Array may have as members thesaurus Concepts or other thesaurus Arrays.\n\nThesaurus Group members are thesaurus Concepts.".
- narrower comment "Narrower concepts are typically rendered as children in a concept hierarchy (tree).".
- narrowerTransitive comment "Can be used to derive ISO isTopConceptOf (which is different from skos:isTopConceptOf).\n\nThe ISO isTopConceptOf can be derived in SKOS from skos:narrowerTransitive where the skos:narrowerTransitive has as subject a concept that is object of a skos:hasTopConcept statement (i.e., a ThesaurusConcept having topConcept = true).".
- notation comment "Best practice in SKOS is to (RDF) type the notation value object. This allows multiple notation value types for the same concept or term to be distinguished. \n\nNote: In ISO 25964-1, such typing is implicit in the thesaurus or it is part of the \"notation\" value.".
- notation comment "Used to store the values of feature codes".
- note comment "ISO refersTo is not mapped.\n\nWork is ongoing in the RDF group to type the content explicitly as HTML or XML in RDF1.1 (http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html#section-html). This would allow embedding relevant hyperlinks in notes.\n\nMay be an embedded and tagged link in the note value (e.g., as done for EuroVoc).\n\n\nIn ISO 25964, some types of Note are associated with concepts, others with terms. In SKOS, all documentation notes are associated with concepts.\n\nIn basic SKOS, notes are represented using simple annotation properties, which type captures the note type. However the SKOS annotation properties can also be used with structured representation of notes as fully-fledged resources. See http://www.w3.org/TR/skos-primer/#secdocumentation and http://www.w3.org/TR/skos-primer/#secadvanceddocumentation for examples of both approaches.\n\nWithin a thesaurus the application of notes to concept and term is more restrictive than in SKOS.\n\nA note may have some structure or formatting. In general, this can be modelled using rdf:value (to represent lexicalValue)\n\nThe language should be held in rdf:value. If this is an XMLLiteral, the language shall also be made available using dc:language (or dct:language).\n\nNote: Work is ongoing in the RDF group to type the content explicitly as HTML or XML In RDF1.1 (http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html#section-html). This would allow embedding relevant hyperlinks in notes.\n\nAdditional attributes can be added to the note structure:\n- dct:created\n- dct:modified".
- prefLabel comment "A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag.".
- prefLabel comment "Simple super property of ISO hasPreferredLabel\n\nBasic SKOS allows labels (as simple literals) to be attached directly to Concepts using skos:prefLabel; this is the preferred simple scenario where label relations are not explicit.".
- prefLabel comment "The range of skos:prefLabel is the class of RDF plain literals.".
- prefLabel comment "skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise\n disjoint properties.".
- related comment "skos:related is disjoint with skos:broaderTransitive".
- Graph comment "An RDF graph (with intensional semantics).".
- Authority comment "An authority, or origin, of a graph; such as a person or company.".
- SignatureMethod comment "A method used to construct a signature used to authenticate a graph.".
- Warrant comment "A relationship between an authority and a graph, in which the authority is in\nsome way an origin of that graph. Warrants may include a digital signature of\nthe graph by the authority.".
- ClassList comment "This is a convenience class for the OWL specification of Fresnel (an rdf:List of resource selectors only).".
- ConvenienceToken comment "Abstract class for expressing shorthands a browser must understand how to expand.".
- ConvienceProperty comment "Abstract class of pseudo properties.".
- Format comment "A Fresnel format class for displaying RDF data; the domain property can be only one of :formatDomain, :classFormatDomain, :instanceFormatDomain.".
- FormatDescription comment "Description of fresnel:Format content separators; super class, not to be used directly.".
- FormatDescriptionNoSubstitution comment "Description of fresnel:Format content separators only; contentNoValue will not be recognized in conjunction with this class.".
- FormatDescriptionSubstitution comment "Description of fresnel:Format content separators and content replacement if values are missing.".
- Group comment "A Fresnel Group is used for grouping formats and lenses together.".
- HidePropertyList comment "This is a convenience class for the OWL specification of Fresnel.".
- LabellingFormat comment "Abstract superclass of all labelling formats.".
- Lens comment "Lens for viewing RDF data.".
- PropertyDescription comment "More detailed description of the property, e.g. for specifing sublenses or merging properties.".
- PropertySet comment "Abstract class of property sets.".
- PropertyValueStyle comment "Abstract superclass of all property value display styles.".
- Purpose comment "Propose in which a specific lens might be appropriate.".
- ShowPropertyList comment "This is a convenience class for the OWL specification of Fresnel.".
- classFormatDomain comment "The Format should be applied to instances of this class.".
- classLensDomain comment "Specifies that the lens is usable for the specified class and its subclasses.".
- contentAfter comment "Content that should be displayed before the content of the current box.".
- contentBefore comment "Content that should be displayed before the content of the current box.".
- contentFirst comment "Content that should be displayed before the content of the first element in a list of boxes; takes over the first :contentBefore element in case of a conflict.".
- contentLast comment "Content that should be displayed after the content of the last element in a list of boxes; takes over the last :contentAfter element in case of a conflict.".
- contentNoValue comment "Content that should be displayed if the current property is missing.".
- depth comment "Closure mechanism, if lenses are recursively used; the recursive depth limit.".
- group comment "Specifies the format group to which a format or a lens belongs.".
- hideProperties comment "List of all properties which should be hidden. Must be used together with 'fresnel:showProperties fresnel:allProperties.'".
- image comment "Show the property value as an image, such as PNG or JPEG .".
- instanceFormatDomain comment "The Format should be applied to this set of instances.".
- instanceLensDomain comment "The lens is usable for the specified set of instances.".
- label comment "Specifies how a property is labelled (only works in conjunction with propertyFormatDomain).".
- labelFormat comment "Assign content formatting to a set of labels (theoretically, this does not make much sense, but it does round out the set of formatting properties; only works in conjunction with propertyFormatDomain).".
- labelStyle comment "Attaching a symbol appropriate for styling labels (only works in conjunction with propertyFormatDomain).".
- none comment "Do not show any label for the property.".
- primaryClasses comment "Specifies the classes that should be considered primaries, or first class results; secondary resources not matching the primaries will only be shown as sublenses. The range is a list of resource selectors.".
- property comment "The RDF property, which is described.".
- propertyFormat comment "Assign content formatting to a set of properties (only works in conjunction with propertyFormatDomain).".
- propertyFormatDomain comment "The Format should be used for the specified properties.".
- propertyStyle comment "Attaching a symbol appropriate for styling properties (only works in conjunction with propertyFormatDomain).".
- purpose comment "Specifies a purpose for which a lens or format might be appropriate.".
- replacedResource comment "Any kind of retrievable resource like an image, audio or video that should be displayed as property value. The browser should try retrieve the resource and show it instead of the property value URI. The browser has to negotiate an appropriate media type with the server using HTTP content negotiation.".
- resourceFormat comment "Assign content formatting to a set of resources (only works in conjunction with classFormatDomain and instanceFormatDomain).".
- resourceStyle comment "Attaching a symbol appropriate for styling a resource. resourceStyle is ignored if not used with :classFormatDomain or :instanceFormatDomain.".
- show comment "Show the RDFS Label of the property. This is the default and doesn't have to be declared.".
- showProperties comment "List of all properties which should be shown.".
- sublens comment "Sublens which should be used for displaying property values.".
- uri comment "Show the property value as an URI.".
- use comment "Explicit definition of fresnel:Group containing formats that should be used to render the lens or sublens.".
- value comment "Specifies how a property value is displayed (only works in conjunction with propertyFormatDomain).".
- valueFormat comment "Assign content formatting to a set of values (only works in conjunction with propertyFormatDomain).".
- valueStyle comment "Attaching a symbol appropriate for styling the values of a property (only works in conjunction with propertyFormatDomain).".
- ReviewStatus comment "A particular stage in a review process".
- TestCase comment "A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement".
- accepted comment "the item has gone through a first review, which shows it as valid for further processing".
- approved comment "the item has gone through the review process and was approved".
- assigned comment "a more specific review of the item has been assigned to someone".
- expectedResults comment "The results that a conformant implementation is expected to produce when this test is executed".
- informationResourceInput comment "Information Resource (e.g. a file) used as input for the test case".
- informationResourceInput comment "Information Resource (e.g. a file) used as input for the test case".
- input comment "Parameters or data that are needed for the test execution.".
- onhold comment "the item had already gone through the review process, but the results of the review need to be re-assessed due to new input".
- rejected comment "the item has gone through the review process and was rejected".
- specificationReference comment "a description or a link of what part of which specification lead to the creation of this test case".
- unreviewed comment "the item has been proposed, but hasn't been reviewed (e.g. for completeness) yet".
- ContentTypeGenericResource comment "A resource which may have representations in\n many different Content-Types.".
- ContentTypeSpecificResource comment "A resource of which all representations are in the\n\t\tsame Internet media type, or 'Content-Type'.".
- FixedResource comment "A resource whose representation type and content will not\n\t change under any circumstances.".
- InformationResource comment "An Information Resource is defined by the Architecture of\n\t the WWW.".
- LanguageGenericResource comment "A resource defiend without constraint as to\n\tthe particular natural language in which it\n maight be expressed.".
- LanguageSpecificResource comment "A resource of which all representations are in the\n\t\tsame natural language.".
- TimeGenericResource comment "A Information Resource which may have many versions,\n and therfore representations of the resource at different times may vary.".
- TimeSpecificResource comment "A resource of which all representations are in the\n\t\tsame version. Representations of the resource will\n not change as a result of th resource neing updated to a\n version with time. The dates of creation and\n of last modification of such a resource would be\n expected to be the same.".
- sameWorkAs comment "The equivalence relation linking all versions of a work,\n specific or generic along various axes.".
- timeGeneric comment "The related resource which for this time-sepcific resource\n is the related time-generic resource.\n A representation of the time-generic resource may be expected to be\n the most recent time-specific resource at the time of\n the representation.".