Thanks for your comment. The WS Description Working Group tracked this issue as a CR063 [1]. The Working Group agreed that reading the sentence literally was misleading, but opted for a simple fix, prepending "Conceptually" to the sentence. This has been implemented in the latest editor's draft [2]. Unless you let us know otherwise by the end of October, we will assume you agree with the resolution of this issue. [1] http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR063 [2] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?content- type=text/html;%20charset=utf-8#inlining-xsd Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com > -----Original Message----- > From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On > Behalf Of Jeremy Hughes > Sent: Wednesday, June 07, 2006 2:44 PM > To: www-ws-desc@w3.org > Subject: Prefix declarations in inlined schema > > > Hi, section 3.1.2 of part 1 [1] says about inlining XML schema: > > "It may be viewed as simply cutting and pasting an existing schema > document to a location inside the types element information item." > > Doing this could mean a namespace declaration, declared in the > enclosing <description> is redeclared in the <schema> element. Of > course, this won't be a problem - I'm more interested in the case > where the inlined schema relies on the enclosing <description>'s > namespace declarations. Meaning the <schema> uses prefixes only > declared in the enclosing <description> element. So ... > > Is it necessary to respecify namespace declarations already specified > in the enclosing WSDL or do the default scoping rules apply? > > [1] > http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?conten > t-type=text/html;%20charset=utf-8#inlining-xsd > > Thanks, > JeremyReceived on Monday, 16 October 2006 17:44:18 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:32 GMT