[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Issue Comment Edited: (EMIX-505) PAP03 Req#32: apparent gap; customer site semantics
[ http://tools.oasis-open.org/issues/browse/EMIX-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26970#action_26970 ]
William Cox edited comment on EMIX-505 at 9/1/11 2:37 AM:
----------------------------------------------------------
See responses to other issues in this series.
Again, the semantics for price and product definition can be conveyed to any facility endpoint. The semantics of SEP2 appear to that of a very broad, complex application definition, and most is irrelevant to price.
Metering communication is addressed elswhere, with the same conclusion. Meters measure, and those measurements may affect the COMPUTATION of price, but not the definitions.
A draft in progress (and publicly available) demonstrates how the key perceived lack of block and tier tariff price information is delivered by EMIX; the application developer takes that information and structures it in their environment. This is how cross-domain and integration architectures work.
The semantic model internal to a domain is relevant only insofar as it is more or less expressive. Critical price and product information is conveyed by EMIX and is consumable by recipients. The December SGIP Tiger Team focused on block & tier price information as a perceived gap; see note contributed to EMIX TC for how that's mappable.
Recommend close no action.
was (Author: william.cox):
See responses to other issues in this series.
Again, the semantics for price and product definition can be conveyed to any facility endpoint. The semantics of SEP2 appear to that of a very broad, complex application definition, and most is irrelevant to price.
Metering communication is addressed elswhere, with the same conclusion. Meters measure, and those measurements may affect the COMPUTATION of price, but not the definitions.
A draft in progress (and publicly available) demonstrates how the key perceived lack of block and tier tariff price information is delivered by EMIX; the application developer takes that information and structures it in their environment. This is how cross-domain and integration architectures work.
Recommend close no action.
> PAP03 Req #32: apparent gap; customer site semantics
> ----------------------------------------------------
>
> Key: EMIX-505
> URL: http://tools.oasis-open.org/issues/browse/EMIX-505
> Project: OASIS Energy Market Information Exchange (eMIX) TC
> Issue Type: Sub-task
> Affects Versions: CSD03/PR03
> Environment: Aaron Snyder
> Reporter: Aaron Snyder
> Assignee: William Cox
>
> Requirement Text:
> The price model shall be useful in [and enable] inter-domain communications.
> Apparent Gap:
> The lack of incorporation of Customer Domain semantics in the schemas (SEP2) does not facilitate inter-domain exchange. ( per AS)
> Also note that metering communications is inter-domain as well.
--
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]