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-551) Use of IDs and referenced artifacts


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

William Cox updated ENERGYINTEROP-551:
--------------------------------------

    Resolution: 
Consider for all interactions.

In EiQuote service add a paramter to EiRequestQuotePayloadType which is quoteID [0..*] for response.

Change documentation for EiRequestQuote to indicate that if one or more quoteIDs are requested that the response is the quotes with respect to the counterparty with those IDs.

In EiTransaction: Created should have 0..* transactionIDs, not emixBases. And Request should also have 0..* transactionIDs. Document that if there are zero transaction IDs all transactions related to the listed counterParties are returned; if there are 1..* transactionIDs, then all the emixBase transactions will be returned. 

transactionName should be considered carefully in a subtask--it may be a carryover from when marketContexts were called transactions. See ENERGYINTEROP-

Conformance: There must be at least one of {counterParty, transactionID, transactionName}  in the Request Transaction Payload sent. Or could return an error.

  was:
Consider for all interactions.

In EiQuote service add a paramter to EiRequestQuotePayloadType which is quoteID [0..*] for response.

Change documentation for EiRequestQuote to indicate that if one or more quoteIDs are requested that the response is the quotes with respect to the counterparty with those IDs.

In EiTransaction: Created should have 0..* transactionIDs, not emixBases. And Request should also have 0..* transactionIDs. Document that if there are zero transaction IDs all transactions related to the listed counterParties are returned; if there are 1..* transactionIDs, then all the emixBase transactions will be returned.

Conformance: There must be at least one of {counterParty, transactionID, transactionName}  in the Request Transaction Payload sent. Or could return an error.


> Use of IDs and referenced artifacts
> -----------------------------------
>
>                 Key: ENERGYINTEROP-551
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-551
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Sub-task
>          Components: model, schema, spec
>    Affects Versions: wd28
>         Environment: William Cox
>            Reporter: William Cox
>            Assignee: Toby Considine
>
> The use of IDs and of the referenced objects/artifacts is not entirely consistent.
> For example, EiCreatQuote returns a QuoteIDType as well as 0..* emixBases. QuoteID is used later in CancelQuotePayloadType.
> Presumably the quoteID is the uid in the returned emixBase(s) - but there should be 0..* not 0..1 of them. (see  e.g. ENERGYINTEROP-494 ).
> Unspoken is how you get the referenced artifact given the ID.  Operations  have been added in wd29-WIP(later) to get an EiMarketContext given an emix:MarketContext as a key.

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