Memespace Names and URNs

The buy zoloft without prescription hearing loss can be conductive, which means sound cannot reach cheap viagra without prescription the inner ear, or sensorineural, in which something causes damage buy viagra pills to the structures in the inner ear or auditory nerve. cheap cialis no prescription Because doctors often do not know the cause of SSHL, buy cheap cheapest online canada they may treat the condition with corticosteroids. KF syndrome causes zofran online stores two or more bones in the neck to remain fused buy cheap compazine online instead of separating into distinct bones. Some researchers have suggested find discount buy online a link between KF syndrome and problems with blood flow order cialis from canada to the fetus, as well as neural tube abnormalities, which buying cheap form the brain and spine of the fetus early in pregnancy..

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.