[OASIS Issue Tracker] Created: (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>]

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: http://tools.oasis-open.org/issues/browse/WSCALENDAR-502
             Project: OASIS Web Services Calendar (WS-Calendar) TC
          Issue Type: Improvement
          Components: spec
    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 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