- From: Peter Ansell <ansell.peter@gmail.com>
- Date: Thu, 3 May 2012 09:00:43 +1000
- To: Bob DuCharme <bob@snee.com>
- Cc: public-esw-thes@w3.org
Hi Bob, That is unusual that the SKOS spec did not allow for xsd:string literals at the time. People have been typing string literals as xsd:string since well before SKOS came around. If one interprets the SKOS spec liberally with respect to RDF-1.1 then it would make sense to simply read "plain literals" as "xsd:string typed literals". The basis for this pragmatic change would be that "plain literals" will have no meaning soon, even if RDF-1.0 documents are still going to be readable by RDF-1.1 parsers. Is it a big issue to change the SKOS spec? Cheers, Peter On 2 May 2012 23:00, Bob DuCharme <bob@snee.com> wrote: > At http://www.w3.org/TR/2009/REC-skos-reference-20090818/#L1329 the SKOS > spec says the following for constraint S12: "The rdfs:range of each of > skos:prefLabel, skos:altLabel and skos:hiddenLabel is the class of RDF plain > literals." As I understand this, the triple {:myConcept1 skos:prefLabel "my > home page"^^xsd:string} violates this constraint, but wouldn't if the object > was just "my home page". > > At http://www.w3.org/TR/rdf11-concepts/#section-Graph-Literal, the RDF 1.1 > Concepts and Abstract Syntax says "This section is a major departure from > RDF 2004 as simple literals are now treated as syntactic sugar for > xsd:string typed literals." > > If simple literals are treated as xsd:string typed literals, what would this > mean for constraint S12? > > thanks, > > Bob > > > >
Received on Wednesday, 2 May 2012 23:01:13 UTC