> (Maintaining changes in URI philosophy and organization over tens to hundreds of years sounds like a maintenance nightmare.) I can't see why. You maintain a

> (Maintaining changes in URI philosophy and organization over tens to hundreds of years sounds like a maintenance nightmare.) I can't see why. You maintain a table of redirects. When you change the URI organization, which would break the URIs, you add the appropriate redirects to prevent that. Then, when you change it again, you just append the new redirects without removing the old ones. If necessary, resolve redirect chains server-side. The table may grow large, but it doesn't seem much more complicated than maintaining redirects across just two generations. Am I missing something?