Re: [provision] Latest drafts of the schemas...

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

Thanks, Jeff and Gerry.  This looks *great* expressed in wsdl and xsd.  
(Of course, I wouldn't be me if I didn't have questions and comments.  
At least you'll know that I read it. :-))

General.
I notice we don't have relationships.  Do we have conceptual issues (or 
just resource issues)?

draft_pstc_spmlv4_core_5.xsd.

- ResultCode.  Each resultCode is for an individual request.  
BatchResponseType contains a sequence of these, one for each 
batchableRequest in the BatchRequestType.  Am I reading this correctly?

- IdentifierType.  Why is IdentifierType an extension of 
ExtensibleType?  Is the idea that this *could* be a string-format "ID", 
but could equally well be *anything*?  If so, why does this need to be 
so wide-open?

- PSOIdentifierType.   (Same question as IdentifierType regarding 
ExtensibleType.  Also) I notice the absence of "name".  Is the "id" 
assumed to be globally unique and immutable (i.e., a guid)?

- PSOType.  I think I understand why a PSO would have an "id" and 
"parameters", but why would a PSO have a *sequence* of {0-1 
PSOIdentifierType, followed by 0-1 PSOParametersType}?  Especially since 
each of those id values is an instance of PSOIdentifierType, wihch 
already contains a sequence of {0-1 id, followed by 0-1 target}?  This 
probably deserves annotation.

- ModifyResponseType.  Extends SpmlResponseType, but adds nothing.  Is 
this a placeholder to add something we may need?   (Same for 
DeleteResponseType, etc.)

- SupportedCapabilityType.   Does "appliesTo" specify a PSOType from the 
schema?  If so, this probably deserves annotation.  Also, why specify 
maxOccurs="1" on the *any*?  Isn't this the default value?

- ListTargetsRequestType.  Extends SpmlRequestType, but adds only an 
empty sequence.  Is this a placeholder?  Is there some other reason we 
need to *extend* SpmlRequestType?  Why do we need the sequence?  This 
probably deserves annotation.

- CancelResultsType.  For consistency, "nosuchRequest" should probably 
be "noSuchRequest".

- StatusReturnsType.  Do we need the space character at the end of 
"status "?

- CancelRequestType.  Extends SpmlRequestType but adds nothing.  Is this 
a placeholder?  Is there some other reason we need to *extend* 
SpmlRequestType?

- StatusRequestType.  Why does it mean for the request to specify 
"statusReturns='status'"?  Is this requesting a string-form status 
message?  What does it mean for the request to default to 
"statusReturns='result'"?  Does this request a(n enumerated) 
ResultCode?  This probably deserves annotation.

- StatusResponseType.  Why are "complexType", "complextContent", 
"extension" and "sequence" all prefixed with "xsd:" and in *only* this 
type declaration?  Also, why does the status response contain a 
*sequence* of currentResponse?  Does this sequence contain one element 
for each target?  Does this sequence contain one element for each 
element in a batch request?  This probably deserves annotation.

draft_pstc_spmlv2_core_5.wsdl.

draft_pstc_spmlv2_password_5.xsd.

- SetPasswordRequestType.  Wouldn't the element named "pso" be better 
named "identifier" or "psoIdentifier" or "psoId"?  In the the core 
AddResponseType, an element named "pso" was an actual object--an 
instance of PSOType.  Here the element is an instance of PSOIdentifierType.
(Same question/comment for ExpirePasswordRequest, ResetPasswordRequest 
and ValidatePasswordRequest.)

- ValidatePasswordRequest.  Typo in "documentation":  "reset a password" 
should be "validate a password" or, better yet, something as explicit as 
"test a value against password policy".

draft_pstc-spmlv2_5.wsdl.  Should be 
"draft_pstc_spmlv2_password_5.wsdl", right?

draft_pstc_spmlv2_search_5.xsd.

- SearchQueryType.  Extends ExtensibleType, but adds nothing.  Is this a 
placeholder for something we may want to add, or is this the only way to 
compose an ExtensibleType?  Also, if we're not going to add anything, 
can't we just use "/>" rather than "</extension>"?

- IterateRequestType.  I notice we don't have an "IterateResponseType".  
Do we need one?  Or is the response to an IterateRequestType an instance 
of SearchResponseType?  It looks like IterateRequestType is separate 
request type (rather than a special case of SearchRequestType).   This 
probably deserves annotation.

draft_pstc_spmlv2_search_5.wsdl.  Do we need an "IterateRequestMsg" or 
"IteratePortType"?  If not, how does one process an iterator?  Does one 
use the SearchRequestMsg and SearchPortType?

draft_pstc_spmlv2_state_5.xsd. 

- SuspendRequestType.  Wouldn't the element named "pso" be better named 
"identifier" or "psoIdentifier" or "psoId"?  In the the core 
AddResponseType, an element named "pso" was an actual object--an 
instance of PSOType.  Here the element is an instance of PSOIdentifierType.
(Same question/comment for ResumeRequestType and ActiveRequestType.)

- SuspendRequestType (again).  Perhaps the documentation could be 
enhanced to mention that the specified PSO is presumably active.  If the 
'suspend' operation is successful, the specified PSO will become inactive.

- ResumeRequestType.  Perhaps the documentation could be enhanced to 
mention that the specified PSO is presumably suspended (i.e., 
inactive).  If the 'resume' operation is successful, the specified PSO 
will become active.

- ResumeResponseType.  Typo in "documentation": change "Set Password" to 
"Resume".

draft_pstc_spmlv2_5.wsdl.  Should be "draft_pstc_spmlv2_state_5.wsdl", 
right?

Gary

Jeff Bohren wrote:

> Attached is version 5 of the SPML 2.0 schemas. This draft includes 
> Gerry's suggestions for the modify and search request. It also 
> includes an iterator for search requests.