RE: [emix] EI/EMIX spec wording clarification request

Excellent Point Ann. We need to use the terminology of messages for EI and EMIX carefully, if at.

On a related point will EI provide messages? EI has something to do with interactions to convey EMIX Products (incl price).

But what is normative in EI? If I use getTransaction instead of requestTransaction with the same EMIX Payload am I violating the EI spec?

Edward G. Cazalet, Ph.D.

101 First Street, Suite 552

Los Altos, CA 94022

650-949-5274

cell: 408-621-2772

ed@cazalet.com

www.cazalet.com

From: Anne Hendry [mailto:ahendry@pacbell.net]
Sent: Sunday, April 03, 2011 12:06 AM
To: emix@lists.oasis-open.org
Subject: [emix] EI/EMIX spec wording clarification request

In the Introduction sections, both the EI and EMIX specs say they each provide
"... a set of messages to communicate price ... ". ¹

To have them both say they provide the same thing blurs the line of where EI stops and EMIX starts.

The terminology could use some clarification/definition. I'd propose something more along the lines of EMIX providing "an XML vocabulary for communication of Price and Product information", or something similar, to distinguish it from getting into the messaging / communication services context of EI.

Does anyone else have suggestions/opinions on this? I think we have several issues around clarification of EI/EMIX boundaries so if that is in process perhaps this can be added to the list. I don't know how those are being tracked since they're between TCs.

-A

¹EMIX wd22 .doc lines 176-177:
"This document defines a set of messages to communicate Price and Product definition for power and energy markets ..."

¹ EI wd22 .pdf line 10:
"Energy Interoperation defines a set of messages to communicate price, reliability, and emergency conditions ..."

emix message