OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (EBXMLMSG-1) Corrections in profile


    [ http://tools.oasis-open.org/issues/browse/EBXMLMSG-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33364#action_33364 ] 

Makesh Rao commented on EBXMLMSG-1:
-----------------------------------

Comments from Theo on #2 in the description.


Sections 2.1.3.1, 2.2.3.1 and 2.3.3.1 states the following

PMode.MEP: support required for: http://www.oasis-open.org/committees/ebxml-msg/one-way

PMode.MEPbinding: support required for: http://www.oasis-open.org/committees/ebxml- msg/push and http://www.oasis-open.org/committees/ebxml-msg/pull.

Yet section 5.2.5 Default Values of Some P-Mode Parameters states the following

PMode.MEP parameter will be constrained to the following value: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/oneWay

and

PMode.MEPbinding parameter will be constrained to the following values:

   http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/push

   http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/pull

These should be one or the other but not both.


> Corrections in profile
> ----------------------
>
>                 Key: EBXMLMSG-1
>                 URL: http://tools.oasis-open.org/issues/browse/EBXMLMSG-1
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Improvement
>          Components: AS4 Profile
>            Reporter: Makesh Rao
>            Priority: Trivial
>
> 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
> - Make all links the standard hyperlink color.

-- 
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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]