Jonathan Tweed wrote:
But the right thing to do in this example. A resource shouldn't have
different URLs depending on where you click from, so if you can't track
the outgoing link for some reason then a query parameter seems correct
to me.
Logging HTTP_REFERER isn't an option? Bummer-ouch. I'd have guessed it'd
be well worth capturing that information...
But as you already know, I do definitely prefer the much nicer
http://www.bbc.co.uk/programmes/b00b3zjr for the URL itself ;-)
Is a complete list of URLs public anywhere? :)
Otherwise, I'm sure if you ever expose a SPARQL endpoint, you'll be
seeing the likes of...
SELECT ?uri, ?t where
{
?uri :title ?t .
FILTER regex(str(?uri), "b00b3z") .
}
cheers,
Dan
--
http://danbri.org/
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
