Should we provide a prefixed version of context? #6
Description
An alternative context is available at https://w3id.org/ore/context-ore, which defines ORE terms with the ore: prefix. This context MAY be used instead, for instance to avoid naming conflicts when including the ORE context in another JSON-LD context.
Should this be included? The reason I made it was thinking of the case of other people importing the ORE context within an application-specific context. We might not want to hijack non-prefixed names like "describes".
If it is to be included, does the text need more explanation on to when it should and should not be used?