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] Updated: (ENERGYINTEROP-513) The eiCreateAvailPayload has one confusing issue: It is our understanding that the VEN would specify the behavior characteristic (Force, etc) but behavior does not appear in the create payload.


     [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated ENERGYINTEROP-513:
--------------------------------------

    Component/s: model
    Description: 
The eiCreateAvailPayload has one confusing issue: It is our understanding that the VEN would specify the behavior characteristic (Force, etc) but behavior does not appear in the create payload. Oddly it does get returned in eiCreatedAvailPayload. It doesn't seem to make sense that the OpenADR Alliance Comments on EI v1.0, July 8, 2011  Page | 3 VTN would dictate how events get mapped to the VENs availability schedule. More description is needed.

NOTE 20111002: Per ENERGYINTEROP-512 "Force" has been removed from the enumeration.

  was:The eiCreateAvailPayload has one confusing issue: It is our understanding that the VEN would specify the behavior characteristic (Force, etc) but behavior does not appear in the create payload. Oddly it does get returned in eiCreatedAvailPayload. It doesn't seem to make sense that the OpenADR Alliance Comments on EI v1.0, July 8, 2011  Page | 3 VTN would dictate how events get mapped to the VENs availability schedule. More description is needed.

       Assignee: Toby Considine  (was: William Cox)

ENERGYINTEROP-512 as applied eliminates Force from the enumeration.

This behavior may be defined in the program, which would suggest in the StandardTerms for the marketContext, or it may be done by the VEN as needed. The behavior needs to be unambiguous.

In wd28, EiAvailBehavior is not used.  Passing to Toby for comment.

> The eiCreateAvailPayload has one confusing issue: It is our understanding that the VEN would specify the behavior characteristic (Force, etc) but behavior does not appear in the create payload. 
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-513
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-513
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Sub-task
>          Components: model, schema
>    Affects Versions: wd27
>         Environment: OpenADR
>            Reporter: Toby Considine
>            Assignee: Toby Considine
>             Fix For: wd29
>
>
> The eiCreateAvailPayload has one confusing issue: It is our understanding that the VEN would specify the behavior characteristic (Force, etc) but behavior does not appear in the create payload. Oddly it does get returned in eiCreatedAvailPayload. It doesn't seem to make sense that the OpenADR Alliance Comments on EI v1.0, July 8, 2011  Page | 3 VTN would dictate how events get mapped to the VENs availability schedule. More description is needed.
> NOTE 20111002: Per ENERGYINTEROP-512 "Force" has been removed from the enumeration.

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