- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 04 May 2006 04:19:47 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv13987/wsdl20
Modified Files:
wsdl20.xml
Log Message:
Made editorial improvements to fragment identifier section A.2. Added bibref to Namespace Binding Context in XPTR.
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.397
retrieving revision 1.398
diff -C2 -d -r1.397 -r1.398
*** wsdl20.xml 18 Apr 2006 18:14:19 -0000 1.397
--- wsdl20.xml 4 May 2006 04:19:44 -0000 1.398
***************
*** 11831,11834 ****
--- 11831,11835 ----
<p>
A WSDL 2.0 fragment identifier consists of zero or more <code>xmlns</code> pointer parts
+ (see <emph>3.4 Namespace Binding Context</emph> in <bibref ref="XPTR"/>)
followed by a WSDL 2.0 pointer part as defined below.
The pointer parts have a scheme name that corresponds to one
***************
*** 11839,11843 ****
The names in the path are of type either QName, NCName,
IRI, URI, or Pointer Part depending on the context.
! The scheme data for extension components is defined by the
corresponding extension specification.
</p>
--- 11840,11844 ----
The names in the path are of type either QName, NCName,
IRI, URI, or Pointer Part depending on the context.
! The scheme data for WSDL 2.0 extension components is defined by the
corresponding extension specification.
</p>
***************
*** 14316,14320 ****
</tr>
! <tr>
<td>20060418</td>
<td>AGR</td>
--- 14317,14327 ----
</tr>
! <tr>
! <td>20060503</td>
! <td>AGR</td>
! <td>Made editorial improvements to fragment identifier section A.2.</td>
! </tr>
!
! <tr>
<td>20060418</td>
<td>AGR</td>
Received on Thursday, 4 May 2006 04:20:57 UTC