On
EMXMLMSG01, we could ask OASIS to allows the URI identifiers to
link to pages that explain their use, as W3C does for SOAP 1.2 for http://www.w3.org/2003/05/soap-envelope/role/ultimateReceiver and
IANA does for www.example.com/.
Unfortunately I'm
traveling most of this week including Wednesday so I can't attend the call
..
Pim
From:
[mailto:] On Behalf Of Makesh Rao
(marao)
Sent: 23 April 2013 00:39
To:
Subject: [ebxml-msg] Jira issues to
discuss this Wed
EMXMLMSG01: Corrections in
Profile
1. In-line citations: In-line citations such as [ebMS3-CP] aren't
linked back to the entry in the References section.
Most specs link these types of references. They are sometimes bolded,
sometimes not and thought that inconsistency might confuse some
readers.
- Need to link back and have consistent font representations.
2. There are a number of broken links in the spec document. Many of
these turn out to be links to faux URLs on the OASIS website (e.g.
http://www.oasis-open.org/committees/ebxml-msg/push) or to docs.oasis-open.org (e.g.
http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/responder).
The narrative explains that these are only meant to be identifiers, not
links, however they are coded as live links in the document. They are broken
links in the document and may give readers an incorrect expectation about what
they can find on the web site.
- Correct the broken links or make them as identifiers and not
links
3. We also noted some links where the URL appears in black but the link
is indeed intended to be live, e.g.:
4.3 Processing Mode Parameter being present with the
value http://www.w3.org/2003/05/soap-envelope/role/ultimateReceiver
EBXMLMSG02: ebMS
Core Schema correction - Quickly Revisit
1) the type of eb:Property is of type Property, an extension of
non-empty-string; the ebMS3 schema does not reference
xs:anySimpleType.
2) the @type attribute is missing from the XML Schema at http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/ebms-header-3_0-200704.xsd
The type attribute is useful so my preference would be to add it back
to the schema.
This section of EBMS3CORE states the following about
eb:Property:
An eb:Property element is of xs:anySimpleType (e.g. string, URI) and
has two attributes:
• @name: The value of this REQUIRED attribute must be agreed upon
between partners.
• @type: This OPTIONAL attribute allows for resolution of conflicts
between properties with the same name, and may also help with Property grouping,
e.g. various elements of an address.
EBXMLMSG03: (Sec
5.8 of AS4) Correction of statement for Receipt generation
For Section 5.1.8, although the statement in the feature table
2.1.1:
"...Use of the ebbpsig:NonRepudiationInformation element (as defined in
[ebBP-SIG]) is REQUIRED as content for the eb:Receipt
message,"
