Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: wd32
    • Fix Version/s: wd32
    • Component/s: model
    • Labels:
      None
    • Environment:

      Ed Koch

    • Proposal:
      Hide

      Evaluate the next version of the schema against the above requirements and adjust as necessary.

      Show
      Evaluate the next version of the schema against the above requirements and adjust as necessary.
    • Resolution:
      Hide

      Reports now have two instances of Target, one to indicate "what is being reported on", one to indicate "sources of information"

      Both are now part of reportDescription

      Show
      Reports now have two instances of Target, one to indicate "what is being reported on", one to indicate "sources of information" Both are now part of reportDescription

      Description

      There are a number of attributes associated withthe feedback which may require a bit of refactoring and refinement. Based upon our experience with telemetry feeds for DR programs the following are the necessary attributes for a particualr dataset that might appear in a feedback payload.

      = Source of the data which is described with the following attribute heirarchy:

      • DR Resouce, i.e. "VEN ID"
      • Data source name, i.e. "meter1"
      • Data set name, i.e. "power"

      = Units for the data

      = A collection (i.e. sequence) of data values. We should support a sequence of values, i.e. meter values from 1:00 to 2:00 at 5 minute intervals. Note that in this example each data value may be associated with an interval (i.e. 5 minute), but in general data values may also be at specific time instances (i.e. timestamps)

      I see most of these attributes in the existing schema, but it is not clear to me how they are organized in a fashion that satisfies the above requirements.

        Attachments

          Activity

          Hide
          toby.considine Toby Considine (Inactive) added a comment -

          Moved to closed per unanimous vote (Aaron no longer present) in TC Meeting 2011-11-09

          Show
          toby.considine Toby Considine (Inactive) added a comment - Moved to closed per unanimous vote (Aaron no longer present) in TC Meeting 2011-11-09
          Hide
          toby.considine Toby Considine (Inactive) added a comment -

          Please review and indicate of Report Description now meets this concern

          Show
          toby.considine Toby Considine (Inactive) added a comment - Please review and indicate of Report Description now meets this concern
          Hide
          toby.considine Toby Considine (Inactive) added a comment -

          Opening all Deferred Items following fote out of WD25 as a CSD for PR

          Show
          toby.considine Toby Considine (Inactive) added a comment - Opening all Deferred Items following fote out of WD25 as a CSD for PR
          Hide
          toby.considine Toby Considine (Inactive) added a comment -

          Needs more discussion than we will get to this week as part of the larger "What is a Resource conversation"

          CLosing to reopen to defer

          Show
          toby.considine Toby Considine (Inactive) added a comment - Needs more discussion than we will get to this week as part of the larger "What is a Resource conversation" CLosing to reopen to defer
          Hide
          william.cox William Cox (Inactive) added a comment -

          The source of the message is a VEN; the referenced information is with respect to (one or more) resources in wd23 terminology. So we need both.

          The VEN has a relatoinship with a particular VTN with respect to a Market Context.

          This all needs to be more clear in the specification.

          Show
          william.cox William Cox (Inactive) added a comment - The source of the message is a VEN; the referenced information is with respect to (one or more) resources in wd23 terminology. So we need both. The VEN has a relatoinship with a particular VTN with respect to a Market Context. This all needs to be more clear in the specification.
          Hide
          bbartell Bruce Bartell (Inactive) added a comment -

          I see an element of VEN ID in the Feedback message as well as Resource ID.
          Do we intend to have 2 identifiers? I thought VEN was a role defintion. Is it also going to be a party identified in the transactions?
          VEN ID is also in the Opt message.

          Show
          bbartell Bruce Bartell (Inactive) added a comment - I see an element of VEN ID in the Feedback message as well as Resource ID. Do we intend to have 2 identifiers? I thought VEN was a role defintion. Is it also going to be a party identified in the transactions? VEN ID is also in the Opt message.

            People

            • Assignee:
              ed.koch Ed Koch (Inactive)
              Reporter:
              ed.koch Ed Koch (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: