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

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

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


Subject: RE: [energyinterop] Draft of EiResponseType and of EiFeedback payloads


So, is this the proposal?

 

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:foo="tc.response.proposal" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:eitc="http://docs.oasis-open.org/ns/energyinterop/201103" xmlns:emix="http://docs.oasis-open.org/ns/emix" targetNamespace="tc.response.proposal" elementFormDefault="qualified" attributeFormDefault="unqualified">

            <xs:import namespace="http://docs.oasis-open.org/ns/energyinterop/201103" schemaLocation="EiClasses.xsd"/>

            <xs:import namespace="http://docs.oasis-open.org/ns/emix" schemaLocation="EMIX/emix.xsd"/>

            <xs:element name="eiResponse" type="foo:EiResponseType"/>

            <xs:complexType name="EiResponseType">

                        <xs:annotation>

                                    <xs:documentation>Event Performance is the actual energy use within each interval during the event.</xs:documentation>

                        </xs:annotation>

                        <xs:sequence>

                                    <xs:element ref="foo:response" minOccurs="1" maxOccurs="1"/>

                                    <xs:element ref="foo:description" minOccurs="1" maxOccurs="1"/>

                                    <xs:element ref="foo:eiTermViolated" minOccurs="1" maxOccurs="unbounded"/>

                        </xs:sequence>

            </xs:complexType>

            <xs:element name="eiTermViolated" type="foo:EiTermViolatedType"/>

            <xs:complexType name="EiTermViolatedType">

                        <xs:sequence>

                                    <xs:element ref="emix:baseTerm" minOccurs="1" maxOccurs="1"/>

                                    <xs:element ref="foo:description" minOccurs="1" maxOccurs="1"/>

                        </xs:sequence>

            </xs:complexType>

            <!-- Response -->

            <xs:element name="response" type="foo:ResponseEnumeratedType"/>

            <xs:simpleType name="ResponseEnumeratedType">

                        <xs:restriction base="xs:token">

                                    <xs:enumeration value="yes"/>

                                    <xs:enumeration value="no"/>

                                    <xs:enumeration value="maybe"/>

                        </xs:restriction>

            </xs:simpleType>

            <!-- Description -->

            <xs:element name="description" type="xs:string"/>

</xs:schema>

 

 

 


"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


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

 

 

From: William Cox [mailto:wtcox@CoxSoftwareArchitects.com]
Sent: Monday, June 06, 2011 1:33 AM
To: EITC
Subject: [energyinterop] Draft of EiResponseType and of EiFeedback payloads

 

The EiResponseType is a first draft out of the "ReponseString" (or "AckAck") group discussion last Thursday.

The EiFeedback payloads were in progress during the discussion on reporting and measurement intervals; the EiFeedbackType is pretty much Ed Koch's proposal, with some notes on what needs to evolve.

Comments welcome.  These are JPGs from an EA model.

Thanks!

bill cox

--
William Cox
Email: wtcox@CoxSoftwareArchitects.com
Web: http://www.CoxSoftwareArchitects.com
+1 862 485 3696 mobile
+1 908 277 3460 fax



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