[ebxml-msg] Errata first shot at DocBook Draft

[Mike Dillon - Drummond Group <mike@drummondgroup.com>]

Hi all,

 FYI, I have DocBook installed and working, as mentioned
 on todays call, I just need to figure out some CDATA like issues,
 then I can finish up and publish first draft of Errata in DocBook style !

 mike dillon
 mike@drummondgroup.com

Title: OASIS ebXML Message Service Specification Errata

OASIS ebXML Message Service Specification Errata

Version 4.1

Working Draft 4.1, 08 January 2003

Document identifier:

ebxml-ms-errata-4.1

Abstract:

This document details errors, omissions and clarification identified for the ebXML Message Service Specification version 2.0. This errata document MUST only be used in conjunction with the specification detailed above. Its purpose is to improve the quality of the specification, reduce inconstancies and improve the interoperability of solutions based on the specification.

Copyright © 2003 The Organization for the Advancement of Structured Information Standards [OASIS]

---

Table of Contents

1. Introduction

2. Document Conventions

2.1. Sources

2.2. Terminology

2.3. Audience

2.4. Caveats and Assumptions

3. Errata List

3.1. Known Errors

Appendixes

A. Revision History

References

---

1. Introduction

This document details errors, omissions and clarification identified for the ebXML Message Service Specification version 2.0. This errata document MUST only be used in conjunction with the specification detailed above. Its purpose is to improve the quality of the specification, reduce inconstancies and improve the interoperability of solutions based on the specification. This document contains 4 major sections: Known errors - details errors in the specification. Minor typographical errors - details textual and grammatical errors in the specification. Clarifications - details areas that required additional information to aid implantation. Miscellaneous - details any other relevant information. All sections are ordered by the section number of the affected section of the original specification.

2.  Document Conventions

2.1.  Sources

During Draft phases of this document, the source of the Errata item will be tracked, this information will be removed for the final draft of the document.

2.2.  Terminology

The key words must , must not , required , shall , shall not , should , should not , recommended , may , and optional in this document are to be interpreted as described in rfc2119.

2.3.  Audience

The target audience for this specification is the community of software developers who will implement the ebXML Message Service

2.4.  Caveats and Assumptions

It is assumed the reader has an understanding of communications protocols, MIME, XML, SOAP, SOAP Messages with Attachments and security technologies

3.  Errata List

3.1.  Known Errors

This section details all the errors in the specification identified by the date on this document together with their resolution or impact. They are ordered by their section number in the original specification.

3.1.1.  Section 3.1.9 Message Header Sample

The example in this section shows a MessageID that does not appear to conform to RFC 2822. In section 3.1.6.1 MessageId Element, lines 878 - 879 the specifcation states “The REQUIRED element MessageId is a globally unique identifier for each message conforming to MessageId [RFC2822].” Within RFC 2822, a BNF shows the format as "<" id-left "@" id-right ">". All examples in the specification follow this BNF notation, except for the example in Section 3.1.9 lines 932 to 936 as below.hey <eb:MessageData> <eb:MessageId>UUID-2</eb:MessageId> <eb:Timestamp>2000-07-25T12:19:05</eb:Timestamp> <eb:RefToMessageId>UUID-1</eb:RefToMessageId> </eb:MessageData> RECOMMEND that this example be changed to read : <eb:MessageData> <eb:MessageId>UUID-2@example.com</eb:MessageId> <eb:Timestamp>2000-07-25T12:19:05</eb:Timestamp> <eb:RefToMessageId>UUID-1@example.com</eb:RefToMessageId> </eb:MessageData> Source: DGI ebXML Messaging Interop Trials

A. Revision History

Revision History
Revision 4.1	08 January 2003
Port to docbook.

References

NonNormative

[ebMS] Message Service Specification version 2.0 . OASIS (Organization for the Advancement of Structured Information Standards).