[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-369) Opt containsadditional elements that are not in the submitted models - need explanationon why they are there
[ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25717#action_25717 ]
Bruce Bartell commented on ENERGYINTEROP-369:
---------------------------------------------
The last comments address http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-369
Not this issue.
This issue is about multiple occurances of VEN ID in the opt message and no Resource ID. The VTN needs to know which resource is opting out in order to adjust fhe forecast. The VEN ID is the party that originated the opt message; and may not be needed.
Additionally, use of the VEN ID could be misleading. The same part could act as VTN or VEN depending on the context. If we decide we need this element it should be the same party ID that is used during enrollment/registration.
> Opt contains additional elements that are not in the submitted models - need explanation on why they are there
> --------------------------------------------------------------------------------------------------------------
>
> Key: ENERGYINTEROP-369
> URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-369
> Project: OASIS Energy Interoperation TC
> Issue Type: Bug
> Components: schema
> Affects Versions: wd22
> Environment: Bruce Bartell
> Reporter: Bruce Bartell
> Assignee: William Cox
> Priority: Minor
>
> EIOptout:contractName - what is this for?
> venID is in twice once at root and again in EIOpt as 1->*. The defintions do nto match.
> The definition in the recurring element reads like a customer account ID ("If this ProgramConstraint is associated with a specific ParticipantAccount then this is the
> identifier of the ParticipantAccount that it is associated with.)
> validDateTimes "These are the date/times during which a DR Event may be issued. If undefined then it is assumed that the DR Event may be issued at any time except as specified by the other constraints such as the black out dates and times." This looks like a program attribute.
> maxConsecutiveDaysFilter No defintion. Enumerator of Accept or Reject. Accept or reject what?
> blackOutDateTimes Redundant with optOutSchedule. I thought we were going to use this as Resourse Constraint?
--
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]