[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [energyinterop] Notes on WD08 draft AND Work in progress on WD09 + PDF
Toby -
I suspect you're right, but we have to focus our efforts on what
makes sense and is reasonably common. Please write up proposed
text and share with the list (or edit into WD09 WIP).
I've had a request for the PDF for WD09 WIP, attached.
Thanks!
bill
I think we will never achieve the interoperability goals of this specification if we do not at least give guidance on Delivery and Position.
From: energyinterop@lists.oasis-open.org <energyinterop@lists.oasis-open.org> on behalf of William Cox <wtcox@coxsoftwarearchitects.com>
Sent: Monday, August 16, 2021 12:12 PM
To: energyinterop@lists.oasis-open.org <energyinterop@lists.oasis-open.org>
Subject: Re: [energyinterop] Notes on WD08 draft AND Work in progress on WD09Toby -
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:
DoneComments 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 with some rewriteConsider 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.
Reworded so CTS 1.0 uses the CTS definition, and referenced extension via standard object484: DO we want to reference that Resources, as defined in EMIX, are extensible?
Done487 [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
Done522: "Facets defined in CTS"
Added text to last line of table 2-2.522: Why not EiQuote??????
Both, and made Italic rather than quoted.588: green Warrant. Capitalize both or neither.
Done. Now Footnote 7
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.
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: wtcox@CoxSoftwareArchitects.com
Web: http://www.CoxSoftwareArchitects.com
+1 862 485 3696 mobile
William Cox
Email: wtcox@CoxSoftwareArchitects.com
Web: http://www.CoxSoftwareArchitects.com
+1 862 485 3696 mobile
Attachment:
ei-cts-v1.0-wd09-WIP-WTC.pdf
Description: Adobe PDF document
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]