This is a suggestion for the 5th star extension.
I just failed to load our own vocabulary http://open-services.net/ns/core# from a JS RDF client due to the CORS policy. I realised that I will hit the same issue with FOAF and others and ended up writing an RDF document proxy https://github.com/berezovskyi/corsherdf. As you understand, proxy is a kludge that always hints at a problem and right now it is that most Linked Data and Semantic Web servers are configured in a way that prevents RDF resources to be used in any kind of “hypermedia” form (where a client dereferences resources itsefl).
Proposed qualifying criteria for the 5th star:
- an ontology allows a CORS request when a preflight request was sent from at least two different domains.
- a CORS response allows to use a
Content-Typeheader to preform content-negotiation in the browser RDF client.