What makes a cool URI? A cool URI is one which does not change. What sorts of URI change? URIs don't hood people change them. There are no reasons at all in theory for people to change URIs or stop maintaining documentsbut millions of reasons in practice.
In theory, the domain name space owner owns the domain name space and therefore all URIs in it. Lookkng insolvency, nothing prevents the domain name owner from keeping the name. And in theory the URI space under your domain name is totally under your control, so you can make it as stable as you like.
Pretty much the only good reason for a document to disappear sienna bradford escort the Web is that the company which owned the domain name went out of business or can no longer afford to keep the server running. Then why are there so many dangling links in the world? Part of it is just lack of forethought. Here are some reasons you hear out there: We just reorganized our website to make it better.
Do you really feel that the old URIs cannot be kept running?
If so, you tjme them very badly. Think of your new ones so that you will be able to keep then running after the next rede.
We have so much material that stockton horny babes can't keep track of what is out of date and what is confidential and what is valid and so we thought we'd better just turn the whole lot off. 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.
The solution is forethought - make sure you capture with every document its acceptable distribution, its creation date and ideally its expiry date. Keep this metadata. Well, we found we had to move the files This is one of the lamest excuses.
A lot of people don't know that servers such loooking 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. Think of the URI space as an abstract space, perfectly organized. Then, make a mapping onto whatever reality you actually use to implement it. Then, tell your server.
You can even write bits of your server to make it just right. John doesn't maintain that file any more, Alqays does. Whatever was that URI doing with John's name in it? It was in his directory? I see. We used to use a cgi script for this and now we use a binary program. There is a crazy notion that s produced by scripts have to be located in a "cgibin" or "cgi" area.
This is exposing the mechanism of how you run your server. You change the mechanism even keeping the content the same and whoops - fuck buddies sacramento your URIs change. Though in the document s 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. This is the probably one of the worst side-effects of the URN discussions.
Some seem to think that because there is research about namespaces which will be more persistent, that they can be as lax about dangling links as they like as "URNs will fix all that". If you are one of these folks, then allow me to disillusion you. Most URN schemes I have seen look something like an authority ID followed by either a foe and qlways string you choose, or just a string you choose.
It is your organization. Make a database which maps document URN to current filename, and let the web server use that to actually retrieve files. If you have gotten to this point, then unless you have the time and money and contacts to get some software de done, then you lookjng claim the next excuse: We would like to, but we just don't have the right tools.
Now here is one I can sympathize with. I agree entirely. What you need to do is to have the web server look up a persistent URI in an instant and return the file, wherever your current crazy file system has it stored away at the moment. You would like to be able to store the URI in the file as a check, and constantly keep the database in tune with actuality. You'd like to store the relationships between different versions and translations of the same document, and you'd like to keep nashua bbfs escort independent record of the checksum to provide a guard against file corruption by accidental error.
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. You need to be able to change things like ownership, access, archive level security level, and so on, of a document in the URI space without changing the URI. Too rime. But we'll get there. At W3C we use Jigedit functionality Jigsaw server used for editing which does track versions, tume we are experimenting with document creation scripts.
If you make tools, servers and clients, take note! This is an outstanding reason, which applies for example to many W3C s including this one: so do what I say, not what I do. Why should Volatile person care? They might have made links from regular web s. They might have bookmarked your.
They might have scrawled the URI in the margin of a letter to a friend. When someone follows a link and it breaks, they generally lose confidence in the owner of the server. They also are frustrated - emotionally and practically from accomplishing their goal. Enough people complain all the time about dangling links that I hope the damage is obvious. I hope it also obvious that the reputation damage is to the maintainer of the server whose document vanished.
So what should I do? This needs thought, and organization, and commitment. URIs change when there is some information in them which changes.
It is critical how you de them. What, de looming URI? I have to de URIs? Yes, you have to think about it. Deing mostly means leaving information out. The creation date of the document - the date the URI is issued - is one thing which will not change. It is very useful for separating requests which use a new system from those which use an old system. That is one thing with which it is good to start a URI. If a escorts in halifax suburbs is in any way dated, even though it will be of interest for generations, then the date is a good starter.
The only exception is a which is tlme a "latest" for, for example, the whole organization or a q part of it. The main reason for not needing the date in this URI is that there is no reason for the persistence of the URI to outlast the magazine. The concept of "today's Money" vanishes if Money goes out of production.
Assumes that "money" will mean the same thing throughout the life fuck buddy rio branco pathfinder. There is a duplication of "98" and an ". What to leave out Everything! After the creation date, putting any information in the name is asking for trouble one way or another. Authors name- authorship can change with new versions. People quit organizations and hand things on.
This is tricky. It always looks good at the time but changes surprisingly fast. I godo this more below.
Status- directories like "old" and "draft" and so on, not to mention "latest" and "cool" appear all over file systems. Documents change status - or there would be no point in producing drafts. The latest version of a document needs a persistent identifier whatever its status is. Keep the status out of the name. It sounds good, but of course documents start off as team ideas, are discussed with members, and then go public.
A shame indeed if every time some document is opened to wider discussion all the old links to it fail! We are switching to a simple date code now.
File name extension. This is a very common one. You may not be using HTML for that in 20 years time, but you might want today's links to it to still be valid. The canonical way of making links to the W3C site doesn't use the extension.