[OASIS Issue Tracker] Updated: (ENERGYINTEROP-577) Improvements to Transactive Services Payloads

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

William Cox updated ENERGYINTEROP-577:
--------------------------------------

    Environment: Ed Cazalet - see also ENERGYINTEROP-580  (was: Ed Cazalet)
    Description: 
Comments in { }

With respect to the Transactive Services Payloads
 
1.       EiCreateTender needs a tendereeParty ID to identify the
counterparty to the Tenderee or each Tender.
{ Accepted
}
2.      Canceled Tender should return a list of canceledTenderIDs
{ in wd32 cancel tender takes one party ID and an optional counterPartyID., and 1..* TenderIDs.

The responses (ArrayOfResponses) responds with an ID (of which tenderID is substitutable) and a response for each. So there's a value that can be used as a Tender ID for each tenderID submitted.

So this is in wd32., but is NOT MANDATORY if the cancel is successful. The pattern is to return those that have failed (required) and those that succeeded (optional).

ACTION improve documentation on this point.
}

3.      Why does EiRequestTender us counterPartyID rather than
tendereeParityID?   As you know I still prefer Party and CounterParty for
Tenderor and Tenderee.
{ Accepted in ENERGYINTEROP-580
}

4.      Need EIDistributeTender service
{ Included in wd32
}

5.      EiCreateTransaction needs multiple transactionIDs if accepting
multiple Tenders.
{ Rejected. For simplicity in 1.0, a single tenderID is used. Note that the mulitplicity can be at any level inside the eiTransaction, which contains an EMIX Base. Allowing multiplicity inside and outside the emix base is too complex for 1.0, and the work would delay 1.0.

I'm splitting this as a deferred post 1.0 in a new issue (FILL IN THE NUMBER) ENERGYINTEROP-
}

6.      Why does ReplyTenderPayload carry emixBase when it does not appear
in any other payload?
{ Thanks for catching this earlier. Corrected by wd32.
}

7.      EiRequestTransaction also needs multiple transactionIDs.
{ Accepted. has 0..* transactionIDs.
}
 


  was:
With respect to the Transactive Services Payloads
 
1.       EiCreateTender needs a tendereeParty ID to identify the
counterparty to the Tenderee or each Tender.
2.      Canceled Tender should return a list of canceledTenderIDs
3.      Why does EiRequestTender us counterPartyID rather than
tendereeParityID?   As you know I still prefer Party and CounterParty for
Tenderor and Tenderee.
4.      Need EIDistributeTender service
5.      EuCreateTransaction needs multiple transactionIDs if accepting
multiple Tenders.
6.      Why does ReplyTenderPayload carry emixBase when it does not appear
in any other payload?
7.      EiRequestTransaction also needs multiple transactionIDs.
 


     Resolution: 
Per marked up Description.

In addition, document the behavior in #2 with respect to receiving the tenderIDs that are canceled or not. This belongs in the EiResponse section 6.8 wd32

> Improvements to Transactive Services Payloads
> ---------------------------------------------
>
>                 Key: ENERGYINTEROP-577
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-577
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>    Affects Versions: wd29
>         Environment: Ed Cazalet - see also ENERGYINTEROP-580
>            Reporter: Toby Considine
>            Assignee: William Cox
>             Fix For: wd30
>
>
> Comments in { }
> With respect to the Transactive Services Payloads
>  
> 1.       EiCreateTender needs a tendereeParty ID to identify the
> counterparty to the Tenderee or each Tender.
> { Accepted
> }
> 2.      Canceled Tender should return a list of canceledTenderIDs
> { in wd32 cancel tender takes one party ID and an optional counterPartyID., and 1..* TenderIDs.
> The responses (ArrayOfResponses) responds with an ID (of which tenderID is substitutable) and a response for each. So there's a value that can be used as a Tender ID for each tenderID submitted.
> So this is in wd32., but is NOT MANDATORY if the cancel is successful. The pattern is to return those that have failed (required) and those that succeeded (optional).
> ACTION improve documentation on this point.
> }
> 3.      Why does EiRequestTender us counterPartyID rather than
> tendereeParityID?   As you know I still prefer Party and CounterParty for
> Tenderor and Tenderee.
> { Accepted in ENERGYINTEROP-580
> }
> 4.      Need EIDistributeTender service
> { Included in wd32
> }
> 5.      EiCreateTransaction needs multiple transactionIDs if accepting
> multiple Tenders.
> { Rejected. For simplicity in 1.0, a single tenderID is used. Note that the mulitplicity can be at any level inside the eiTransaction, which contains an EMIX Base. Allowing multiplicity inside and outside the emix base is too complex for 1.0, and the work would delay 1.0.
> I'm splitting this as a deferred post 1.0 in a new issue (FILL IN THE NUMBER) ENERGYINTEROP-
> }
> 6.      Why does ReplyTenderPayload carry emixBase when it does not appear
> in any other payload?
> { Thanks for catching this earlier. Corrected by wd32.
> }
> 7.      EiRequestTransaction also needs multiple transactionIDs.
> { Accepted. has 0..* transactionIDs.
> }
>  

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