Memespace Names and URNs

There remeron for order is an association between advanced dry or wet macular degeneration buy buy overnight delivery with significant central vision loss. Wet macular degeneration is an buy purchase advanced form of the condition, and experts generally consider it order buy overnight delivery the most severe form. When TB affects the lungs, the cialis side effects disease is the most contagious, but a person will usually erythromycin for order only become sick after close contact with someone who has gel canada this type of TB. If a person stops taking their acomplia sale medication early, some bacteria can survive and become resistant to order synthroid in us antibiotics. This means that a person with HIV has a nexium prescription higher risk of developing TB and experiencing more severe symptoms purchase cheapest 60 no prescription tablets than someone with a healthy immune system. An active TB cheap viagra tablet infection is contagious and potentially life threatening if a person does.

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.