Inheritance and Scarcity in EMIX Sequences

["Toby Considine" <Toby.Considine@gmail.com>]

A complete power product description looks as below. In EMIX, a Product is a Product Description applied to a schedule. We have conformance rules that state that a product description can be “shared” between the Gluon and Each Interval.

 

<power:powerProductDescription>

    <power:productType>Energy</power:productType>

    <power:serviceDeliveryPoint>

        <power:node>xxxnode.idxx</power:node>

    </power:serviceDeliveryPoint>

    <power:unitEnergyPrice>

        <emix:priceMultiplier>

            <emix:multiplier>0.111</emix:multiplier>

            <emix:marketContext>ref-to-market@context.com</emix:marketContext>

        </emix:priceMultiplier>

        <power:energyReal>

            <itemDescription>RealEnergy</itemDescription>

            <itemUnits>Wh</itemUnits>

            <scale>k</scale>

        </power:energyReal>

    </power:unitEnergyPrice>

    <power:powerReal>

        <itemDescription>RealPower</itemDescription>

        <itemUnits>W</itemUnits>

        <scale>k</scale>

        <power:powerAttributes>

            <hertz>60</hertz>

            <voltage>220</voltage>

            <ac>true</ac>

        </power:powerAttributes>

    </power:powerReal>

    <power:charges />

</power:powerProductDescription>

 

If only the price varies per Interval, it would be good to express it as below. This includes only the context and the price, and leaves everything else as defined Gluon/Product Description.

 

<power:powerProductDescription>

    <power:unitEnergyPrice>

        <emix:priceMultiplier>

            <emix:multiplier>0.111</emix:multiplier>

        </emix:priceMultiplier>

    </power:unitEnergyPrice>

</power:powerProductDescription>

 

Note that per our conformance rules, only the elements that have a changing value are expressed. All components not expressed are inherited from the gluon. A full context is provided for the expressed variables so that multiple Products Descriptions could be carried by the same Sequence.

 

For this to validate, nearly everything (perhaps everything) in each power product needs to have a minOccurs of zero. The other choice is to state explicitly that evaluation (for completeness of artifact) does not occur until after the Intervals have been assembled and the re-assembly of the virtual products completed.

 

A similar example could be made using block purchases, wherein the quantity varies by interval.

A similar example could be made using block pricing, wherein only the Price Tiers the vary by interval.

 

We have danced around this, now we need to come to a consensus how explicitly we wish to handle these cases. Any changes we make to the cardinality of product descriptions will apply to all product descriptions.

 

tc

 

---

“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