← Prev in month
← Prev in thread
Next in thread →
Next in month →
Application-specific data in Streams and ENERGYINTEROP-504
I like the applicationSpecificSignalBase in the following fragment from EiClasses.xsd, wd29-wip2. In a previous email I said that in wd29-wip2 the SignalLevelType is (largely) an xs:choice; I've highlighted the element that's the subject of this email in Bold Italic . <xs:complexType name= SignalLevelType > <xs:annotation> <xs:documentation>The Signal Level is a Stream Payload holding a single value.</xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base= eitc:StreamPayloadBaseType > <xs:sequence> <xs:choice minOccurs= 1 maxOccurs= 1 > <xs:element ref= eitc:signalDelta minOccurs= 0 maxOccurs= 1 /> <xs:element ref= eitc:signalSetpoint minOccurs= 0 maxOccurs= 1 /> <xs:element ref= eitc:signalPercent minOccurs= 0 maxOccurs= 1 /> <xs:element ref= eitc:programLevel minOccurs= 0 maxOccurs= 1 /> <xs:element ref= emix:quantity minOccurs= 0 maxOccurs= 1 /> <xs:element ref= emix:priceBase minOccurs= 0 maxOccurs= 1 /> <xs:element ref= emix:productDescription minOccurs= 0 maxOccurs= 1 /> <xs:element ref= eitc:applicationSpecificSignalBase minOccurs= 0 maxOccurs= 1 /> </xs:choice> <xs:element ref= emix:itemBase minOccurs= 0 maxOccurs= 1 /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> This seems to fully address Bruce's ENERGYINTEROP-504 issue on information that needs to be filled in for SEP2 and other application environments ? One can use a signal stream with application specific information, with outbound information in an event Stream and return information in a feedback Stream. We've discussed the importance of this for integration and the care and feeding of (specifically) SEP2. Thoughts? Thanks! bill -- William Cox Email: Web: http://www.CoxSoftwareArchitects.com +1 862 485 3696 mobile +1 908 277 3460 fax
← Prev in month
← Prev in thread
Next in thread →
Next in month →