Details

    • Proposal:
      Hide

      Agreed

      Simplify CtsStreams by requiring the local UID (typically an integer).

      Show
      Agreed Simplify CtsStreams by requiring the local UID (typically an integer).
    • Resolution:
      Hide

      Agreed

      Simplify CtsStreams by requiring the local UID (typically an integer). (applied in ctsWD13, UML updated ctsWD14)

      Show
      Agreed Simplify CtsStreams by requiring the local UID (typically an integer). (applied in ctsWD13, UML updated ctsWD14)

      Description

      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. 

        Attachments

          Activity

          toby.considine Toby Considine (Inactive) created issue -
          WilliamCox William Cox made changes -
          Field Original Value New Value
          Labels ARCH-CONF editorial
          toby.considine Toby Considine (Inactive) made changes -
          Status New [ 10000 ] Open [ 1 ]
          toby.considine Toby Considine (Inactive) made changes -
          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.
          WilliamCox William Cox made changes -
          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.
          Hide
          WilliamCox William Cox added a comment -

          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.

          Show
          WilliamCox William Cox added a comment - 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.
          WilliamCox William Cox made changes -
          Assignee Toby Considine [ toby.considine ] William Cox [ williamcox ]
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          WilliamCox William Cox made changes -
          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).
          WilliamCox William Cox made changes -
          Status Resolved [ 5 ] Open [ 1 ]
          Hide
          WilliamCox William Cox added a comment -

          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.

          Show
          WilliamCox William Cox added a comment - 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.
          WilliamCox William Cox made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          WilliamCox William Cox made changes -
          Fix Version/s ctsWD14 [ 17669 ]
          Fix Version/s ctsWD13 [ 17668 ]
          WilliamCox William Cox made changes -
          Resolution Agreed

          Simplify CtsStreams by requiring the local UID (typically an integer). (applied in ctsWD13, UML updated ctsWD14)
          Status Resolved [ 5 ] Applied [ 10002 ]
          Hide
          WilliamCox William Cox added a comment -

          Transition all APPLIED to CLOSED per Energy Interoperation TC Motion April 28, 2022.

          Show
          WilliamCox William Cox added a comment - Transition all APPLIED to CLOSED per Energy Interoperation TC Motion April 28, 2022.
          WilliamCox William Cox made changes -
          Status Applied [ 10002 ] Closed [ 6 ]

            People

            • Assignee:
              WilliamCox William Cox
              Reporter:
              toby.considine Toby Considine (Inactive)
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: