Example Section	Line Number	Comment
3.2	821	No namespace for SOAP: or eb:
3.2	836	No namespace for SOAP: or eb:. Does not validate. Obviously PartyInfo, CollaborationInfo and PayloadInfo will not validate. These elements are stubbed out.
3.3	869	No namespace for SOAP:, wss:, wsr:, or eb:. eb:Messaging validates, the rest does not.
3.3	896	No namespace for SOAP:, wss:, wsr:, or eb:. Does not validate. PartyInfo, CollaborationInfo and PayloadInfo are stubbed out. As well as Security and Response.
5.1.3.2	1317	Line 1321 - missing eb: prefix on Messaging element. UserMessage stubbed out.
5.1.4	1375	No namespace for eb:. Otherwise this example is basically a stub
5.1.5	1402	Example is a stub.
5.2		Examples are stubs
5.2.1	1467	No namespace for SOAP: or eb:. Does not validate. Line 1474 - the schema specifies element TimeStamp, the xml (and the spec) has Timestamp. I believe that the schema is incorrect. Line 1508 - missing quotes around the location attribute value.
5.3.1	1838	TimeStamp issue
5.3.1	1895	The schema requires eb:From to be before eb:To. The example has these reveresed. This ordering in the schema seems unecessary.
5.3.2	1937	looks ok
5.3.3	1958	Line 1971 and 1975 - missing xml:lang attribute.
5.3.4	1987	looks ok
5.3.5	2032	Does not validate - Schema requires Signals to come before UserMessages. Seems like an uncessary restriction in the schema.
7.9.1	2347	Does not validate - Use of soap: prefix and S11: prefix is inconsistent, Timestamp issue. ConversationId in spec and xml, ConversationID in schema.
7.9.2	2493	Does not validate - Use of soap: prefix and S11: prefix is inconsistent, Timestamp issue. ConversationId in spec and xml, ConversationID in schema.
7.9.3	2660	Does not validate - Use of soap: prefix and S11: prefix is insonsistent. TimeStamp element is used. Inconsistent use of eb: prefix and ebms: prefix. Missing namespace deleration for ds: .
7.10	2792	Does not validate - Use of soap: prefix and S11: prefix is inconsistent, Timestamp issue. Missing wsse: namespace declaration.