2 Feb
2004
2 Feb
'04
10:40 a.m.
On Mon, Feb 02, 2004 at 09:08:05AM +0000, Steve Harris wrote:
That is pretty interesting.
I hadn't considered that *I* might be the 3rd party :-)
--
Paul Winkler
http://www.slinkp.com
Look! Up in the sky! It's THE SPAMSTRANGLING FOOD!
(random hero from isometric.spaceninja.com)
The URIs do not have to be resolvable. Thier just
unique-ish identifiers.
The fact that they sometimes look like URLs is a pain. I think thier
should have been a 'namespace:' URI prefix, but its a bit late now.
So to answer your question, dont update your URIs.
ok. I have to say that's pretty damn weird.
Providing RDF data representing the things in the site
is the most
important, but I now find it easier to to run sites off RDF because the
site code tends to depend less on the data than with SQL. I guess it
depends how much SQL youve done
near zero
and wether you are willing to change.
I do web development with Zope. My site code never depends on
the data store :-)
AFAICT the
advantages lie with the former. Could you give an
example of such a third-party app? I'm not really coming up with
compelling use cases.
OK, take the LAD conference website. They might want to include a short
bio of each presenter - they can take all the project related data from
<insert name of new site> and add a few paras of text. After the event has
run they could publish photos on the website and mark up whos shown in
each photo, and publish the photo and bio stuff (against the same URIs),
the original site can then load this new stuff into thier KB and suddenly
you have a whole load of new data. Its like data for free.
You /can/ do all this stuff by web-scraping HTML into your internal
database format and resyncing with the source site every week, but who
would bother?
As an example, look at my entry on works KB:
http://triplestore.aktors.org/browse/?resource=http%3A%2F%2Fwww.ecs.soton.a…
I hardly wrote any of that, most of it came from other sources, eg.
someones online photo album and random databases published as RDF, click
"show sources" (top right) to see where it all came from.