[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ENERGYINTEROP-493) EiTender issues including spelling
[ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toby Considine updated ENERGYINTEROP-493:
-----------------------------------------
Fix Version/s: wd29
(was: wd28)
> EiTender issues including spelling
> ----------------------------------
>
> Key: ENERGYINTEROP-493
> URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-493
> Project: OASIS Energy Interoperation TC
> Issue Type: Bug
> Affects Versions: wd26
> Reporter: William Cox
> Assignee: William Cox
> Fix For: wd29
>
>
> Cancellation or cancel? 931
> 936 EiSend - should be EiRequestTender. Diagram has problems. Add EiDistributeTender. Withdraw should be Cancel/Canceled.
> Part of diagram duplicated
> Distribute Tender - to geo area
> UID for that tender?
> Send back what I received.
> EC: if a UID for a tender could receive -- suggest change to returning UuidTypes for the response?
> Retuirn all tenders that I've created - response for "not all" but success?
> Should I have partial success if only a; few can be done. Creation of a tender may or may not require a response, but just an ack that I received the payloads.
> T: two cases - comm are good enough, don't care if you accepted one - each of the five rejected should have an error message? Or "I got your message and may or may not do anything with it"
> Independent - respond with a list of UIDs of created - but sometimes you don't want (all of N California). If don't want a response, use DistributeTender (TB)
> EC: On create - ack of recei9pt of the message - list of IDs of created things. Make it optional - market rules? T: should define all three patterns. one is (a) Tell me about rans you've created; (b) these are the ones I've successfully created in my memory (c) I don't know what's going on - tello me everything about what you accept/reject (create)
> B: Apply same "boolean" as EiEvent TestEvent to this.
> EiRequestTender should be from either pParty - either. party. NOTE only those to which I was a Party.
> Is it only tenders made? Only ones that are ative? limit set of tenders that come back? T: Date? Value? Date range?
> ADD string - "query: string [0..1]" - but default to return all active (not withdrawn, have not expired) for the relevant party pair .
> Cancel - a list of UIDs (here TenderIDType) - as shown.
> Cancel and Canceled - - the entire tender. If it was created with DistributeTender or CreateTender I already have the ID and the geolocation in my hand, so I don't need to have the full tender.
> Same pattern for Canceled, 0..* tenderIDs.
> partyRole - roles like ISO, LSE, MA, ... that list of things. ... at a high level in the architecture.
> Event - does the UID change? UID and revision have to send back more than the UID.
--
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]