I mean that's better in some ways certainly, but you'd probably also want to create some sort of canonical identifier that would represent the band so that if anyone was doing anything programmatically across the web they would be able to connect the two concepts. I mean, YOU might know which Bliss is #1 and which is #2, but someone else might come to very different conclusions.

I mean, you can take this to excess, clearly, but I think a good proportion of the time in areas where there are different spellings, namespace collisions and the like, that I'd prefer to stick an informationless identifier at the end of the URL to represent the specific thing.

OR I'd go for something much more interesting.

Given that Wikipedia has pages on most of these artists and that—by its nature—it has to have a separate page for each one of them, then you can view that as a well maintained centralised controlled vocabulary. I'd probably go with using their URLs as some kind of identifier and perhaps even translating their URL conventions locally.

Having said htat, they don't have any of the three artists called 'Bliss' so maybe that wouldn't work.

On 16 Jul 2007, at 16:56, James Cridland wrote:

In terms of music artists (I rediscovered the great band Bliss this weekend, and found three different Bliss's within the same last.fm page, of which I was only interested in one, and the pictures and everything is all really very messed-up) then perhaps disambiguation pages work like wikis.

www.bbc.co.uk/music/artist/bliss/ is a disambiguation page, leading to
www.bbc.co.uk/music/artist/bliss_1/
www.bbc.co.uk/music/artist/bliss_2/
...etc

This also has the benefit that you don't need a database call to link to an artist page on /music - just call str_replace(" ","_",strtolower($artist)); instead. Not that it's quite that easy, of course.


-
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/[email protected]/

Reply via email to