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


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

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

Subject: Re: [energyinterop] Conformance and Market Contexts and Program descriptions

Hi Toby,

I look a this differently and much simpler requirement. The constraints we want to add are purely based on the need of the markets (and defined by them). Of course, there will be many more that the future markets will determine and that is part of every standardization process and most of the requirements included in EI -- things evolve as we move on. Here, wer're defining the requirements for both current and future market needs.

The real question is what are the minimum set of requirements that a market needs right now? 

From the ones you've suggested, I would say (plus more) the following as it relates to a specific program (or universal) per resource (not sure if it has to go all the way to the asset): 

- Availability Schedule (includes both date/time such as black-out dates/times)

- Minimum Notification Time (prior to the event)

- Maximum Run Time (duration/window during the event)

- Maximum participation days for consecutive event days

There might be others that the TC may determine are necessary. 



On Mon, Apr 25, 2011 at 7:42 AM, Toby Considine <Toby.Considine@gmail.com> wrote:

Some off-list comments have led me to think about the number of possible constraints, wand whether every system needs to understand all of them. This concern is closely allied with the related issue that Constraints are extensible, so a given market could create their own.


In some domains, people use “must understand” flags on some semantic elements, suggesting that “If you do not understand this, you must refuse to accept request”. WS-RM carefully distinguishes between “I received the message intact” and “I received the message and understood it”.




If there are forty kinds of constraints, and a given market context (with its specific market rules) decides that *it* wants to use only 3 of them, say (arbitrarily):


Availability Schedule

Minimum Notification Time

Maximum Run Time


Is there a way to express in the market rules that only those three are accepted? Is there a way for an VEN to communicate that it does not understand some constraints?


Is this in our out of scope?




“The single biggest problem in communication is the illusion that it has taken place.”
– George Bernard Shaw.

Toby Considine
TC9, Inc

TC Chair: oBIX & WS-Calendar

TC Editor: EMIX, EnergyInterop

U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee


Email: Toby.Considine@gmail.com
Phone: (919)619-2104

blog: www.NewDaedalus.com



Rish Ghatikar
Lawrence Berkeley National Laboratory
1 Cyclotron Road, MS: 90-3111, Berkeley, CA 94720
GGhatikar@lbl.gov | +1 510.486.6768 | +1 510.486.4089 [fax]

This email is intended for the addressee only and may contain confidential information and should not be copied without permission. If you are not the intended recipient, please contact the sender as soon as possible and delete the email from computer[s].

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