Hi Kevin and Aurelien,
(I know I've been sending you stuff fast and furious, so I'll understand if you need some time to digest some of this stuff. Sorry!)
As you know, I've suggested we change the WSDL descriptions of GetResource and GetIdentity to use a different output format than Search/KeywordSearch to only allow one Resource record to be returned. Also, as I've alluded to previously, a number of recent incremental changes have introduce a number of inconsistances and a somewhat hodgepodge organization of the spec document. So along with my recommended change to the WSDL, I wanted to take the opportunity to reorganize the spec around the new WSDL.
Here's a summary of what I did to the RegistrySearch interface WSDL: o GetResource and GetIdentity share a common output format called
ResolveResponse that allows exactly one Resource element.
o I got rid of the separate RegistryInterface.xsd file; since this
schema is used only by RegistrySearch, it seems just as easy to
include it directly in the <types> section of the WSDL.
o I defined an extra NotFound fault for GetResource to handle the case
when the input identifier cannot be resolved to a record.
o I added in XQuerySearch to be part of the WSDL, regardless of whether
the registry supports it.
o I added the OperationUnsupported fault to XQuerySearch that
non-supporting registries should throw.
o in the <binding> section, I matched the soapAction and namespace URIs
to the target namespace of the WSDL itself.
Given these changes, I've reorganized section 2 around the theme that we have two kinds of operations in the searching interface: "search" operations that return VOResources and "resolve" operations that return a single Resource; the contents now looks like this...
2 Searching
2.1 Required Search Operations
2.1.1 Output Format
2.1.2 Constraint-based Search Query
2.1.3 Keyword Search Query
2.2.1 Output Format
2.2.2 Identifier Resolution
2.2.3 Identity Query
There isn't anything new in terms of content (other than what I talked about above in the WSDL), but you will see a bunch more detail describing inputs and outputs. Here are some notes:
o The pagination and identifierOnly schemes (old section 2.1) have
been integrated into the descriptions of inputs and outputs.
o The description of VORegistry metadata has been moved to the (as yet
unfinished) section 4.
o I went ahead and changed that "to" attribute to "max".
So if I can't talk you into the WSDL changes ;-) we can revert the spec document back and try to deal with the inconsistancies and organization there.
cheers,
Ray