- From: Leigh Dodds <leigh.dodds@talis.com>
- Date: Wed, 8 Jul 2009 10:27:53 +0100
- To: Christopher St John <ckstjohn@gmail.com>
- Cc: public-lod@w3.org
Hi Christopher, 2009/7/7 Christopher St John <ckstjohn@gmail.com>: > On a vaguely similar topic as the .htaccess discussion, I ran into > a problem using a third party service to host some triples. I want > my URLs to be "pretty", and based on a domain that I control. > Something like: > > http://nrhpdata.daytripr.com/site/72001552 > > (which describes a United States National Register of Historic > Places site.) But when hosting at Talis[1] (or anywhere but > nrhpdata.daytripr.com) I end up with something like: > > http://api.talis.com/stores/ckstjohn-dev1/meta?about=http://nrhpdata.daytripr.com/site/72001552 The describe service (/meta?about=...) provides a default linked data description for any URI that is mentioned in a store. I agree that you don't necessarily want to expose the mechanism for generating the RDF to the consumer, and so generally speaking you'll want to hide this from consumers. The approach that we and some of the other people who are hosting data with us have taken is to proxy the urls through from a more specific domain. This is relatively easy to do, although obviously requires that you have some technical smarts in order to set things up. We should shortly be publishing some recipes to illustrate how thats done in a number of ways. We're also planning to roll-out domain hosting to help further lower the barrier to publishing linked data (in fact we set on of these up for a customer yesterday) The redirector also looks like a useful service! Let me know when you're ready to move the data to the Connected Commons :) Cheers, L. -- Leigh Dodds Programme Manager, Talis Platform Talis leigh.dodds@talis.com http://www.talis.com
Received on Wednesday, 8 July 2009 09:28:34 UTC