[OASIS Issue Tracker] (EBXMLMSG-108) Unclear if empty ConversationId is allowed

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Sander Fieten commented on EBXMLMSG-108:
----------------------------------------

I agree that it might be useful to have indicate that there is no "real" conversation. But for that case it would in my opinion be better to have no ConversationId element at all. Problem of course is that this is not allowed by the current version of the spec. So best would be to change the spec on this point.
Based on the current text of the spec I don't find it evident that the empty string could be used for this purpose, I would rather define a special value for indicating this.


> 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 §5.2.2.6 states that the eb:ConversationId element is required and must occur in the ebMS message header. In §5.2.2.10 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
(v6.2.2#6258)