Merge pull request adlnet#261 from imartinezortiz/issue-256

Clarify current version of the used JSONSchema specification

xapi-profiles-about.md

@@ -239,7 +239,7 @@ even if there no requirement in a given area.
 
 <a name="json"></a>**JSON**: [JavaScript Object Notation](http://www.json.org). A simple way to represent data structures for computers that humans don't have too hard a time writing or reading. The way Profiles are represented in this specification.
 
-<a name="jsonschema"></a>**JSON Schema**: [JSON Schema](http://json-schema.org) are a way to describe and constrain the form of JSON documents.
+<a name="jsonschema"></a>**JSON Schema**: [JSON Schema](http://json-schema.org) are a way to describe and constrain the form of JSON documents. This specification adheres to [Draft-07](https://json-schema.org/specification-links.html#draft-7) version of the JSON Schema specification.
 
 <a name="jsonld"></a>**JSON-LD**: [JSON-LD](https://json-ld.org) turns JSON into Linked Data, making it easy to use with Linked Data tools and integrate with other datasets.
 

xapi-profiles-structure.md

@@ -272,7 +272,7 @@ Property | Type | Description | Required
 `schema` | IRI | the IRI for accessing a JSON Schema for this extension. The JSON Schema can be used to constrain the extension to a single type. | Optional
 `inlineSchema` | Object | An alternate way to include a JSON Schema, as a string. | Optional
 
-Profiles MUST use at most one of `schema` and `inlineSchema` for Extensions.
+Profiles MUST use at most one of `schema` and `inlineSchema` for Extensions. JSON Schema expressions SHOULD adhere to the [Draft-07](https://json-schema.org/specification-links.html#draft-7) version of the JSON Schema specification.
 
 Statements including extensions defined in a Profile MUST:
 * only use a ContextExtension in context
@@ -325,7 +325,7 @@ Property | Type | Description | Required
 `schema` | IRI | the IRI for accessing a JSON Schema for this document resource. | Optional
 `inlineSchema` | String | An alternate way to include a JSON Schema, as a string. | Optional
 
-Profiles MUST use at most one of `schema` and `inlineSchema` for Document Resources
+Profiles MUST use at most one of `schema` and `inlineSchema` for Document Resources. JSON Schema expressions SHOULD adhere to the [Draft-07](https://json-schema.org/specification-links.html#draft-7) version of the JSON Schema specification.
 
 Learning Record Store Clients sending Document Resources
 * MUST use the `id` as the `stateId` or `profileId` (as appropriate) when interacting with the corresponding resource.