- From: Janne Saarela <janne.saarela@profium.com>
- Date: Mon, 15 Mar 2004 08:49:25 +0200
- To: RDF Data Access Working Group <public-rdf-dawg@w3.org>
- Cc: Eric Prud'hommeaux <eric@w3.org>
> One could get the answer:
>
> { ?tune vcard:FN "L'amour de loin".
> ?tune mb:genre ?genre. } => { <> answer (?genre) }.
>
> and the presentation information:
>
> { mn:genre rdfs:label ?label } => { <> answer (?label) }.
>
> separately. Is it a common case that the client asking
> about an mb:genre property won't know how to display it?
I agree that making separate queries will do the trick
but it will make XSLT development trickier.
What we need to build to our customers is query result
visualisation using XSLT from RDF/XML to (X)HTML and
other markup.
For this purpose we've noticed that we need
access to labels/comments from XSLT. If they are
not explicitly requested in the original query, alternatives are:
a) make other queries for them like you suggested which
makes xslt more inefficient.
b) include the natural language descriptions in the XSLT
(replicating strings from RDFS to XSLT, not very nice)
Therefore we had to introduce support for syntactic sugar
ourselves to include rdfs:label and rdfs:comment to
query results without query explicitly asking for them.
Janne
--
Janne Saarela <janne.saarela@profium.com>
Profium, Lars Sonckin kaari 12, 02600 Espoo, Finland
Tel. +358 (0)9 855 98 000 Fax. +358 (0)9 855 98 002
Mob. +358 (0)40 508 4767 Internet: http://www.profium.com
Received on Monday, 15 March 2004 02:49:45 UTC