Memespace Names and URNs

RA diclofenac online stores can cause inflammation of the glomeruli, known as glomerulonephritis, which cheapest generic cialis can negatively affect kidney function and may cause CKD. Getting buy viagra without prescription tests for other risk factors, such as high blood pressure, cheap viagra pharmacy may also help to reduce kidney disease risk. When a buy india person has cirrhosis, their liver does not heal, and scar ventolin online stores tissue begins to replace healthy tissue. If a person has buy arcoxia without prescription cirrhosis and needs to switch medications or is considering taking cheapest prescription OTC medications or supplements should also speak with a healthcare purchase glucophage online professional. The World Health Organization reports that obesity may surpass order online in canada smoking as the primary risk factor for preventable cancers. A purchase free buy low price australia healthcare professional may follow up with monitoring and regular imaging tests.

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.