- From: Thomas B. Passin <tpassin@comcast.net>
- Date: Thu, 06 Jun 2002 08:31:18 -0400
- To: RDF Interest <www-rdf-interest@w3.org>
Thanks, Patrick. Tom P [Patrick Stickler] > On 2002-06-05 16:14, "ext Thomas B. Passin" <tpassin@comcast.net> wrote: ... > > I could also see creating subproperties of rdfs:label, like rdfs:label-eng, > > but that wasn't done above either. > > > > So how does this work? > > At the moment (and I can't say this is my preference) literals in > RDF are structured objects, not just strings. They are comprised of > a single bit, which designates the parseType, the actual string value, > and a language tag, if specified by xml:lang. Thus, the triples produced > by the above RDF/XML are (using qnames for clarity ;-) > > <voc:blackeye.vsaa.lv/cv/sex/male> rdf:type cv:Sex . > <voc:blackeye.vsaa.lv/cv/sex/male> rdfs:label "Male"-en . > <voc:blackeye.vsaa.lv/cv/sex/male> rdfs:label "Mies"-fi . > > Now, applications are then supposed to filter/select literal values > based on language. > > There are some folks (myself included ;-) who would prefer for > the xml:lang attribute to be treated the same as any arbitrary > property, namely resulting in a blank node with the xml:lang attribute > as a property. Thus: > > <voc:blackeye.vsaa.lv/cv/sex/male> rdf:type cv:Sex . > <voc:blackeye.vsaa.lv/cv/sex/male> rdfs:label _:x . > _:x rdf:value "Male" . > _:x xml:lang "en" . > <voc:blackeye.vsaa.lv/cv/sex/male> rdfs:label _:y . > _:y rdf:value "Mies" . > _:y xml:lang "fi" . > > which would expose the language qualification to RDF > applications in a more native manner. > > Still, in either case, what you have are multiple language > qualified labels which constitute an implicit selection set, > from which an application can choose the preferred one. Yet > the identity of the controlled value itself is canonical. > > >
Received on Thursday, 6 June 2002 08:30:22 UTC