Memespace Names and URNs

Consequences india in australia of blocking the receptors include reduced blood pressure and prevention diflucan of damage to the kidneys and heart. For this reason, buy cheap atarax a person can consult their doctor about their health issues buy cialis on line and all the medications they take. This was a response serevent to continued reports of suicidal thoughts or actions and other buy buy cheap adverse events in people taking montelukast. If a person has glucophage online stores any of the above signs, they could be experiencing significant cheapest no prescription medication side effects and may be thinking about suicide. "Bronchodilators store get generic without online prescription are a class of asthma medications that can help relieve purchase sale work bronchospasms and improve breathing through relaxing and opening air passages," said.

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.