Memespace Names and URNs

He erythromycin without prescription was the royal surgeon for four French kings and an canadian diflucan expert in battlefield medicine, particularly wound treatment and surgery. Paré buy cheap ampicillin online canada also believed that phantom pains, sometimes experienced by amputees, were cheapest allopurinol side effects dose related to the brain, and not something mysterious within the norvasc for order amputated limb. At one time, doctors asked King Charles II buy norvasc online to help by touching sick people in an attempt to cheap drops no rx cure them of scrofula, a type of tuberculosis (TB). The purchase cheap prescription online canada anesthesiologist provides pain relief before, during and after surgery, but purchase cephalexin price work they also fulfill a number of other important roles. The lumigan purchase anesthesiologist controls these vital measures and the patient's level of buy azor pain and unconsciousness throughout the operation. Anesthesiologists are also qualified to.

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.