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-330) Allowmechanism for interactions between VEN andVTN for transactions.



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

William Cox commented on ENERGYINTEROP-330:
-------------------------------------------

Comments from base task (ENERGYINTEROP-210) Copied here:

Bill:

*Don't understand the comment/suggestion. Please create a new item including only (d). EventInfoTypeID is a class, eventStateID seems to be what you're suggesting but it's not clear how you suggest applying it. 

Rish:

d. This reflects interactions between VEN and VTN for different types of DR events/programs (e.g., VEN participation in both CPP and DBP programs). in OpenADR 1.0, the eventStateID was intended to show different types of programs/events as part of one payload - in EI we should at least consider the OpenADR style, or even better allow multiple XSDs (one for CPP and one for DBP) that a VEN can poll. The architecture needs discussion. 

Bill:

Not clear what meaning of "transaction" you're using here. The approved consistent terminology uses that for agreements. In the transaction processing sense, which seems to be close to what you're talking about, a transaction ID is maintained by the transaction manager, not among (say) a set of nodes.

Multiple XSDs adds to my confusion.  Need a clear statement of the desired effect, and the implied architecture.

> Allow mechanism for interactions between VEN andVTN for transactions.
> ---------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-330
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-330
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Sub-task
>         Environment: Girish Ghatikar wd15 lines 643-649; wd16 lines 643-649 
>            Reporter: William Cox
>            Assignee: Girish Ghatikar 
>
> Allow mechanism for interactions between VEN and VTN for transactions/ For example, the eventStateID in OpenADR 1.0 is intended to handle transactions by avoiding data payload issues. Other option (may be better) is to create a framework that allow creation of multiple XSDs for each of the types. 

-- 
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]