[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (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:comment-tabpanel&focusedCommentId=27936#action_27936 ]
Toby Considine commented on ENERGYINTEROP-504:
----------------------------------------------
The original document implies a reading type considerable more complicated than a string.
Is the proposal to URL encode a long XML artifact and pretend it is a string? Per the proposed annotation:
Detailed description for a type of a reading value. Values in attributes allow for creation of recommended codes to be used for identifying reading value types as follows: <macroPeriod>.<aggregate>.<measuringPeriod>.<accumulation>.<flowDirection>.<commodity>.<measurementKind>.<interharmonic.numerator>.<interharmonic.denominator>.<argument.numerator>.<argument.denominator>.<tou>.<cpp>.<consumptionTier>.<phases>.<multiplier>.<unit>.<currency>.
1) I don't think we should be encoding and ignoring large artiifacts to tunnel them. Doing so is a barrier to interoperation.
2) The proposal seems to indicate that it occurs in the Market Context, in the Signal, and in each Interval. Is this required?
3) Several of the annotations are obscure.
Or perhaps I am misunderstanding the proposal and.or the artifact.
> 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]