Squeezing the Message

Ahh, so often when I clean out the pantry, I first make the mess worse, by taking everything out of the cabinets, cluttering all counters with ad hoc piles, and finally discover a new order as I put things back in. Until recently, The specifications that compose Energy Interoperation were all out on the counters, and the bloat was large.

Specific fixes for the OpenADR Bloat

1) WS-Calendar is tighter than it was. Intervals no long contain components. These changes were small, but the cumulative effect over many Intervals is large.
http://docs.oasis-open.org/ws-calendar/ws-calendar-spec/v1.0/csd04/ws-calendar-spec-v1.0-csd04.html

2) EMIX (voted out for Public Review last week) includes some specific rules for using inheritance as defined in WS-Calendar to reduce the repetition in an EMIX Schedule. (AN EMIX Schedule is defined as a Product Description applied to a WS-Calendar Sequence). In particular, the conformance section describes how elements such as Product Description, Terms, and Time Zone can be defined once in the Standard Terms associated with a Market Context, and be inherited by all Intervals.
http://www.oasis-open.org/committees/download.php/42662/emix-1-0-wd35.zip

3) The attached document is a *rough* first draft at extending the inheritance and processing rules in EMIX and WS-Calendar into Energy Interoperation. It assumes that Program Definitions can be added to Market Contexts as if they were Product Descriptions to accomplish the same message reduction for Program-Based signals.

“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

http://www.tcnine.com/
blog: www.NewDaedalus.com

energyinterop message