RE: new snapshots

For MEX, since mex:Metadata contains a mex:MetadataSection element plus an 
xs:any (per the xsd), instead of just repeating all of that would people 
be ok with just:

[Action]
  http://www.w3.org/2009/02/ws-mex/GetMetadataResponse
[Body]
 
 <mex:GetMetadataResponse>
   <mex:Metadata ...> ... </mex:Metadata>
   xs:any*
 </mex:GetMetadataResponse>

and this way the "..." under the mex:Metadata can just imply "other 
stuff".   Thoughts?

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.



Ram Jeyaraman <Ram.Jeyaraman@microsoft.com> 
Sent by: public-ws-resource-access-request@w3.org
08/20/2009 04:11 PM

To
Yves Lafon <ylafon@w3.org>, "public-ws-resource-access@w3.org" 
<public-ws-resource-access@w3.org>
cc

Subject
RE: new snapshots






My review comments on MEX and WS-ResourceTransfer. This completes my 
review. Thanks.
 
MEX
 
Issue http://www.w3.org/Bugs/Public/show_bug.cgi?id=6500 resolution states 
the following part:
 
[action]
  http://schemas.xmlsoap.org/ws/2004/09/mex/GetMetadata/Response
[Body]
  <mex:GetMetadataResponse ..>
      <mex:Metadata ?>
      ?
      </mex:Metadata>
      xs:any *
  </mex:GetMetadataResponse>
 
The latest draft of the MEX specification states
 
[Action]
  http://www.w3.org/2009/02/ws-mex/GetMetadataResponse
[Body]
 
 <mex:GetMetadataResponse>
   <mex:Metadata ...>
     xs:any*
   </mex:Metadata>
 
   xs:any*
 
</mex:GetMetadataResponse>
 
I believe the xs:any inside the <mex:Metadata> is extraneous.
 
WS-ResourceTransfer
 
Looks good.
 
From: public-ws-resource-access-request@w3.org 
[mailto:public-ws-resource-access-request@w3.org] On Behalf Of Ram 
Jeyaraman
Sent: Tuesday, August 18, 2009 12:09 PM
To: Yves Lafon; public-ws-resource-access@w3.org
Subject: RE: new snapshots
 
Here are my review comments on the latest drafts of WS-Transfer, 
WS-Enumeration, and WS-Eventing. I am yet to review MEX and RT. Thanks.
 
WS-Transfer
 
Should the specification use WS-Fragment or WS-Fragments?
 
The change is highlighted in red.
 
[Body] /wst:Delete@Dialect="http://www.w3.org/2009/02/ws-frag" 
The WS-Fragment [WS-Fragments] specification defines this dialect URI. Use 
of this URI indicates that the contents of the Get element MUST be 
processed as specified by the WS-Fragment [WS-Fragments] specification.
The above  comment applies for the descriptions of the following 
attributes as well.
 
[Body] /wst:Put@Dialect=http://www.w3.org/2009/02/ws-frag
[Body] /wst:Create@Dialect=http://www.w3.org/2009/02/ws-frag
 
WS-Enumeration
 
The phrase ?returning the EnumerateResponse. message.? has a extra full 
stop after EnumerateResponse.
 
WS-Transfer
 
Looks good.
 
-----Original Message-----
From: public-ws-resource-access-request@w3.org 
[mailto:public-ws-resource-access-request@w3.org] On Behalf Of Yves Lafon
Sent: Friday, July 24, 2009 7:02 AM
To: public-ws-resource-access@w3.org
Subject: new snapshots
 
See
http://www.w3.org/2002/ws/ra/snapshots/20090724/wsenum.html
http://www.w3.org/2002/ws/ra/snapshots/20090724/wseventing.html
http://www.w3.org/2002/ws/ra/snapshots/20090724/wsmex.html
http://www.w3.org/2002/ws/ra/snapshots/20090724/wsrt.html
http://www.w3.org/2002/ws/ra/snapshots/20090724/wst.html
 
and the diffs from the june snapshots:
http://www.w3.org/2002/ws/ra/snapshots/20090724/wsenum-diff.html
http://www.w3.org/2002/ws/ra/snapshots/20090724/wseventing-diff.html
http://www.w3.org/2002/ws/ra/snapshots/20090724/wsmex-diff.html
http://www.w3.org/2002/ws/ra/snapshots/20090724/wsrt-diff.html
http://www.w3.org/2002/ws/ra/snapshots/20090724/wst.html
 
--
Baroula que barouleras, au tiéu toujou t'entourneras.
 
         ~~Yves