Major 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.
Please review and indicate of Report Description now meets this concern
Opening all Deferred Items following fote out of WD25 as a CSD for PR
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
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.
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.
Moved to closed per unanimous vote (Aaron no longer present) in TC Meeting 2011-11-09