energyinterop — archive

Notes on WD08 draft

From: William Cox <[email protected]>
To: [email protected]
Date: Mon, 16 Aug 2021 16:12:00 -0000

Toby - Thanks for the detailed comments. I've incorporated most of them in WD09 - WIP (Work in Progress). I'm sending this (and a diffmarked copy wrt WD08) to the list rather than clutter the repository with transitory versions. See attached as DOCX - Word Comments and Edits are fine. Thanks! bill On 8/11/21 10:59 AM, Considine, Toby wrote: Comments on WD08 Consider moving one-sentence paragrapg 217-219 to be the topic [first] sentence of paragraph 213-216. Done Line 246. Consider replacing have been unique systems with have not been interoperable Done. 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. Done with some rewrite 484: DO we want to reference that Resources, as defined in EMIX, are extensible? Reworded so CTS 1.0 uses the CTS definition, and referenced extension via standard object 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. Done Bravo on Paragraph at 515 :-) 522: Facets defined in CTS Done 522: Why not EiQuote?????? Added text to last line of table 2-2. 588: green Warrant. Capitalize both or neither. Both, and made Italic rather than quoted. Footnote 8: more efficent than Done. Now Footnote 7 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. Leaving this alone right now per discussion in August 12 meeting. The note is ambiguous - which Actor decides? Not available, or can't accept the full committed amount? Seems like an area that needs discussion. -- William Cox Email: [email protected] Web: http://www.CoxSoftwareArchitects.com +1 862 485 3696 mobile Attachment: ei-cts-v1.0-wd09-WIP-WTC-diff-wrt-wd08.docx Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document Attachment: ei-cts-v1.0-wd09-WIP-WTC.docx Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document