Designs dating name current
For example, take the National Science Foundation: NSF Online Documents the main page for starting to look for documents, is clearly not going to be something to trust to being there in a few years."cgi-bin" and "oldbrowse" and ".pl" all point to bits of how-we-do-it-now.And web servers just don't come out of the box with these features.When you want to create a new document, your editor asks you for a URI instead of telling you. At W3C we use server used for editing) which does track versions, and we are experimenting with document creation scripts. This is an outstanding reason, which applies for example to many W3C pages including this one: so do what I say, not what I do. They might have scrawled the URI in the margin of a letter to a friend.Whatever was that URI doing with John's name in it? This is exposing the mechanism of how you run your server.You change the mechanism (even keeping the content the same ) and whoops - all your URIs change.Except insolvency, nothing prevents the domain name owner from keeping the name.
Assumes that "money" will mean the same thing throughout the life of By contrast, if you use the page to find a document, you get first an equally bad Report of Working Group on Cryptology and Coding Theory Looking at this one, the "pubs/1998" header is going to give any future archive service a good clue that the old 1998 document classification scheme is in progress.Though in 2098 the document numbers might look different, I can imagine this URI still being valid, and the NSF or whatever carries on the archive not being at all embarrassed about it.That I can sympathize with - the W3C went through a period like that, when we had to carefully sift archival material for confidentiality before making the archives public. A lot of people don't know that servers such as Apache give you a lot of control over a flexible relationship between the URI of an object and where a file which represents it actually is in a file system.The solution is forethought - make sure you capture with every document its acceptable distribution, its creation date and ideally its expiry date. Think of the URI space as an abstract space, perfectly organized.