[OASIS Issue Tracker] (ENERGYINTEROP-711) Streams and Intervals

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/ENERGYINTEROP-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=80713#comment-80713 ] 

William Cox edited comment on ENERGYINTEROP-711 at 2/8/22 4:57 PM:
-------------------------------------------------------------------

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.


was (Author: williamcox):
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 bother 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.

> Streams and Intervals
> ---------------------
>
>                 Key: ENERGYINTEROP-711
>                 URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-711
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: cts
>    Affects Versions: CTSPR01
>         Environment: Donald Hammerstrom https://lists.oasis-open.org/archives/energyinterop-comment/202111/msg00008/2111DJH_CTS_Review.pdf
>            Reporter: Toby Considine
>            Assignee: William Cox
>            Priority: Major
>              Labels: ARCH-CONF
>
> 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.Â



--
This message was sent by Atlassian Jira
(v8.3.3#803004)