[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [energyinterop] RE: [emix] Prices Absolute, Relative, and Programmed...
If the only issue is that these
requirements are considered totally DR and hence, EI requirements, then I
concur. We will have to make sure they are
included in the EI somewhere. I have not had a chance to look into the items
listed in detail and do not expect to be on today’s call. Can we put this
into the EI hopper for next week? Bruce
Bartell Xtensible Solutions From: Toby Considine
[mailto:tobyconsidine@gmail.com] On Behalf Of
Toby Considine OK – but I need actionable information. Questions (1) 1) Is
this a proposal that EMIX lose the Program level? 2) Is
this a proposal that EMIX lose the relative price? Question (2) So how do we communicate these things that are event related… 3) Do
we create shadow objects to travel alongside EMIX that communicate schedules
for program information? 4) Do
we create shadow objects to travel alongside EMIX that communicate schedules
for relative price information? For each of the above, we could use WS-Calendar exactly as EMIX does. It would be straightforward to vote “YES” on all four.
Doing so would push the shadow objects into EI and out of EMIX, which could be
a good thing. We are at the point in these standards where editors need clean and
clear direction… tc "If something is not worth doing, it`s not worth doing well"
- Peter Drucker
From: I second Sean. On Wed, Nov 3, 2010 at 9:15 AM, Crimmins, Sean <SCrimmins@caiso.com> wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]