[OASIS Issue Tracker] Commented: (EMIX-512) PAP03 Req #43: apparentgap; markets redux

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

    [ http://tools.oasis-open.org/issues/browse/EMIX-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27003#action_27003 ] 

Joshua Phillips commented on EMIX-512:
--------------------------------------

When I think of price model and emix's capability to communicate IRC Market information I am concerned about how emix may coincidentally transmogrify the information model submitted by the IRC.  While it is outrageous to suggest it could support all markets, it is expected it could support several currently operating markets which may be expected to utilize the functionality.   Some IRC concerns are explained as EI issues for resolution not EMIX.  However with EI not yet addressing these concerns, how can an EMIX schema be deemed complete as 1.0.  Other issues may arise in EI that must be resolved in EMIX.  Resolving such an issue could break or be in direct conflict EMIX 1.0.  

> PAP03 Req #43: apparent gap; markets redux
> ------------------------------------------
>
>                 Key: EMIX-512
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-512
>             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 support quotation of price, quantity, and characteristics across markets.
> Apparent Gap:
> See verification of Req#35, Req#36. Is support for all markets guaranteed? What if the other markets can not process EMIX+WS-Calendar due to incomprehensible semantics/terms?

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