OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emix message

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


Subject: [OASIS Issue Tracker] Created: (EMIX-315) WD 19 .doc Line 171:reword to clarify scope w.r.t. EI


WD 19 .doc Line 171: reword to clarify scope w.r.t. EI
------------------------------------------------------

                 Key: EMIX-315
                 URL: http://tools.oasis-open.org/issues/browse/EMIX-315
             Project: OASIS Energy Market Information Exchange (eMIX) TC
          Issue Type: Improvement
            Reporter: Anne Hendry 
            Assignee: William Cox
            Priority: Minor


Line 171 states:
"This document defines a set of messages to communicate Price and Product definition ..."
This closely resembles line 10 in the EI spec (wd22 pdf):
"Energy Interop defines messages to communicate price ..."
I thought EMIX was defining the payload,
more along the lines of how it's stated in Line 331:
EMIX defines the information for use in messages that convey this
[Price and product] actionable information.
and Line 375:
EMIX is not concerned with the processes whereby an actor provides
the products and resources it describes. EMIX is an information model
that assumes conveyance within a service-based environment.
So this first sentence confuses scope.


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