[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=25729#action_25729 ]
Girish Ghatikar commented on ENERGYINTEROP-369:
------------------------------------------------
Let's first, replace (as per Toby's comment on 04/05): "fix the spelling of eitc:businesSchedule to businessSchedule." It doesn't seem to be the case in the latest WD23.
Second, how does the VEN ID and Resource ID resolve when the signals cascade through different VENs (e.g., Service provider to aggregator to a building)? I would think that the VEN ID is receiver of the signal and the resource ID is the "end or culminating" point of the signal at the ESI level. T I would think that if there is a direct VTN to resource communication, the VEN ID is same as resource ID. We need to also account how the telemetry requirements for A/S markets are handled in return. This is an important requirement for markets that offer incentives to enable automation for DR for customers and also for the purposes of certification and testing.
> 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]