-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: No Action
-
Affects Version/s: CTSPR01
-
Fix Version/s: None
-
Component/s: cts
-
Labels:
-
Resolution:
The original white paper/submission can be read in the URI under "environment"There are 30 specific recommendations in the "Specific Recommendations" section of the submitted Hammerstrom paper. I have numbered them all for traceability as I recombine them into specific issues. The original white paper/submission can be read in the URI under "environment"
28. Figure 11-2 (and elsewhere re payload intervals): I’ve observed that CTS streams reference integer interval series, whereas many interaction payloads reference Interval objects. It is unclear to me what, if anything, associates a Party’s CTS streams to specific Instrument Interval objects.
The reference to Figure 11-2 Delivery Facet Payloads (https://docs.oasis-open.org/energyinterop/ei-cts/v1.0/csd01/ei-cts-v1.0-csd01.html#_Toc85711716) could also included Figure 10-2 Position Facet Payloads (https://docs.oasis-open.org/energyinterop/ei-cts/v1.0/csd01/ei-cts-v1.0-csd01.html#_Toc85711714), as these are essentially similar, and differ from the CTS Stream of 1 or more elements found elsewhere in the specification.
These are the payloads that use a "Bounding Interval" to describe the domain of interest; the reply provides a CtsStream including all intervals that fall within the closed boundingInterval.
A CTS stream does appear to be useful to describe that bounding behavior, as it is exactly one interval fully specified.
Transition all APPLIED to CLOSED per Energy Interoperation TC Motion April 28, 2022.
The reference to Figure 11-2 Delivery Facet Payloads (https://docs.oasis-open.org/energyinterop/ei-cts/v1.0/csd01/ei-cts-v1.0-csd01.html#_Toc85711716) could also included Figure 10-2 Position Facet Payloads (https://docs.oasis-open.org/energyinterop/ei-cts/v1.0/csd01/ei-cts-v1.0-csd01.html#_Toc85711714), as these are essentially similar, and differ from the CTS Stream of 1 or more elements found elsewhere in the specification.
These are the payloads that use a "Bounding Interval" to describe the domain of interest; the reply provides a CtsStream including all intervals that fall within the closed boundingInterval.
A CTS stream does appear to be useful to describe that bounding behavior, as it is exactly one interval fully specified.