Recently purl.org experienced several downtimes and, despite numerous community requests, CORS headers have still not been set. This makes it impossible to access the vocabulary from a in-browser JavaScript application and harms the trust in Hydra.
To improve the long-term stability of Hydra and make it accessible also from in-browser applications the proposal is thus to move the namespace to w3.org. In practice this means that the hydra prefix would be mapped to http://www.w3.org/ns/hydra/core#.
Recently purl.org experienced several downtimes and, despite numerous community requests, CORS headers have still not been set. This makes it impossible to access the vocabulary from a in-browser JavaScript application and harms the trust in Hydra.
To improve the long-term stability of Hydra and make it accessible also from in-browser applications the proposal is thus to move the namespace to w3.org. In practice this means that the
hydraprefix would be mapped tohttp://www.w3.org/ns/hydra/core#.