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-474) eiEnroll Resource Not in WD25


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

Bruce Bartell commented on ENERGYINTEROP-474:
---------------------------------------------

Based on wd32-wip1:
Capabilities need to be associated with ramps up/recovery. Same as in Figure 4-7.

There are mandatory IDs for AdminPartyID, PartyID, enrolleePartyID (in the message twice), enrollee.entityID. I only see definitions for some in the schema and no mention in the spec.
Assuming AdminPartyID is if the resource is managed by a third part. Mandatory might be tough if there is no third party, would it be the same ID as enrollee? If we have enrollee.entityID then why do we need the generic PartyID? Which of these would correlate (or hopefully be the same value as) to then VENID?

The definitions for both applicationDate and endDate are the same and refer to termination. applicationDate is probably the date that the enrollment was submitted to the VTN/Enroller.





> eiEnroll Resource Not in WD25
> -----------------------------
>
>                 Key: ENERGYINTEROP-474
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-474
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: schema
>    Affects Versions: wd25
>         Environment: Bartell
>            Reporter: Bruce Bartell
>            Assignee: William Cox
>             Fix For: wd29
>
>
> The enrollment services are not in wd25 in spec or schema payloads.
> Is this going  to be in CD02? or later?
> I am assuming that this is where the resoruce "capabilities and constraints" will be defined.
> Capabilities as what can be shed/generate over time (ramps) and contraints as min/max per # items that were already defined for resoruces.

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