[OASIS Issue Tracker] Updated: (ENERGYINTEROP-410) Need to addcurrent value to signals

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

     [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated ENERGYINTEROP-410:
--------------------------------------

    Proposal: 
(1) Confirm that the EIEventCreatedType.createdTime can be used for representing the creation time of the payload.

NOTE: I believe what's requested is that EiCreatedEventPayload include createdTime [for that payload]. 

(2) Add creation time attribute to the EIRequestEventPayloadType

NOTE: I believe this is a request to add creationTime: xcal:DateTimeType to EiRequestEventPayloadType. Semantics need to be clear (see comments below).

(3) Make the following change to the wip7 schema:

	<xs:complexType name="EiEventSignalType">
		<xs:complexContent>
			<xs:extension base="eitc:EventBaseType">
				<xs:sequence>
					<xs:element ref="eitc:signalName"/>
					<xs:element ref="emix:marketContext" minOccurs="0"/>
					<xs:element ref="eitc:uid"/>
>>>>NEW element
				<xs:element name="currentValue">
						<xs:complexType>
							<xs:sequence>
								<xs:element ref="eitc:signalInformationBase"/>
							</xs:sequence>
						</xs:complexType>
					</xs:element>
>>>END of new element
				</xs:sequence>
				<xs:attribute ref="eitc:schemaVersion"/>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>


  was:
(1) Confirm that the EIEventCreatedType.createdTime can be used for representing the creation time of the payload.

NOTE: I believe what's requested is that EiCreatedEventPayload include createdTime [for that payload]. I don't think, however, that this can be used as an information key - the createdtime should go in EiEventType or EventDescriptorType

(2) Add creation time attribute to the EIRequestEventPayloadType

NOTE: I believe this is a request to add creationTime: xcal:DateTimeType to EiRequestEventPayloadType. Semantics need to be clear (see comments below).

(3) Make the following change to the wip7 schema:

	<xs:complexType name="EiEventSignalType">
		<xs:complexContent>
			<xs:extension base="eitc:EventBaseType">
				<xs:sequence>
					<xs:element ref="eitc:signalName"/>
					<xs:element ref="emix:marketContext" minOccurs="0"/>
					<xs:element ref="eitc:uid"/>
>>>>NEW element
				<xs:element name="currentValue">
						<xs:complexType>
							<xs:sequence>
								<xs:element ref="eitc:signalInformationBase"/>
							</xs:sequence>
						</xs:complexType>
					</xs:element>
>>>END of new element
				</xs:sequence>
				<xs:attribute ref="eitc:schemaVersion"/>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>



> Need to add current value to signals
> ------------------------------------
>
>                 Key: ENERGYINTEROP-410
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-410
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>    Affects Versions: wd22
>         Environment: Ed Koch
>            Reporter: Ed Koch 
>            Assignee: Ed Koch 
>             Fix For: wd25
>
>
> Need to add a currentValue attribute to the EIEventSignalType.
> This information reflects the current value of the signal.  It is redundant information to the singal value scheudle and was used in OpenADR 1.0 to reflects the value of the signal at the time that the payload was created.  Even though this is redundant information it makes it much easier for simple devices to determine the current signal value without needed to parse the entire singal schedule. 
> Note that I believe the payload created time is reflected in the EIEventCreated.createdTime attribute. With respect to the RequestEventPayload payload type we may be missing this attribute.
> SEE ATTACHED COMMENTS WTC

-- 
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