[OASIS Issue Tracker] (WSCALENDAR-496) Line 214/215: "The effect of this is that Stream Intervals are ordered as a Partition in order of increasing UID." Far too broad

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

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

William Cox edited comment on WSCALENDAR-496 at 4/29/16 5:02 PM:
-----------------------------------------------------------------

"UID" misleads - it's a LOCAL ID that allows distinction between the stream payloads. The problem is "Universal ID" which isn't universal unless composed with the UID for the stream.


was (Author: williamcox):
UID misleads - it's a LOCAL ID that allows distinction between the stream payloads. The problem is "Universal ID" which isn't universal unless composed with the UID for the stream.

> Line 214/215: "The effect of this is that Stream Intervals are ordered as a Partition in order of increasing UID."  Far too broad
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WSCALENDAR-496
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-496
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Bug
>          Components: streams
>         Environment: Benoit Lepeuple
>            Reporter: Toby Considine
>            Assignee: William Cox
>
> This sentence assumes there is an ordered relation for UIDs, which can be true for a particular implementation, but is not the case in general as UIDs are derived from a string datatype. This kind of assumption can not be left as is without a conformance statement making mandatory the usage of a particular datatype / order relation for the UIDs. Unless implementations will never interop (even using the same datatype let say numbers hold in a string datatype: One could sort alpha, the other could cast to Int then sort numerically or vice-versa).
> Also applies to Line 297



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)