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] (EBXMLMSG-108) Unclear if empty ConversationId is allowed

    [ https://issues.oasis-open.org/browse/EBXMLMSG-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66990#comment-66990 ] 

Theo Kramer commented on EBXMLMSG-108:

My reading from the core spec is that element eb:ConversationId must be set - and that a default of “1” may be used if it does not form part of any partner agreed upon requirements.

It may also be useful that the ebms-header  schema be updated to set minOccurs to value "1" for element ConversationId as follows

        <xsd:complexType name="CollaborationInfo">
                        <xsd:element name="AgreementRef" type="tns:AgreementRef" minOccurs="0"/>
                        <xsd:element name="Service" type="tns:Service"/>
                        <xsd:element name="Action" type="xsd:token"/>
                        <xsd:element name="ConversationId" type="xsd:token" minOccurs="1"/>

The same may be required for the eb:Action element

> Unclear if empty ConversationId is allowed
> ------------------------------------------
>                 Key: EBXMLMSG-108
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-108
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Bug
>          Components: Core Spec
>            Reporter: Sander Fieten
> In § states that the eb:ConversationId element is required and must occur in the ebMS message header. In § where the element is further described it is stated that the value is "a string identifying the set of related messages that make up a conversation between Parties." and "The actual semantics of this value is beyond the scope of this specification.". There is no explicit statement on whether an empty string is allowed.
> The XML schema defines the type of this element as xsd:token without any further restrictions, so an empty string would be valid. It is however unclear whether this is intentional as also the eb:Action element has the same type although the Action shall not be an empty string.
> Because an empty string doesn't really qualify as an identifier it seems logical to assume that an empty value is not allowed here.
> Additionally §4.3 defines also a default value of '1' for this element if no value is specified also suggesting that an empty value is not allowed.

This message was sent by Atlassian JIRA

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