-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: CTSPR01
-
Component/s: cts
-
Proposal:
-
Resolution:
19. Line 452 – 3: Since conformant CTS implementations need not be owned by the same implementer, it is unwise to permit omission of the UID property. This permission to omit also appears in Tables 5-1 & 5-2.
| Field | Original Value | New Value |
|---|---|---|
| Labels | ARCH-CONF editorial |
| Status | New [ 10000 ] | Open [ 1 ] |
| Proposal | It appears that the sentence in question has the matter backward |
Agreed
In Section 5.2 (prose) As with [Streams], CTS Stream Intervals are ordered, that is the sequence of intervals is essential. Some serialization specifications, notably XML, do not require that order be preserved when deserializing a list. The UID enables proper ordering of the Stream Intervals if order is not preserved. Since conformant CTS implementations need not be owned by the same implementer, and may pass through multiple translations, the UID property is required. In table 5-2 UID An “Local UID” used to order the Interval within the Stream As conformant CTS implementations need not be owned by the same implementer, intermarket gateways (however defined) may deserialize and re-serialize to different specifications, the UID mandatory. |
| Proposal |
Agreed
In Section 5.2 (prose) As with [Streams], CTS Stream Intervals are ordered, that is the sequence of intervals is essential. Some serialization specifications, notably XML, do not require that order be preserved when deserializing a list. The UID enables proper ordering of the Stream Intervals if order is not preserved. Since conformant CTS implementations need not be owned by the same implementer, and may pass through multiple translations, the UID property is required. In table 5-2 UID An “Local UID” used to order the Interval within the Stream As conformant CTS implementations need not be owned by the same implementer, intermarket gateways (however defined) may deserialize and re-serialize to different specifications, the UID mandatory. |
Agreed
In Section 5.2 (prose) As with [Streams], CTS Stream Intervals are ordered, that is the sequence of intervals is essential. Some serialization specifications, notably XML, do not require that order be preserved when deserializing a list. The UID enables proper ordering of the Stream Intervals if order is not preserved. Since conformant CTS implementations need not be owned by the same implementer, and may pass through multiple translations, the UID property is required. In Table 5-1 changed the Note on Stream Intervals to Ordering is addressed differently in different serializations. XSD is a specific example where the order of a list is implementation defined, so the Stream Interval UID is mandatory under XML serialization. In Table 5-2 changed the Note on UID to As conformant CTS implementations need not be owned by the same implementer, intermarket gateways (however defined) may deserialize and re-serialize to different specifications, in which case the gateway MUST have knowledge as to when the UID is mandatory. |
| Assignee | Toby Considine [ toby.considine ] | William Cox [ williamcox ] |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Proposal |
Agreed
In Section 5.2 (prose) As with [Streams], CTS Stream Intervals are ordered, that is the sequence of intervals is essential. Some serialization specifications, notably XML, do not require that order be preserved when deserializing a list. The UID enables proper ordering of the Stream Intervals if order is not preserved. Since conformant CTS implementations need not be owned by the same implementer, and may pass through multiple translations, the UID property is required. In Table 5-1 changed the Note on Stream Intervals to Ordering is addressed differently in different serializations. XSD is a specific example where the order of a list is implementation defined, so the Stream Interval UID is mandatory under XML serialization. In Table 5-2 changed the Note on UID to As conformant CTS implementations need not be owned by the same implementer, intermarket gateways (however defined) may deserialize and re-serialize to different specifications, in which case the gateway MUST have knowledge as to when the UID is mandatory. |
Agreed
Simplify CtsStreams by requiring the local UID (typically an integer). |
| Status | Resolved [ 5 ] | Open [ 1 ] |
Agreed
Simplify CtsStreams by requiring the local UID (typically an integer) (technically, changing the cardinality to 1..1 in the UML model. Figure 5-1 needs to be updated along with text of Section 5.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Fix Version/s | ctsWD14 [ 17669 ] | |
| Fix Version/s | ctsWD13 [ 17668 ] |
| Resolution |
Agreed
Simplify CtsStreams by requiring the local UID (typically an integer). (applied in ctsWD13, UML updated ctsWD14) |
|
| Status | Resolved [ 5 ] | Applied [ 10002 ] |
Transition all APPLIED to CLOSED per Energy Interoperation TC Motion April 28, 2022.
| Status | Applied [ 10002 ] | Closed [ 6 ] |
In Section 5.2 (prose)
As with [Streams], CTS Stream Intervals are ordered, that is the sequence of intervals is essential. Some serialization specifications, notably XML, do not require that order be preserved when deserializing a list. The UID enables proper ordering of the Stream Intervals if order is not preserved. Since conformant CTS implementations need not be owned by the same implementer, and may pass through multiple translations, the UID property is required.
In Table 5-1 changed the Note on Stream Intervals to
Ordering is addressed differently in different serializations. XSD is a specific example where the order of a list is implementation defined, so the Stream Interval UID is mandatory under XML serialization.
In Table 5-2 changed the Note on UID to
As conformant CTS implementations need not be owned by the same implementer, intermarket gateways (however defined) may deserialize and re-serialize to different specifications, in which case the gateway MUST have knowledge as to when the UID is mandatory.