Collector for rules involving dtStart, dtEnd and Duration

XMLWordPrintable

    • Type: Improvement
    • Resolution: Applied
    • Priority: Major
    • wd21
    • Affects Version/s: pr02
    • Component/s: None
    • None
    • Hide

      Closing issue because all sub-issues closed.

      Show
      Closing issue because all sub-issues closed.

      1.
      		 All - Does the standard assuming any type of industry? Specification of interoperability for the energy industry is lacking. Certain assumptions will leave the interoperability more difficult and costly, rather than generic. Sub-task Closed Toby Considine (Inactive)
      2.
      		 Section 3.1.1 - Choosing one format would benefit interoperability. Sub-task Closed Toby Considine (Inactive)
      3.
      		 Section 2.2.1 - "no representation as whether UTC or local time are more appropriate " - A hard decision here would have provided lots of benefit to interoperability. Flexibility will not help with interoperability. Sub-task Closed Toby Considine (Inactive)
      4.
      		 All - The standard provides every possible method to define intervals and schedules while this is clever it does not increase the chance of interoperability. Sub-task Closed Toby Considine (Inactive)
      5.
      		 Table 1.6 - The definition relate to implementation e.g. "need inheritance" or "not complete" rather than the information that is undefined in this state Sub-task Closed Toby Considine (Inactive)
      6.
      		 Abstract - If there is nothing energy sector specific in this standard what benefit does it provide over the other standards mentioned. Sub-task Closed Toby Considine (Inactive)
      7.
      		 All - the standard does not effectively address the time period definitions that are particular to the wholesale energy markets Sub-task Closed Toby Considine (Inactive)
      8.
      		 Line 2678 - "Intervals SHALL NOT include an END time." Sub-task Closed Toby Considine (Inactive)
      9.
      		 Line 858 - dtEnd says "SCHEDULED completion time..." is this implied or computed or expressed? dtStart simply says "Start time" Sub-task Closed Toby Considine (Inactive)
      10.
      		 Line 858 - dtEnd is not listed and optional, as are dtStart and duration (DtStart and Duration?) Sub-task Closed Toby Considine (Inactive)
      11.
      		 Line 368 - Elsewhere it's recommended that intervals have DtStart and Duration (either of which can be filled in through eg inheritance), but we see later an odd blend (line 858 adds DtEnd to the mix). This needs to be clear and consistent across the doc. Sub-task Closed Toby Considine (Inactive)
      12.
      		 Line 368 - Both DtStart and Duration are "optional". What precisely does that mean? That neither need to be present? we find later that these values can be inherited from a gluon, but at this point "optional" seems to mean "no value is required" Sub-task Closed Toby Considine (Inactive)
      13.
      		 Line 858 - it is unclear why there is a restriction on using only dtStart and duration, and dtEnd and duration, but NOT dtStart and dtEnd. Sub-task Closed Toby Considine (Inactive)
      14.
      		 Line 881 - The "optionality" of dtEnd and duration is not clearly defined Sub-task Closed Toby Considine (Inactive)

          Assignee:
          Toby Considine (Inactive)
          Reporter:
          Toby Considine (Inactive)
          Votes:
          0 Vote for this issue
          Watchers:
          0 Start watching this issue

            Created:
            Updated:
            Resolved: