Re: [provision] Draft 8 of the SPML XSDs...

[Gary P Cole <Gary.P.Cole@Sun.COM>]

1. Need to break out async as a separate capability.
The async capability should contain the cancel and status operations
and any type that is specific to these operations.

2. Iterator should be *optional* in SearchResponseType.
In today's working group call, you suggested that the XSD should allow
the provider to omit content for every response in case of error.
(I think this means that no response should require a sub-element.)

3. <pso> should be minOccurs="0" and maxOccurs="unbounded" in 
SearchResponseType.
This allows the provider to return any number of objects.

4. <iterator> should be minOccurs="0" and maxOccurs="1" in 
SearchResponseType.
If the provider returns all matching objects (or if there is an error),
then there is no need for a provider to return an iterator.

5. <modification> should be minOccurs="1" and maxOccurs="unbounded" in 
ModifyRequestType.  This allows a requestor to specify multiple 
modifications for the same object.

6. The "component" element should be of type SelectionType (rather than 
IdentifierType) in ModifyRequestType.  This allows a requestor to use an 
XPATH expression to specify the component of an object that the provider 
is to modify.

7. SelectionType should be enhanced to allow a requestor to specify any 
number of mappings from a prefix (that may be used in the expression 
that is the value of the "path" attribute) to a namespace URI.

gpc

Jeff Bohren wrote:

> Draft 8 has batch semantics broken out as a separate capability.
>