The Viagra identify has grow to be so well-known that many fake aphrodisiacs now call themselves "natural viagra" or are introduced as blue tablets imitating the shape and color of Pfizer's product. You will need to research well while in search of erectile dysfuntion cures. Servers get hammered by individuals looking up contextual mappings. I know this from personal expertise (and by that I imply many painful hours of my life wasted that I can by no means get back). Should it happen in a separate namespace first and then get "pulled in" later? Viagra is in a category of impotence medicine recognized because the phosphodiesterase 5 (PDE5) inhibitors and was the primary authorised to deal with ED. The primary downside with choosing to put our terminology URIs at HTTP(S) URIs is that it assumes that those vocabularies will remain alive. The selection to map our vocabulary to URIs is definitely a really affordable approach to cut back ambiguity. The issue is dramatically worse for json-ld contexts (and related documents corresponding to XML DTDs): these are the very documents by which we map phrases to their totally outlined meanings. Unfortunately, the selection to map them to namespaces and to live URIs (a-la http(s): URIs), is a mistake that may ultimately bite us (and doubly so for JSON-LD contexts).