Anne -
Excellent point.
I couldn't find this in Jira -- would you please enter the item in
your email ( In
the Introduction sections, both the EI and EMIX specs say they
each
provide
... a set of messages to communicate price ... . )
All
--
ANY issues on the spec, schemas, etc, must be put into Jira or
there's a significant likelihood that it will be missed.
Sending an email to the list is not the same. Enter your issues in
Jira where they fit with our workflow and will be addressed.
Remember also to include specific changes in the Proposed
Resolution box - to get to it you have to edit the issue after
you've created it.
Thanks!
bill
--
William Cox
Email:
Web: http://www.CoxSoftwareArchitects.com
+1 862 485 3696 mobile
+1 908 277 3460 fax
On 4/4/11 2:21 PM, Anne Hendry wrote:
type= cite
>
Yes, I've seen quite a few similar questions go by on both lists
(EI
and EMIX). Perhaps there should be a small cross-TC team (maybe a
couple of people from each) to hammer this out.
We could really use an architecture diagram.
Perhaps such a team could create one in such a way that either it
was
two parts, one representing each TC domain and the boundary
interfaces
showing where/how the two fit together, then we could incorporate
each
into the respective specs, or one single diagram (similarly
clarifying
the interfaces) and both TCs could use the same diagram.
Either way, it's something we could use sooner than later.
-A
Ed Cazalet wrote, On 4/3/2011 5:48 AM:
[email protected]
type= cite
>
X-NONE
X-NONE
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
www.cazalet.com
From:
Anne Hendry [ mailto: ]
Sent: Sunday, April 03, 2011 12:06 AM
To:
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 ... . 1
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
1 EMIX wd22 .doc lines 176-177:
This document defines a set of messages to communicate
Price and
Product definition for power and energy markets ...
1 EI wd22 .pdf line 10:
Energy Interoperation defines a set of messages to
communicate price,
reliability, and emergency conditions ...
