OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-409) Need to addsome attributes to Feedback



    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25582#action_25582 ] 

Bruce Bartell commented on ENERGYINTEROP-409:
---------------------------------------------

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.

> Need to add some attributes to Feedback
> ---------------------------------------
>
>                 Key: ENERGYINTEROP-409
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-409
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: model
>    Affects Versions: wd22
>            Reporter: Ed Koch 
>            Assignee: William Cox
>             Fix For: wd23
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]