[OASIS Issue Tracker] (ENERGYINTEROP-729) Tender Payloads

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

    [ https://issues.oasis-open.org/browse/ENERGYINTEROP-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=80729#comment-80729 ] 

William Cox edited comment on ENERGYINTEROP-729 at 2/21/22 11:42 PM:
---------------------------------------------------------------------

Include the missing Attribute table for EiCreatedTenderPayload, EiCancel/CanceledTenderPayload, and EiDistributeTenderPayload and update the UML. PENDING.

The resourceDesignator coordinates what the tender requests (in EiCreateTenderPayload) and what the Market or MarketPlace supports as a check that the tender went where it needs to be, as an opportunity for a consistency check. While the Tender attributes MIGHT allow inference of the resource, common practice is to explicitly state a designator. Moreover, tenders may be sent to multiple markets, which implies resourceDesignators are consistent across multiple systems or are mappable. Include clarifying text.

The descriptive tables for EiCreatedTender and EiCancel/CanceledTender are missing. If the tender is forwarded, the market or other intermediate Actors may rewrite the CounterPartyId, so the final one needs to be returned to the Actor that sent the EiCreatedTenderPayload object.


was (Author: williamcox):
Include the missing Attribute table for EiCreatedTenderPayload, EiCancel/CanceledTenderPayload, and EiDistributeTenderPayload and update the UML.

The resourceDesignator coordinates what the tender requests (in EiCreateTenderPayload) and what the Market or MarketPlace supports as a check that the tender went where it needs to be, as an opportunity for a consistency check. While the Tender attributes MIGHT allow inference of the resource, common practice is to explicitly state a designator. Moreover, tenders may be sent to multiple markets, which implies resourceDesignators are consistent across multiple systems or are mappable.

The descriptive tables for EiCreatedTender and EiCancel/CanceledTender are missing. If the tender is forwarded, the market or other intermediate Actors may rewrite the CounterPartyId, so the final one needs to be returned to the Actor that sent the EiCreatedTenderPayload object.

> Tender Payloads
> ---------------
>
>                 Key: ENERGYINTEROP-729
>                 URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-729
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: cts
>    Affects Versions: CTSPR01
>         Environment: Horia Pop; Lateral Inc https://lists.oasis-open.org/archives/energyinterop-comment/202112/msg00001.html
>            Reporter: Toby Considine
>            Assignee: William Cox
>            Priority: Major
>              Labels: FACET, RES-PROD-INSTR
>
> *Tender Facet à Payloads Definition*
> Why is a resourceDesignator required when theÃtender already infers it? Tender implies an instrument. Instrument implies product. Product implies a market. Market implies a resource. If the intent is to identify the market, why not specify the product or market directly?
> Why is there a CounterPartyID in the responses for EICreatedTender and EiCanceledTender payload?
> _[Lines 572]_



--
This message was sent by Atlassian Jira
(v8.3.3#803004)