Emix Market Context is a string/identifier/effectively a UID – Nothing more.
EI Market Context uses standard terms from EMIX and a whole lot more. It even includes optional Application Extension elements to support a Context for a premises-based application (like SEP2).
All this does is it stated that the EMIX:Market Context is the Unique Identifier you can use to request the full complete extensible EI Market Context. Whe you don’t want it don’t send it. It is optional to send it when you want. There will probably be some post 1.0 services to “Tell me what EI market Contexts I can choose from because I want to find one that supports [SEP].
tc
"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 http://www.oasis-open.org blog: www.NewDaedalus.com |
From: energyinterop@lists.oasis-open.org [mailto:energyinterop@lists.oasis-open.org] On Behalf Of Girish Ghatikar
Sent: Tuesday, October 04, 2011 3:13 PM
To: Edward Koch
Cc: energyinterop@lists.oasis-open.org
Subject: Re: [energyinterop] EIMarketContext versus emix:MarektContext
Bill and others,
I agree with Ed. I think we debated this much at the EI TC meetings and decided that the EI TC must be able to extend the needs beyond what's being offered through other standards, while remaining compliant with those requirements. The specific case under discussion may be EiMarketContext vs. emix:MarketContext --- however, the need of the EI TC specific community may extend to other attributes. Otherwise, the boundaries are not clear.
Thanks,
-Rish
On Tue, Oct 4, 2011 at 9:59 AM, Edward Koch <ed@akuacom.com> wrote:
Bill,
I've been seeing a lot of JIRA's related to the use of EiMarketContext versus the emix:MarketContext. I don't have time to go review all the changes you are making with regards to this, but let me point out that the EiMarketContext contains the emix:MarketContext and is an extension to include attributes not defined in the emix:MarektContext, therefore as a general rule we don't lose anything by using it. The opposite can't be said if you substitute an existing reference to the EiMarketContext with a reference to the emix:MarektContext since the attributes in the EIMarektContext that are not in the emix:MarketContext sand will not be available. I fear this may be the case with respect to the Avail and Opt services. I'm not going to burn too many cycles on this now since in theory we can easily resolve it later by putting int the appropriate reference. The bigger issue is to use the notion of the market context correctly and put in the references whether it is the EIMarketContext or the emix:MarketContext.
thanks,
-ed koch
---------------------------------------------------------------------
To unsubscribe, e-mail: energyinterop-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: energyinterop-help@lists.oasis-open.org
--
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].