OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-383) Constraintsand Constraints Behavior re-factoring

    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25222#action_25222 ] 

Toby Considine commented on ENERGYINTEROP-383:

I would like a discussion of the ConstraintsBehavior object, as it is not a Constraint, as defined in EMIX, but some responses to some specific constraints when encountered. 

It almost sounds as "How to configure the VTN for this customer  [VEN]". Can the VEN CHange it? Is it a report about that configuration to the VEN, but its actual setting is out of scope?

> 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
>    Affects Versions: wd22
>            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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]