On Fri, Dec 18, 2009 at 09:30:51AM +0000, Kake L Pugh
On Thu 17 Dec 2009, Dominic Hargreaves
[snip many other useful bits of reply from you]
should we take it down altogether? I don't feel able to; as
of community provided data we should try and keep it relevant and
but if we can't do that shouldn't we at least retain it so that
parts are still accessible?
I have trouble finding any useful parts in it, to be honest.
I do get your point about community-provided data - it _is_ generally
somewhat unethical to solicit data from people, give them the
that their data is safe, and then remove their access to it - but the
reason I brought this up at the time when I did bring it up is that
not sure there's anyone left who actually cares about OGL's data.
I'm starting to agree. And no-one on the OGL list replied when I
dropped the hint about getting rid of it at
so I will implement the read-only bit as soon as I get a round tuit
(if someone reading this fancies a little coding, then a patch to
OpenGuides to disable all the writable features would be great :)
I'll probably also put robot meta tags to stop indexing.
Then if noone has popped up a few months after that I'll think about
taking the whole thing down.
I'm interested in grabbing a copy of the RDF export of the data (and
possibly, a dump of the DB history's sake), so that it can be reused
in Semantic Web projects (initially here at University of Southampton).
There is a bit of a bug preventing me from doing so at the moment -
ampersands are not properly escaped in RDF.pm - It looks like they are
not transformed by the escaping module (I think because it's designed
to escape HTML entities, not for XML serialisation).
Is there any chance this could be fixed on OGL so that I can crawl
download the RDF?