Matches in LOV for { ?s ?p Todo: \nNot modelled but requiring further extension:\n\n- CustomTermAttribute : \n Best practice would be to define custom RDF data-type properties taking plain literal values. The property name depends on the customAttributeType.\n\n- CustomConceptAttribute :\n Best practice would be to define custom RDF data-type properties taking plain literal values. The property name depends on the customAttributeType.\n\n- refersTo (reference from within a note to a concept or label/term:\n May be an embedded and tagged link in the note value (e.g., as done for EuroVoc http://eurovoc.europa.eu/).\n\n- CustomNote :\n Depending noteType a new custom property should be defined as a sub-property of skos:note (consider applicability of: skos:changeNote and skos:example)\n \n - BTG/NTG - BTP/NTP - BTI/NTI :\n Currently these are only defined as direct (one-step) sub-properties of skos:broader / skos:narrower.\n\nSome constraints currently expressed only in natural language (in rdfs:comment) may be formally expressed as OWL(2) axioms.\n\nWe have postponed the implementation of the iso-thes properties mentioned in the VersionHistory section of the mapping documentation.. }
Showing items 1 to 1 of
1
with 100 items per page.
- skos-thes toDoList "Todo: \nNot modelled but requiring further extension:\n\n- CustomTermAttribute : \n Best practice would be to define custom RDF data-type properties taking plain literal values. The property name depends on the customAttributeType.\n\n- CustomConceptAttribute :\n Best practice would be to define custom RDF data-type properties taking plain literal values. The property name depends on the customAttributeType.\n\n- refersTo (reference from within a note to a concept or label/term:\n May be an embedded and tagged link in the note value (e.g., as done for EuroVoc http://eurovoc.europa.eu/).\n\n- CustomNote :\n Depending noteType a new custom property should be defined as a sub-property of skos:note (consider applicability of: skos:changeNote and skos:example)\n \n - BTG/NTG - BTP/NTP - BTI/NTI :\n Currently these are only defined as direct (one-step) sub-properties of skos:broader / skos:narrower.\n\nSome constraints currently expressed only in natural language (in rdfs:comment) may be formally expressed as OWL(2) axioms.\n\nWe have postponed the implementation of the iso-thes properties mentioned in the VersionHistory section of the mapping documentation.".