[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-352) Add aconstraint to the model that maxConsecutiveDays in EiConstraint is presentonly if schedule is not and vice versa
[ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25195#action_25195 ]
William Cox commented on ENERGYINTEROP-352:
-------------------------------------------
"Constraint" is confusing us -- emix:Constraint is NOT the same as EiConstraint.
These constraints are now in EMIX wd22 - maxConsecutiveDurations, availability schedule. Use that rather than this version.
This solution is overly complex.
> Add a constraint to the model that maxConsecutiveDays in EiConstraint is present only if schedule is not and vice versa
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: ENERGYINTEROP-352
> URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-352
> Project: OASIS Energy Interoperation TC
> Issue Type: Improvement
> Affects Versions: wd22
> Environment: William Cox
> Reporter: William Cox
> Assignee: William Cox
>
> The class EiConstraint has three associations to EiConstraintSchedule:
> (a) acceptSchedule
> (b) maxConsecutiveDays
> (c) notAcceptSchedule
> All need filter:EiConstraintBehavior, but consecutiveDays is mutually exclusive with schedule.
> Add a contraint to the model to so indicate.
> The alternative would require that EiConstraint have two classes rather than one.
--
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]