[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: SPML Issues list updates
Further to my action item from the last meeting, I would like to ask that the issues list be updated to reflect these problems: New Issue - SPML should support the transport of XML data Description: There is no satisfactory mechanism to transport XML documents within an SPML request. The SPML should work with Web Services and other XML-based targets which will use XML documents to communicate parameters. New Issue - SPML should allow searches across arbitrarily large data sets Description: The current requirement for all search results to be communicated in a single response message places potentially huge burdens on both clients and servers. The SPML must allow the client to iterate through result sets. This is a critical scalability issue. New Issue - Use of synchronous or asynchronous mode should be dictated by the server Description: The SPML allows the client to specify whether a request should be executed in synchronous or asynchronous mode. This can result in unacceptable blocking times for clients and cause problems for synchronous operations that span very long periods of time due to target constraints or workflow/approval processes. The server is in a position to determine the optimal execution mode for a given target and request and should therefore control the execution mode. Amend issue 1.1.2 - Attribute Definitions Should be in XSD This issue should be renamed to "SPML should support the use of XML Schema". Description: Since targets are likely to make extensive use of XML Schema, and because it is very likely that data items required by targets will be specified in XML Schema, the SPML should support the use of XML Schema and other standard XML-based schema languages in preference to the current limited SPML-specific schema language. Amend issue 1.1.5 - There Should be a Standard WSDL Definition This issue should be renamed to "The SPML interface should be specified in a WSDL definition". Description: The definitive description of the interface to a PSP and PST should be a WSDL document. This is more in keeping with Web Services and promotes the use of the SPML with other standards such as UDDI, BPEL etc. While we have discussed these issues on the list, they have not as yet been captured in the issues document. Gerry
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]