Memespace Names and URNs

Addressing buy lipitor online sleep apnea and related eye conditions promptly is important to zyprexa online stores prevent potential complications and maintain overall health and quality of order flagyl online life. The eyes may become dry, sand-like, gritty, and worn cheapest cafergot out, especially with prolonged digital device use. Smoking is a order cheapest colchicine dose significant risk factor for many eye problems, including cataracts, age-related find viagra no prescription required macular degeneration (AMD), and optic nerve damage. People also use cheap nasonex internet tea tree oil for MGD, which is when the glands buy mirapex from india that make oil in the eyelids do not work as dexamethasone they should, resulting in dryness. There is little information on tablet (metacam) whether tea tree oil is safe for someone who is pregnant.

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.