[OASIS Issue Tracker] Commented: (EMIX-504) PAP03 Req #31: apparentgap; metering

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

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

Toby Considine commented on EMIX-504:
-------------------------------------

A recurring motif in recentyl reported issues is Composition. EMIX is assumed to be composed with other specifications to meet needs. As applications potentially built on EMIX do not assume that all information must come from the same source, it does not require that all information be in every packet. 

That said, the EMIX Delivery information model is compatibble with the minimal semantic model defined in NAESB PAP10. 

Also recommend close no change. 

> PAP03 Req #31: apparent gap; metering
> -------------------------------------
>
>                 Key: EMIX-504
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-504
>             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] meter communications.
> Apparent Gap:
> Specification is not reusing recognized and deployed semantics from IEC CIM, NAESB, SEP2, ANSI C12.19 or DLMS/COSEM, making this model not useful in meter communications.

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