OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-423) Opt Out forindividual event; not in opt out message; is it in feedback?



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

William Cox commented on ENERGYINTEROP-423:
-------------------------------------------

URI for WIP2 is http://www.oasis-open.org/committees/download.php/42983/wd26_ed_wip2.zip. WIP 1 was deleted, so there's no note on the proposed change.

Trying to extract only information with respect to this issue, it seems that the proposed additional element for the EiCreatedEventPayloadType, is a mandatory ei:EiOptType - values OptIn and OptOut - so you have to send one or the other. This is confusing with respect to the EiOpt service, as this does not affect the Availability or Opt system except for this one event, and requires that a value be sent.

Quoting from WIP2 EiPayloads.xsd:

	<xs:complexType name="EiCreatedEventPayloadType">
		<xs:annotation>
			<xs:documentation>This is the payload for the EiEvent Service CreatedEvent response..</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="eventCreatedResponse" type="eitc:EiResponseType" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>This is an acknowledgement of the receipt of a DR notification or dispatch. It should be accompanied by any necessary provisions for non-repudiation</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="eitc:eventID" minOccurs="1" maxOccurs="1"/>
			<xs:element ref="eitc:modificationNumber" minOccurs="1" maxOccurs="1"/>
			<xs:element ref="eitc:optType"/>
		</xs:sequence>
	</xs:complexType>

The approach makes a lot of sense, but requiring that either OptIn or OptOut be sent with each message is an issue. I suggest that the element be an optional boolean called something like "NoPerformance". I think that this does exactly what's requested and is more clear.

> Opt Out for individual event; not in opt out message; is it in feedback?
> ------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-423
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-423
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>         Environment: Bruce Bartell
>            Reporter: Bruce Bartell
>            Assignee: Bruce Bartell
>
> Need the ability to opt out for an individual event. The event does not seem to be in the opt out message. Are we handling this through feedback message?

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