On Thu 15 Mar 2007, Tom Heath tom.heath@gmail.com wrote:
The URI that you plugged in is the URI of a "wiki entry about Angel", SE16 4NB, not the URI of the thing itself.
Ah-ha, thanks, I'd not spotted that. Perhaps a quick fix would be to have the "RDF/XML" link in the navbar point to the URI of the thing itself, rather than the URI of the entry-about-the-thing? That seems to make more sense to me, in terms of doing the Expected Thing. After all, the interesting thing is the, well, thing, not the entry about it.
Lots of great ideas in your mail - thank you! I started going through and replying bit by bit, but pretty much everything was "yes, that sounds cool, we should be able to do that". So I'll just say it once, and it generally applies to the whole lot (some bits of it would, of course, take more work than others).
Do you think you'd be able to take the RDF output for that page, and edit in the stuff that you'd like to see there? Just so we have a reference for what we're aiming for. It's a lot easier to understand things when there's a concrete example.
Regarding "pretty" URIs, I'm not sure we should be trying to incorporate URI rewriting within OpenGuides itself - and consequently I don't want us to depend on it to the extent of writing our RDF on the assumption that it's there. Does a machine that's processing some RDF actually care that a URI isn't very attractive? And can't we use something like the rdf:Descriptionrdfs:label thingy in your Far
From The Madding Crowd RDF to protect people using browsers like the
Disco one from having to look at ugly URIs?
Incidentally, an idea for other Guide admins - Bob made this for me: http://london.randomness.org.uk/goodbeerguide which is memorable and easy to tell people (I just typed it in this mail, didn't go and look it up). Simple things like this can make it easier to persuade people to go and look at your Guide.
Kake