[OASIS Issue Tracker] Created: (AMQP-62) Better explain the role of the XML notation used in the specification and its relation to the wire format

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Better explain the role of the XML notation used in the specification and its relation to the wire format
---------------------------------------------------------------------------------------------------------

                 Key: AMQP-62
                 URL: http://tools.oasis-open.org/issues/browse/AMQP-62
             Project: OASIS Advanced Message Queuing Protocol (AMQP) TC
          Issue Type: Improvement
          Components: DTD, Overiew, Types
    Affects Versions: CSPRD01
            Reporter: Rob Godfrey
            Assignee: Rafael Schloming


Comment From Public Review:

What is the role of the DTD with respect to the normative requirements defined in the document? If there are none, and its is just to document the template, then please remove as point 1) addresses this.

Saying that, it is unclear to me what the xml snippets in the documet mean wrt conformance. Throughout 1.2 (type encodings) xml snippets are provided despite encoding being defined in a bnf style e.g. 1.2.1 contains:

 Type:null
  <type name="null" class="primitive"/>

As an additional example 2.7 contains many complec type definions in xml. Does the xml get serialized somehow - if so that is really not clear.

Please clarify why the xml snippets are provided and how they relate to wire encoding.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira