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] Updated: (ENERGYINTEROP-504) Add Reading Type as optional element in ei:Market Context for use in eiQuote


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

William Cox updated ENERGYINTEROP-504:
--------------------------------------

    Description: 
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.

  was:
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 necassary 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.

       Assignee: Bruce Bartell  (was: William Cox)

Not sure what this means. ReadingType expresses information already expressed in EMIX and EI, and is not duplicated elsewhere.

A precise and identical representation of ReadingType is not required for conformance to NAESB PAP10; the information is already there.

is the proposal to add an optional element readingType: string ?

> 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: Bruce Bartell
>             Fix For: wd28
>
>
> 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

        


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