[OASIS Issue Tracker] Updated: (ENERGYINTEROP-349) EiEvent isoverly complex; simplify per current EMIX and WS-Calendar

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

     [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated ENERGYINTEROP-349:
--------------------------------------

    Description: 
In cleaning up the UML to generate first draft schemas, it became clear that there are several schedules in EiEvent.

One is schedule (associated with Emix:wscal:Sequence) which should be replaced with a simple gluon OR a link (contained in the gluon). This is a carryover from a more complex way of expressing schedules.  A gluon is the standard way of referencing a sequence, which is no longer an object in wscal.

By removing the associations the diagram is also more clear. (the working UML toward WD23 shows these changes)

In the alternative, make the attributes BusinesSchedules as appropriate.



  was:
In cleaning up the UML to generate first draft schemas, it became clear that there are several schedules in EiEvent.

One is schedule (associated with Emix:wscal:Sequence) which should be replaced with a simple gluon OR a link (contained in the gluon). This is a carryover from a more complex way of expressing schedules.  A gluon is the standard way of referencing a sequence, which is no longer an object in wscal.

By removing the associations the diagram is also more clear. (the working UML toward WD23 shows these changes)




> EiEvent is overly complex; simplify per current EMIX and WS-Calendar
> --------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-349
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-349
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>    Affects Versions: wd22
>         Environment: William Cox
>            Reporter: William Cox
>            Assignee: Ed Koch 
>
> In cleaning up the UML to generate first draft schemas, it became clear that there are several schedules in EiEvent.
> One is schedule (associated with Emix:wscal:Sequence) which should be replaced with a simple gluon OR a link (contained in the gluon). This is a carryover from a more complex way of expressing schedules.  A gluon is the standard way of referencing a sequence, which is no longer an object in wscal.
> By removing the associations the diagram is also more clear. (the working UML toward WD23 shows these changes)
> In the alternative, make the attributes BusinesSchedules as appropriate.

-- 
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