Changing the namespace to w3.org (ISSUE-19)

Hi folks,

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 and reliability of Hydra and make the
vocabulary and the predefined JSON-LD contexts accessible from in-browser
applications, I would thus propose 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# instead of http://purl.org/hydra/core#.

I think this is the right thing to do and that it's still early enough to
make this change. Does someone object or thinks that this is a bad idea?


--
Markus Lanthaler
@markuslanthaler

Received on Wednesday, 4 December 2013 19:12:34 UTC