a version for recommended change to GetResource,GetIdentity

[Aurelien Stebe]

Hi Ray,

This is definitely an improvement. As I told you before, I was unsure 
about having two output formats for Search methods, but I can see now 
that it makes the interface much clearer.

I think there is still a paragraph missing about the @xsi:type query. 
What is the final decision ?
@xsi:type='SimpleImageAccess'    or    @xsi:type='sia:SimpleImageAccess'
    or    @xsi:type='%:SimpleImageAccess'    or    @xsi:type like 
'%:SimpleImageAccess'.
I prefer the first two solutions, but I can see it being a problem for 
XMLDB implementations.

To react to Paul's message, I would prefer VOResources to stay inside 
the WSDL, as this should be the only place it is needed and it makes one 
less namespace as Ray pointed out. Where do you use VOResources schema 
to validate documents Paul ? The current set of recommended or 
"standard" schema extensions is stated in the RI, in section 3.1.3

Also, I noticed a few typos or errors, especially in the schemas 
snippets. The attribute "to" should be replaced by "max", some 
attributes should be made "required", the OAI is referenced as OAI GET, 
it should be GET and POST.

Cheers,
Aurelien

KevinBenson wrote:
> Yes it looks very good, I placed it on the RegistryInterface page 
> http://www.ivoa.net/twiki/bin/view/IVOA/RegistryInterface    The wsdl 
> was not quite right, but corrected it (I think); it should now work 
> with WSDL2Java. Located in schema/registry/RegistrySearch/v1.0 for the 
> wsdl.  The zip file has some older unused schema's as well and 
> probably not the most recent 1.0 vr:Resource schema's but will try to 
> get the latest version tomorrow.
>
> As far as the document goes I like your changes especially the WSDL 
> Notes inline in the document.  There might still be a couple of 
> concerns with KeywordSearch that I will have a think about and post a 
> separate e-mail later on that subject or follow up on Paul's e-mail.
>
> cheers,
> Kevin
>