W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > January to March 2004

Re: JS-2: implicit inclusion of annotations

From: Eric Prud'hommeaux <eric@w3.org>
Date: Sun, 14 Mar 2004 23:01:37 -0500
To: Janne Saarela <janne.saarela@profium.com>
Cc: RDF Data Access Working Group <public-rdf-dawg@w3.org>
Message-ID: <20040315040137.GA8263@w3.org>

On Thu, Mar 11, 2004 at 10:38:21PM +0200, Janne Saarela wrote:
> == Task & Roles
> A client software wishes to connect to server software
> to retrieve RDF via a query. The client wishes to render
> the query result for the user using XSLT. The XSL
> transformation should be self-sufficient i.e. no more
> queries are needed from the XSL itself to render
> human readable strings.
> == Description
> A client requests for music:genre property value
> from a server. Here, the music:genre value will be a
> resource type of object.
> The client uses XSLT to transform the query result
> into XHTML. For a Finnish user, an object value
> 'http://music.org/genres/Classical' should be rendered as
> string 'Klassinen musiikki' and for English speaking
> users as 'Classic music'. In addition, the property
> 'music:genre' should be rendered as 'tyylilaji' for
> Finnish users and as 'genre' for English speaking users.
> These strings might be available via schema annotations
> using primitives such as  rdfs:label or rdfs:comment.
> Instead of making a complex query (at the end of the
> day) which returns rdfs:label and rdfs:comment for
> the resource values and for properties, a syntactic
> sugar would be useful to make the annotations available
> for all of them in the query result.

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 think this presentation request comes up more commonly
when the client doesn't know exactly what properties it
is looking for:

  { ?thingy vcard:FN "L'amour de loin".
    ?thingy ?p       ?v. } => { <> answer (?p ?v) }.

A query language that expressed variable predicates would
allow for these queries to be smushed together:

  { ?thingy vcard:FN   "L'amour de loin".
    ?thingy ?p         ?v.
    ?p      rdfs:label ?label } => { <> answer (?p ?v ?label) }.

office: +81.466.49.1170 W3C, Keio Research Institute at SFC,
                        Shonan Fujisawa Campus, Keio University,
                        5322 Endo, Fujisawa, Kanagawa 252-8520
        +1.617.258.5741 NE43-344, MIT, Cambridge, MA 02144 USA
cell:   +1.857.222.5741 (does not work in Asia)

Feel free to forward this message to any list for any purpose other than
email address distribution.
Received on Sunday, 14 March 2004 23:01:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:00:24 UTC