[OASIS Issue Tracker] Commented: (ENERGYINTEROP-504) Add Reading Type as optional element in ei:Market Context for use in eiQuote

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

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

Toby Considine commented on ENERGYINTEROP-504:
----------------------------------------------

We can't be chained at the hip to a 3rd party standard not developed in an SDO. On the other hand, we need to support application-specific communications. 

A continuing concern is that we cannot have communications that merely duplicate the EI Payloads, because that would require that we create processes to validate the overlapping semantics. If a VEN approves/accepts an event, then the information on the application specific information must be what is in the event.

I propose that we 

1)	Create an optional abstract applicationInfo element in the event.
2)	Develop strong conformance language that the applicationInfo MUST NOT restate information already in the event
3)	Develop strong conformance language that when information is adjacent to Energy Interoperation information, that the semantics must be the same as EI uses (which encompasses WS-Calendar conformance and EMIX conformance)

I would not mind having a better name for the applicationInfo element.

I also recommend that we (Bruce) prepare a brief tech note using, perhaps, the artifact that Bruce has already prepared (as modified to meet the conformance) as an theoretical example...


> Add Reading Type as optional element in ei:Market Context for use in eiQuote
> ----------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-504
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-504
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: schema
>    Affects Versions: CSD02/PR02
>         Environment: Bruce Bartell
>            Reporter: Bruce Bartell
>            Assignee: William Cox
>
> Add Reading Type as part of ei:MarketContext for optional use in eiQuote.
> The xsd with the suggested structures is contributed at: http://www.oasis-open.org/apps/org/workgroup/energyinterop/document.php?document_id=43357
> Reading Type is is a necessary component for a tariff price message in order to provide proper context of the price and to express both the nature of a product and its pricing characteristics. This  is the structure that provides for interoperability for pricing message between and among the domains defined for NAESB PAP10, EUI, ESPI, SE2 and others.

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