- From: David Wood <david@zepheira.com>
- Date: Fri, 20 Mar 2009 09:19:47 -0400
- To: Daniel Schwabe <dschwabe@inf.puc-rio.br>
- Cc: Kingsley Idehen <kidehen@openlinksw.com>, Knud Hinnerk Möller <knud.moeller@deri.org>, giovanni.tummarello@deri.org, Tom Heath <Tom.Heath@talis.com>, public-lod@w3.org
YOu may not be able to publish data in a "permanent" location, but you certainly can publish to a "permanent" URL - that is what PURLs are for. See http://purlz.org/ Regards, Dave On Mar 19, 2009, at 11:35 PM, Daniel Schwabe wrote: > Kingsley Idehen wrote: >> ... >>> - a stable service with a long-range commitment (as Daniel already >>> said) >> Yes, but is that worth the dislocation of the domain component of >> the HTTP identifier pointing back to me? > Sorry but I'm really confused here. I don't see how this applies to > the scenario where there is NO place where one can reliably publish > the data in a "permanent" form. > I can understand the scenario where I publish data using my own > URIs, and do a owl:sameas to Dogfood server URIs when applicable, > but if I can't guarantee a permanent service this doesn't help in > the long run. > If you are referring to the scenario where one does offer this > permanent publishing through one's own server, then it doesn't > matter if it's on the Dogfood server or not. > > Can you give me an example of a scenario of what you mean? > > Cheers > D > > >
Received on Friday, 20 March 2009 13:20:24 UTC