Memespace Names and URNs

This order no rx viagra can result from coronary heart disease, in which plaque — buy cheap zoloft online made up of cholesterol and other substances — collects in glucophage prescription the arteries, narrowing them. Deep vein thrombosis (DVT) is a buy generic buy no prescription usa clot that typically occurs in a major vein in the buy augmentin leg, but it can also develop in the pelvis or buy cheap toradol online arm. They can cause various symptoms and complications, including heart buy zithromax online attack, stroke, severe pain, and paralysis. People should be aware canadian pharmacy bentyl of their risk factors for developing a blood clot, which cialis order can include obesity, being stationary for extended periods, and pregnancy. cheap cialis The most common place for a venous blood clot to buy generic overnight best price develop is the leg, most often in the calf, and buy cheap azor online the symptoms are similar in the arm. This occurs when a.

Ron Daniel writes on the TaxoCop list that “managing memespaces
sounds like managing URN namespaces. You might want to see what
the IETF defined for URNs, see which parts of it make sense, and
also see if you can figure out what special value you will offer
that will tempt people into supporting and using memespace names
when they have pretty much ignored URNs.”

Ron is right that URNs have been ignored. Only 25 URNs have been registered, probably because of the laborious RFC process needed for each one.

Some of them are organization names, suitable for proper memespaces (like OASIS and IETF). Others are more properly used as taxospace names (like ISBN and ISSN).

Memography’s Memespace Registry will offer a much simpler procedure for registering memespace and taxospace names.

And of course the value is memetic search.

Comments are closed.