Memespace Names and URNs

Decongestant order discount cheap side effects effects eye drops are also known as anti-redness eye drops and cialis free delivery help reduce symptoms of bloodshot eyes. Dry eye occurs when methotrexate order a person's tear glands are not producing sufficient tears to buy colchicine on line coat and lubricate the eye. A healthcare professional may prescribe diflucan sale antibiotic eye drops or ointment for bacterial pink eye to buy generic cafergot reduce the length of the infection, the risk of spreading free lipitor online order pink eye to others, and the risk of complications. Treatments purchase buy without prescription for dry eye include OTC and prescription eye drops, as nexium online well as lifestyle and habit changes. People with SLE can buy celexa without prescription also have eye issues related to SLE medications, such as purchase generic buy prescription delivery steroid-induced glaucoma. In addition, if a person notices any changes glyburide no prescription in their vision or new eye-related symptoms, seeking prompt medical attention.

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.