[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=25396#action_25396 ]
Bruce Bartell commented on ENERGYINTEROP-369:
---------------------------------------------
The definitions in the original issue are from the xsd file.
Comments are for Ei Schemas 20110503-1236edt.
I do not see contractName, so that's a non-issue.
venID is in twice once at root (in payloads:eiCreatedOptPayload) and again in eiClasses:EIOpt as 1->*. The defintions have been removed.
So, what is venID for? The opt should apply to a Resouce. Are we intending to use unique identifiers for each VEN? Also, if we need it why would it apply to the entire message and be repeated as part of an opt schedule? Suggest we remove both references.
No longer see validDateTimes or blackOutDateTimes.
But I do see some new ones:
<xs:element ref="emix:availabilitySchedule" minOccurs="0"/> --> This seem redundant with opt-in Schedule.
<xs:element ref="emix:maximumConsecutiveDurations" minOccurs="0"/> --> This seems like a Resource Contraint and should be part or Enroll/Register Resource
<xs:element ref="emix:unavailabilitySchedule" minOccurs="0"/> --> Seems redundant with opt-out schedule.
> 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: Bruce Bartell
> 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]