[OASIS Issue Tracker] (WSCALENDAR-502) General: Why not make Sequence a type of Component? Why not enhance the notion of Partition/Sequence to cope with the need for Streams?

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

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

William Cox commented on WSCALENDAR-502:
----------------------------------------

If one views a stream as an optimization of a "sequence with no gaps and all intervals the same size" in shorthand, I don't think that this is a different concept; the supporting text MUST express this clearly.

> General: Why not make Sequence a type of Component?  Why not enhance the notion of Partition/Sequence to cope with the need for Streams?
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WSCALENDAR-502
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-502
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: STRM CSPRD02
>         Environment: Benoit LePeuple
>            Reporter: Toby Considine
>            Assignee: Toby Considine
>
> My understanding is that Streams are just a particular kind of Sequence (Partition), a new animal with particular rules of inheritance to minimize the amount of repeated data (by inventing the Stream Payload Base). Why not doing that with animals we already domesticated: A Gluon Payload Base or Sequence Payload Base?
>  
> I do not feel comfortable with such overlapping concepts and specifications.



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