Fix term mapping of @reverse.

Author: davidlehn

CHANGELOG.md

@@ -14,6 +14,7 @@
 - Terms of the form of a relative IRI may not be used as prefixes.
 - Match spec error code "invalid context entry" vs "invalid context member".
 - Keywords may not be used as prefixes.
+- Term mapping of `@reverse`.
 
 ### Changed
 - Keep term definitions mapping to null so they may be protected.

lib/context.js

@@ -505,6 +505,10 @@ api.createTermDefinition = ({
         'jsonld.SyntaxError', {code: 'invalid IRI mapping', context: localCtx});
     }
 
+    if(!api.isKeyword(reverse) && reverse.match(KEYWORD_PATTERN)) {
+      return;
+    }
+
     // expand and add @id mapping
     const id = _expandIri(
       activeCtx, reverse, {vocab: true, base: false}, localCtx, defined,
@@ -516,18 +520,6 @@ api.createTermDefinition = ({
         'jsonld.SyntaxError', {code: 'invalid IRI mapping', context: localCtx});
     }
 
-    if(reverse.match(KEYWORD_PATTERN)) {
-      // FIXME: remove logging and use a handler
-      console.warn('WARNING: values beginning with "@" are reserved' +
-        ' for future use and ignored', {reverse});
-      if(previousMapping) {
-        activeCtx.mappings.set(term, previousMapping);
-      } else {
-        activeCtx.mappings.delete(term);
-      }
-      return;
-    }
-
     mapping['@id'] = id;
     mapping.reverse = true;
   } else if('@id' in value) {