4 ms·
I feel like the canonical URL for every page should be an UUID, with a database of which human readable document names maps to which UUID:s (and a history of ch
by Natanael_L 10y ago
I feel like the canonical URL for every page should be an UUID, with a database of which human readable document names maps to which UUID:s (and a history of changes should be provided via some tool in case somebody links using the human readable name and it gets replaced, perhaps via the sitemap page).
- tremon 10y agoI feel like the canonical URL for every page should be an UUID Please, not just a UUID. I'd like to know what to expect before clicking a link. I think nu.nl has found an interesting solution to this problem: every article has a canonical url of the form $section/$articlenumber/$title.html -- However, the "title" part (everything between the last slash and .html) is ignored by the server, and is pretty much free to alter as you like. All these three links resolve to the same article: http://www.nu.nl/buitenland/4263268/ http://www.nu.nl/buitenland/4263268/ http://www.nu.nl/buitenland/4263268/amerikaanse-stad-moet-stoppen-met-rassenscheiding-scholen.html http://www.nu.nl/buitenland/4263268/amerikaanse-stad-moet-st... http://www.nu.nl/buitenland/4263268/judge-orders-cleveland-ms-to-merge-segregated-schools.html http://www.nu.nl/buitenland/4263268/judge-orders-cleveland-m...
- Natanael_L 10y agoI almost felt like adding that. I'm guessing appending a title after a # character would be the most technically simple solution?
- tremon 10y agoTechnically simple, yes, but semantically different. A link /path/to/page#title would imply (at least to me) that the page holds more information than only the #title article.