REMINDER - TC meeting Thursday, January 13 11am EST

energyinterop message

This is the first on the resolution of the excellent comments received on our first Public Review Draft of CTS.

As I mentioned in my previous email, we plan to address all of the editorial comments and start working from the posted WD12 which has all of those changes included.

This first part of the meeting should be quick - we will only discuss issues with the editorial category revisions.

-------- Forwarded Message --------

Subject:	Method of work for CTS Public Review Comments - first TC steps at Thursday meeting
Date:	Mon, 10 Jan 2022 18:40:28 -0500
From:	William Cox <wtcox@coxsoftwarearchitects.com>
To:	EITC <energyinterop@lists.oasis-open.org>

All comments are in Jira - Go to https://issues.oasis-open.org/projects/ENERGYINTEROP/ for base. You need to log in to comment or make changes; use your Workspace login credentials.

https://issues.oasis-open.org/issues/?jql=project%20%3D%20ENERGYINTEROP%20AND%20status%20in%20(Open%2C%20New)%20ORDER%20BY%20lastViewed%20DESC gets a useful list view. Click on the Key column header to sort by issue number.

The public review draft is at
âÂÂÂ http://docs.oasis-open.org/energyinterop/ei-cts/v1.0/ei-cts-v1.0.html
âÂÂÂ http://docs.oasis-open.org/energyinterop/ei-cts/v1.0/ei-cts-v1.0.pdf (use for line numbers)

Work plan:
a)ÂÂÂ Divide into the following categories; refactor as needed. (Most editorial/explanatory (EDITORIAL) comments have been factored out already.)
b)ÂÂÂ Refactor as necessary to address OTHER category and cohesion of resolution.
c)ÂÂÂ Assign comment areas
d)ÂÂÂ Process EDITORIAL/clarification first. Approve planned resolutions in TC meeting motion (as a group, separate any exceptions called out by TC), then generate a new clean Working Draft with editorial accepted. This is planned for January 10, 2022 posting.
e)ÂÂÂ Work in parallel on the categories.

First draft of categories. We'll combine or create new ones as needing.

1)ÂÂÂ EDITORIAL comments related to editorial and explanatory material including clarifications. Clarification of whatâs intended. Key words include facet service
2)ÂÂÂ PREREQUISITES including comments on _expression_ of units, mantissa and granularity for quantities and prices, and Standard Terms (comments related to non-hour-aligned markets, etc.)
3)ÂÂÂ RESOURCE for resource-product-instrument comments. Notes on how EMIX is clustered and factored differently to enable more dynamic market discovery and interaction.
4)ÂÂÂ CONFORMANCE both to base standards and to CTS. Include clarified discussion on refactoring and applicability to base standards (similar to e.g. IEC 62746-10-3 mappings)
5)ÂÂÂ OUTSIDE CTS, for example, constraints on market behaviorânotes on market matching algorithms may be a standard termâas might be scale/decimal faction length
6)ÂÂÂ FACETS including facet description. For example, clarify the Position facet, and address comments on Tender and Transaction and other facets (except Market Information below)
7)ÂÂÂ MARKET INFORMATION facet comments
8)ÂÂÂ OTHER

Toby has already split out editorial comments - so after Thursday we'll be working on the substantive comments.

Thanks!

bill

William CoxÂ

Email: wtcox@CoxSoftwareArchitects.comÂ

Web: http://www.CoxSoftwareArchitects.comÂ

+1 862 485 3696 mobile