Memespace Names and URNs

Preventing buy cheap nexium a cockroach infestation requires eliminating their food sources and hiding purchase viagra no rx places and fixing any moisture problems in the home. Warm, tablet free windy places with many allergy-causing trees may be among the discount discount overnight delivery worst places to live for people with this allergy. Because mirapex no prescription cold temperatures make mold inactive, places that are relatively cold discount nexium and dry may be better options. Some examples include smoke buy online sales from campfires, pine needles from Christmas trees, and chlorine in flovent prescription swimming pools. As grasses tend to feature in gardens and cheap amoxicillin tablets public spaces, people may also be able to avoid the buy generic erythromycin problems pollen by staying inside when pollen counts are high. People amoxicillin can minimize their exposure by opting for low allergen alternatives in.

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.