[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [provision] First Draft of the Request/Response schema for SPML...
|
Jeff
Some questions and thoughts for discussion on the list or during this weeks call:
- Why is the BatchRequets BatchRequests sequence a minOccurs=0? This implies that I can construct a Batch with no operations in it. Is this deliberate? - I believe we are missing an optional "ordering" attribute on the BatchRequest for parallel executions - CamelCase on BatchCancelResponse cancelResults - On BatchCancelRequest, what is the difference between response|status in returnType? Same question for for BatchStatus statusResults? - Is there no way to make the requestID mandatory if processing is async? We have this optional for sync requests to allow for canceling hanging request… - We discussed having other “operational parameters”. Maybe we should start a separate thread to define some of these and see what comes out…. · What the operation costs? · Who approved it? · What other data got changed?? · When to execute this?
-------------------------------------------------------- Darran Rolls http://www.waveset.com Waveset Technologies Inc drolls@waveset.com (512) 657 8360 --------------------------------------------------------
-----Original Message-----
Attached is the first draft for the Request/Response schema for SPML. This requires the SPML Core schema and the DSMLv2 schema.
Jeff Bohren Product Architect OpenNetwork Technologies, Inc
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC