[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [energyinterop] Squeezing the Message
I think (3) states that we have. Of course, more squeezing is good. It is noteworthy that there are specific use cases where all the flexibility that comes with verbose expressions is still required. For example, it is difficult to compress tiers because you still need to include multiple highwater marks for each interval. The challenge is maintain the flexibility that we must, while allowing the vast majority of messages to get much much smaller. tc "He who fights with monsters should look to it that he himself does not become a monster, and if you stare long into an abyss, the abyss also stares into you." - Fredrich Nietzche
From: Koch, Edward [mailto:Edward.Koch@Honeywell.com] I think we have to go beyond what is specified in EMIX. When can we get the next version of the EI schema so we can make sure we can generate the XML we agreed upon last week and generate our EI conformance statements around that. Thanks, -ed Koch From: Toby Considine [mailto:tobyconsidine@gmail.com] On Behalf Of Toby Considine 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. 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. 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. tc “The single biggest problem in communication is the illusion that it has taken place.”
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]