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

 


Help: OASIS Mailing Lists Help | MarkMail Help

smartgrid-interest message

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


Subject: RE: [smartgrid-interest] Price Attributes and Discovery URIs


Indeed.

 

But per the PAP09,

 

NAESB & FIX are in charge of surveying existing Price Communication from FIX/JPM/FISD/NARUC/ISO-RTO/EEI/AHAM/Zigbee/OpenHAN and delivering that summary to OASIS for EMIX. EMIX (which did not go out last night as that would have required convening over Labor Day) will then base its work on that work. There is no need to start that data gathering again.

 

EMIX will, per the PAP, coordinate with TC57 (still undefined what that means) and periodically share its work with the DEWGs for comments. NAESB remains the point for Utility groups to communicate with OASIS under the PAP09 report.

 

Hence my summary

“EMIX plans to start with models from NAESB et al.”

 

Of course, any one from any of the identified organizations can choose to participate in the Technical Committee, but if we are to meet the ambitious schedule NIST has requested, we cannot stop and re-debate the prior decisions made along the road at every step….

 

 

 

 


"A man should never be ashamed to own that he has been in the wrong, which is but saying ... that he is wiser today than yesterday." -- Jonathan Swift


Toby Considine

Chair, OASIS oBIX TC
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: Marty Burns [mailto:burnsmarty@aol.com]
Sent: Wednesday, August 12, 2009 10:29 AM
To: Toby.Considine@gmail.com; smartgrid-interest@lists.oasis-open.org
Subject: RE: [smartgrid-interest] Price Attributes and Discovery URIs

 

Toby,

 

Don’t you need to start from the collection of work that overlaps from a number of sources including OpenADR, EPRI Common Objects, NAESBE, ANSI C12, SEP 2,….?

 

Marty

 

From: Toby Considine [mailto:tobyconsidine@gmail.com] On Behalf Of Toby Considine
Sent: Wednesday, August 12, 2009 9:44 AM
To: smartgrid-interest@lists.oasis-open.org
Subject: [smartgrid-interest] Price Attributes and Discovery URIs

 

(retitled to follow conversation fork)

 

Extensible discoverable product attributes. Michael Oldak calls them Terms and Conditions. Today they are references to named tariffed products

 

(We warrant that it will be at least 40% green over the course of a month)

(You have a class C DR load shedding contract in place)

 

With future dynamic pricing, it may be an agreement to buy from the local mill stream, or to buy from the cheapest power available. You may opt for a hybrid product, in which carbon credits are sold along with watts, just as one can buy green offsets with an airline ticket today.

 

Michael argues that the choice of tariffed product may be made once and left in place for years.  If so, it would be a waste to transmit all that descriptive overhead every time.

 

Does this mean a registry in the sky? With URIs in the product to reference?

 

Dynamic transactive markets may let you pick / filter offers on the fly. This might argue for carrying a larger portion of the key attributes with the message.

 

EMIX plans to start with models from NAESB at el.

We will require compatibility with FIX protocol going forward (I assume).

The ESI (Energy Services Interface) will consume stuff and talk to BAS systems below. Whether the ESI and the BAS are collocated is an engineering decision. Whether the Enterprise is in a shim in-between is a business decision.

 

Well, so I shoot from the hip.  The committee will decide.

 

tc


"If something is not worth doing, it`s not worth doing well" - Peter Drucker


Toby Considine
TC9, Inc

Chair, OASIS oBIX Technical Committee
OASIS Technical Advisory Board

  

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

http://www.oasis-open.org

blog: www.NewDaedalus.com

 

 

From: Considine, Toby (Campus Services IT) [mailto:Toby.Considine@unc.edu]
Sent: Wednesday, August 12, 2009 8:59 AM
To: 'Brian Frank'; 'William Cox'
Cc: 'smartgrid-interest@lists.oasis-open.org'; 'Toby Considine'
Subject: RE: [smartgrid-interest] Energy Market Information Exchange Charter - supporters wanted; ready for submission to create Technical Committee

 

Restful interactions have their place. As APIs at a distance, they are clean and predictable. As part of transactional systems and open bidding markets, one needs the rest of the WS Transaction infrastructure. As part of a massively distributed delayed environment that may involve long running workflows, one may need a multi-document messaging based format.

 

Zooming in on REST is a little like zooming in on UDP, only a couple layers up. There are times when RESTful connections are exactly what one needs. There are times when they are not.

 

tc


"A man should never be ashamed to own that he has been in the wrong, which is but saying ... that he is wiser today than yesterday." -- Jonathan Swift


Toby Considine

Chair, OASIS oBIX TC
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: Brian Frank [mailto:brian@skyfoundry.com]
Sent: Wednesday, August 12, 2009 8:42 AM
To: William Cox
Cc: smartgrid-interest@lists.oasis-open.org; Toby Considine
Subject: Re: [smartgrid-interest] Energy Market Information Exchange Charter - supporters wanted; ready for submission to create Technical Committee

 


Energy Market Information Exchange is an XML vocabulary to express price and characteristics, so the means of communicating is not part of the charter.

 

I can see how that is nice in theory, but I don't understand how that works in practice.  At the very least any sophisticated modeling requires naming things.  And naming things typically implies a way to reference those named things.

 

So I guess my question is - will the model be RESTful in that "things" are named and referenced with URIs?  

 



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