[OASIS Issue Tracker] Created: (ENERGYINTEROP-383) Constraints andConstraints Behavior re-factoring

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

Constraints and Constraints Behavior re-factoring
-------------------------------------------------

                 Key: ENERGYINTEROP-383
                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-383
             Project: OASIS Energy Interoperation TC
          Issue Type: Improvement
          Components: schema
            Reporter: Toby Considine
            Assignee: William Cox
             Fix For: wd23


We have the Schedules from EMIX Constraints:

availabiltySchedule
unavailabilitySchedule

We also have the EI ConstraintBehavior, which is hints at how to deal with times when there is an incompatibility between the temporal constraints of the schedule and the requirements of the event.

Currently, the availability schedules are in the array of constraints. Should they instead be paired in some other object with the eiConstraintBehavior? This appears to be what the eiConstraintSchedule does. In refactoring [eiEvents] several constraints were eliminated, a couple new ones were added to EMIX constraints, and the event now has an array of constraints, unspecified.
Should it be an Array of eiConstraintSchedule(s) with any single constraint modifiable by the eiConstraintBehavior? Should only some constraints be expressable in eiConstraintSchedule(s)?


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