energyinterop — archive

[Toby Considine]

Comments on WD08 Consider moving one-sentence paragrapg 217-219 to be the topic [first] sentence of paragraph 213-216. Line 246. Consider replacing "have been unique systems" with "have not been interoperable" Consider replacing all of section 1.63 and associated subsections with: WS-Calendar expresses events and sequences to support machine-to-machine (M2M) negotiation of schedules while being semantically compatible with human schedules, i.e., [iCalendar]. The TC produced schemas to support messages that are nearly identical to those used in human schedules, a more abstract Platform Independent Model (PIM) and a compact _expression_, [Streams], to support remote telemetry and projections. WS-Calendar conveys domain specific information in a per-event payload. An essential concept of WS-Calendar is inheritance, by which a starting time can be applied to an existing message, or by which all events in a sequence can be start with the same payload. Inheritance is used to “complete” a partial message during negotiation. CTS makes use of this to apply common market product across a sequence, or to convey a specific starting time to a market product. CTS messages conform to the Streams format. 484: DO we want to reference that Resources, as defined in EMIX, are extensible? 487 [Table] Consider noting that while this specification may refer to a Matching Engine, the structure and algorithms of the matching engine are out of scope. Bravo on Paragraph at 515 522: "Facets defined in CTS" 522: Why not EiQuote?????? 588: green Warrant. Capitalize both or neither. Footnote 8: "more efficent than" Notable EI Interaction left out: Failure to Deliver. Transaction 47 - I ordered 10 kW of power and I was only able to take delivery of 7 kW.