Re: [emix] Transactive State

EMIX is not a process, and not a prescribed set of steps, and specifies no service calls.

"It is the theory that decides what can be observed." - Albert Einstein

Toby Considine

Chair, OASIS oBIX Technical Committee
U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee

Facilities Technology Office
University of North Carolina
Chapel Hill, NC

Email: Toby.Considine@ unc.edu
Phone: (919)962-9073

From: Anne Hendry [mailto:ahendry@pacbell.net]
Sent: Thursday, June 02, 2011 4:50 PM
To: emix@lists.oasis-open.org
Subject: [emix] Transactive State

Transactive State as described in spec wd26:

"As parties use EMIX to come to an agreement and transact energy, the information required changes. An initial offer may not have a price. An agreement may not yet have a performance date. It is necessary for both parties in any communication to understand the Transactive State, i.e. what level of agreement defines the current communication."

It seems like what is being said with the Transactive State enumeration is that in order to make sense of the information that is being conveyed in a transaction one would need to know what Transactive State one was in. However, wouldn't this be obvious by where you are in sequence of Service calls (and not need to be repeated as an indicator element in EMIX)?

In which EI service calls would Transactive State be communicated?

Thanks,

-Anne

emix message