GEMS14 — Numerous small errata and inconsistencies

6.3.1.13 hex_value - Add: The length in bits is specified by following the hex data with a forward slash and the number of bits. E.g. /22.6.3.1.13 hex_value - Add: The length in bits is specified by following the hex data with a forward slash and the number of bits. E.g. /22.

Many of the XML examples: The gems_version attribute type should be xsd:decimal not xsd:int

Many of the XML examples: The XML examples shoudl all include the standard xml version segment like:
<?xml version="1.0" encoding="UTF-8"?>
This is missing from most of the examples

Many of the examples: The gems_version is shown as an integer value like: "1". It should be shown as a decimal value like: "1.3"

7.3.4.1 SetConfigMessage Example - this has a superfluous line: </SetConfigMessage> about half way down that needs to be deleted.

7.3.7.1 PingMessage Example - The version number should be changed from 1.1 to 1.3

7.3.7.2 PingResponse Example - The version number should be changed from 1.1 to 1.3

7.3.8.1 ConnectionRequestMessage without Authentication - The version number should be changed from 1.2 to 1.3

7.3.8.3 ConnectionRequestMessage with Authentication - The version number should be changed from 1.2 to 1.3

7.3.8.4 Failed ConnectionRequestResponse - add the version number as 1.3

7.3.8.5 Successful ConnectionRequestResponse - add the version number as 1.3

7.3.8.3 ConnectionRequestMessage with Authentication - The token filed text should be: "up:john:secret"

7.5.1 Example Device Definition File - replace 'bool' with 'boolean' 4 places

Table 8.1 boolean type: example should be: param:boolean=true

8.3.3 GetConfigMessage Example - change example sync_pattern to be: sync_pattern:hex_value=FAF320/22

8.3.4 SetConfigMessage Example - change example sync_pattern to be: sync_pattern:hex_value=FAF320/22

8.3.7 DirectiveMessage Example (response) - change accepted:bool=true to accepted:boolean=true

Clarify the bit_length field in a hex_value within the PIM

The request was to add the /bit-length notation to the description. Since this is actually the GEMS-ASCII format (XML is different), we will add a comment about the bit_length instead.

Issue GEMS14-7 lists many corrections in the documented examples. Since these are being removed from the document the issues are OBE. The generated examples online already correct these issues.