W3C home > Mailing lists > Public > public-sparql-dev@w3.org > April to June 2006

tuple identifiers

From: Eric Prud'hommeaux <eric@w3.org>
Date: Sat, 10 Jun 2006 19:42:53 +0200
To: Chris Bizer <bizer@zedat.fu-berlin.de>
Cc: Dan Connolly <connolly@w3.org>, public-sparql-dev@w3.org
Message-ID: <20060610174253.GC13928@w3.org>

On Sat, Jun 10, 2006 at 05:30:34PM +0200, Chris Bizer wrote:
> I think the discussion about browseable http URIs for database-backed resources and Tim's comment on tabulator is very important. Right now D2R server doesn't allow you to dereference dynamically created URI, but all the information that is needed to make URIs dereference-able is already in the mapping. So it should be possible to make URIs browseable by using a URI creation pattern like http://D2RserverURL/resource/classMapID/PrimaryKey. We will add this feature to next D2R server release and hack up a demo which shows how tabulator is used to browse a database. 

I've experimented with using tuple identifiers like
  <service uri> + SELECT+%3Fp+%3Fo+%7B%3Fs+%3COrders.pk%3E+7%3B+%3Fp+%3Fo%7D
  (url-encoding of "SELECT ?p ?o {?s <Orders.pk> 7; ?p ?o}")
to identify the Orders tuple with pk=7. This ends up being much longer and a little harder to process than something like
  <service uri> + Orders.pk=7 *
but also does not require any extra service point to honor the "tell me about this tuple" queries.

* this is a somewhat simplified example as I prefer to use unique keys that might service a translation into a different (type of) database.

home-office: +1.617.395.1213 (usually 900-2300 CET)
cell:        +81.90.6533.3882

Feel free to forward this message to any list for any purpose other than
email address distribution.
Received on Saturday, 10 June 2006 17:41:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:15:49 UTC