[OASIS Issue Tracker] Commented: (ENERGYINTEROP-369) Opt containsadditional elements that are not in the submitted models - need explanationon why they are there

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Toby Considine commented on ENERGYINTEROP-369:
----------------------------------------------

Good catch, Bruce.

Per our conversation last night, all should have been using the eitc:BusinessScheduleType instead of the emix:BusinessScheduleType. The eitc:BusinessScheduleType was created as you and I discussed (an array of intervals and an availability.

<!-- 2.2 Market Context Defintion -->
<xs:element name="businesSchedule" type="eitc:BusinessScheduleType"/>
<xs:complexType name="BusinessScheduleType">
	<xs:sequence>
		<xs:element ref="xcal:vavailability" minOccurs="0" maxOccurs="unbounded">
			<xs:annotation>
				<xs:documentation>Regular periods of time when a resource is either available to be scheduled or always unavailable</xs:documentation>
				<xs:appinfo>As of this draft, the vavailability object in WS-Calendar is not fiully usable. Comments have been submitted to the groups working on that standard. The Intervals below can be used instead</xs:appinfo>
			</xs:annotation>
		</xs:element>
		<xs:element ref="xcal:interval" minOccurs="0" maxOccurs="unbounded">
			<xs:annotation>
				<xs:documentation>Unique Intervals</xs:documentation>
				<xs:appinfo>As of this draft, the vavailability object in WS-Calendar is defective and not usable. The vavailability artifact expresses regular periods of time when a resource is either available to be scheduled or always unavailable. Comments have been submuitted to the groups woring on that standard</xs:appinfo>
			</xs:annotation>
		</xs:element>
	</xs:sequence>
</xs:complexType>

When I look at that, I wonder i we should be using the constrained eitc:interval we also discussed last night.

The secret wip7 (on my hard drive) now has changed to the two occurrences (in RuleSet as well as in Opt) to use the eitc version.




> 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