CMPWG 10/9/2014:

The 128-bit signed integer is shown in the spec like this:

"<opc:OpaqueType Name="Int128" LengthInBits="128">
<opc:Documentation>A 128-bit signed integer.</opc:Documentation>
</opc:OpaqueType>"

The Schema for the OpaqueType looks like this:

" <xs:complexType name="OpaqueType">
<xs:complexContent>
<xs:extension base="TypeDescription">
<xs:attribute name="LengthInBits" type="xs:int" use="optional" />
<xs:attribute name="ByteOrderSignificant" type="xs:boolean" default="false" />
</xs:extension>
</xs:complexContent>
</xs:complexType>"

The example does not appear to conform to the schema, the "ByteOrderSignificant" is missing; and why is "LengthInBits" optional? Should "LengthInBits" be an unsigned int?

Also, in the case of the 128-bit signed integer, how would that be sent over the wire?

Lastly, the last sentence in Table C.3 "ByteOrderSignificant" states "If this attribute is “true”, then the LengthInBits attribute shall be specified and it shall be an integer multiple of 8 bits" so we are assuming this means that we can define an opaque type that is 19 bits long when the attribute is FALSE?