Issue 16950: GEMS-XML hex_value length Issue (gems-rtf) Source: Amergint Technologies (Mr. Rob Andzik, andzik(at)amergint.com) Nature: Uncategorized Issue Severity: Summary: The GEMS-XML XSD bases the HexParameter on the xsd:hexBinary type. This type expects an even number of characters (two for each octet). The GEMS-XML specification should mention this and explain how it needs to be handled. Recommend always providing an even number of hex characters and using the bit length to specify the actual length. Example of an invalid 4 bit field: E/4 Example of a valid 4 bit field: E0/4 Resolution: Revised Text: Actions taken: January 10, 2012: received issue Discussion: End of Annotations:===== m: Rob Andzik Date: Tue, 10 Jan 2012 12:58:15 -0700 Subject: GEMS-XML hex_value length Issue To: issues@omg.org The GEMS-XML XSD bases the HexParameter on the xsd:hexBinary type. This type expects an even number of characters (two for each octet). The GEMS-XML specification should mention this and explain how it needs to be handled. Recommend always providing an even number of hex characters and using the bit length to specify the actual length. Example of an invalid 4 bit field: E/4 Example of a valid 4 bit field: E0/4 -- Rob Rob Andzik 719-522-2813 AMERGINT Technologies www.amergint.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :x-gm-message-state; bh=CO3JX8jgpCYFuW3NV9nVPb3KOq7oQ6eomJaOzP1mRS4=; b=hAPWtI7l/nBdchFGIciPdbSWVWdxY3o4Qme8kR7Kmz/opv3iPv9JvFRBRves1Sg5iM HFPUQZaS2xs3toyWt1ParMy4ilTJ5QD0iHIOsQJQcG8QvK7JZZ8VTx37iQM0hVhQ2SVs xwnrND5pLXbkzAtU9XD1B0xZupLZUuFb5D+0C7kWJj9kiasytSrlKhi9f8UZAojG6UR0 RINCHAvbZscbY+H5LzbpkJ+XfZJ0ZGmqm1uNxM91GJrN27oWtD+4vMbXrzw0LqZuNt4E GE5iSEfaftnpIdMdi0k3991RP/FEF84jQJfWoLotY0xl/HfxxnFwLAB8PFQPsZwsw/Ar 2AiQ== X-Received: by 10.152.87.15 with SMTP id t15mr7866082laz.85.1374267966643; Fri, 19 Jul 2013 14:06:06 -0700 (PDT) From: Rob Andzik Date: Fri, 19 Jul 2013 15:05:46 -0600 Subject: Issue 16950: GEMS-XML hex_value length Issue (DISCUSS) To: "gems-rtf@omg.org" X-Gm-Message-State: ALoCoQkxPWjfOf9vh78QfDrQV0vtJ5M0+lF4xOrjYbo7i61IWb9+A1Q1kNZFlw1oA61arCu02M5/ X-Virus-Scanned: amavisd-new at omg.org Issue 16950: GEMS-XML hex_value length Issue This is just an update to the description for the GEMS-XML hex_value. XML expects full bytes (two nibbles). The field must be padded out to two nibbles for XML. Example: E0/4 (good) E/4 (bad) Both indicate exactly the same 4-bit value. There is no technical reason this needs to be specified for GEMS-ASCII, but there might be some benefit to keeping them in sync. Thoughts? X-Env-Sender: nthompson@rtlogic.com X-Msg-Ref: server-8.tower-219.messagelabs.com!1374500532!3813867!1 X-Originating-IP: [207.109.164.59] X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked From: "Thompson, Nigel" To: "andzik@amergint.com" , "gems-rtf@omg.org" Date: Mon, 22 Jul 2013 07:42:11 -0600 Subject: RE: Issue 16950: GEMS-XML hex_value length Issue (DISCUSS) Thread-Topic: Issue 16950: GEMS-XML hex_value length Issue (DISCUSS) Thread-Index: Ac6Ew9BWSmdsZWHITcih305Tha8uqgCHVqCA Accept-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US X-Mlf-Version: 7.4.2.7667 X-Mlf-UniqueId: o201307221342120039695 X-Virus-Scanned: amavisd-new at omg.org I would suggest keeping the rules the same for both the ASCII and XML encodings. Nigel From: Rob Andzik [mailto:andzik@amergint.com] Sent: Friday, July 19, 2013 3:06 PM To: gems-rtf@omg.org Subject: Issue 16950: GEMS-XML hex_value length Issue (DISCUSS) Issue 16950: GEMS-XML hex_value length Issue This is just an update to the description for the GEMS-XML hex_value. XML expects full bytes (two nibbles). The field must be padded out to two nibbles for XML. Example: E0/4 (good) E/4 (bad) Both indicate exactly the same 4-bit value. There is no technical reason this needs to be specified for GEMS-ASCII, but there might be some benefit to keeping them in sync. Thoughts? smime2.p7s smime2.p7s