> One may also consider one of the two articles to be the translation of > the other (which is what I plan on doing for my project), thus > considering the both to be different articles and having no > information on the language in the url. > So something like this : > "/articles/topic/subtopic/article-title-in-english/display/" > "/articles/topic/subtopic/article-title-in-dutch/display/"
Right. I would go one step further. The REST philosophy says that the URL is an important part of the user interface: it should be meaningful and understandable. If so, the whole URL needs to be expressed in the user language. Therefore, if an English-speaking user sees the URL: /articles/prog-langs/python/indentation-stroke-of-genius/ (no /display/ needed at the end) an Italian-speaking one should see: /articoli/linguaggi-programmazione/python/indentazione-colpo-di-genio/ While the two URLs are the same article expressed in two different human languages, I think that the mere translation process makes the two things different enough that it's not the same resource anymore, so different URLs are warranted. Furthermore, each article translation may have different comments, furthermore differentiating them. -- Nicola Larosa - http://www.tekNico.net/ Baby, I can tell you there's no easy way out Lost inside of dreams that guide you on Baby, I can tell you there's no easy way out Soon the guiding moonlight will be gone -- David Sylvian, Silver Moon, Gone to Earth, 1986 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
