FW: A couple of corrections to WD 36 schema

Thanks

"A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away."
- Antoine de
Saint-Exupery
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:

Phone: (919)619-2104
http://www.tcnine.com/ blog: www.NewDaedalus.com
From:
Edward G. Cazalet [mailto:]
Sent:  Tuesday, September 06, 2011 12:16 PM
To:  
Cc:  
Subject:  A couple of corrections to WD 36 schema

See minor typos in doc in terms.xsd

< xs:documentation
>Terms are extrinsic to the product delivery but effect how each party interacts with others. Terms may be tied to basic operational needs, or state schedules of availability, or suggest limits on bids and p rices  acceptable. It is possible for a given party to offers  its  service to the market with different Terms and thereby receive different values. Terms may originate with the buyer, the seller, or the market context </  xs:documentation
>

Power.xsd  Does this duplicate Ancillary Services???
-<xs:simpleType name="PowerOptionTypeEnumeratedType"> -<xs:annotation> <xs:documentation>Power Reserve Options</xs:documentation> </xs:annotation> -<xs:restriction base="xs:string"> <xs:enumeration value="SpinningReserve"/> <xs:enumeration value="NonSpinningReserve"/> <xs:enumeration value="OperatingReserve"/> <xs:enumeration value="DemandResponse"/> </xs:restriction> </xs:simpleType>

I think we can delete this now that we are explicit about Ancillary Services.


Edward G. Cazalet, Ph.D.
101 First Street, Suite 552
Los
Altos, CA 94022
650-949-5274
cell: 408-621-2772

www.cazalet.com