Memespace Names and URNs

Mirena buy cheap glucophage is approved to help prevent pregnancy and treat heavy menstrual cialis without rx bleeding in adolescents who have started their menstrual periods. Several buying generic atenolol medications people take to treat a variety of health conditions buy generic gentamicin eye drops may contribute to kidney damage. Usually, physical symptoms of grief erythromycin cost come and go over time, gradually improving over the course asacol online stores of a few months or years. They'll likely monitor you best price for viagra for any symptoms of respiratory depression during your treatment, or atenolol they may have you try a different medication for your cheapest cialis price condition. A person who is interested in trying alternative treatments, cialis drug such as CBD, should contact a doctor to discuss the buy generic augmentin potential benefits and risks. However, several laws give people rights clindamycin gel online when physical or mental disabilities affect their everyday activities. When cancer.

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.