W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > August 2005

2002/ws/desc/wsdl20 wsdl20.xml,1.328,1.329

From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 23 Aug 2005 10:40:58 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <20050823104058.33DE14EF8A@homer.w3.org>

Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv8165

Modified Files:
	wsdl20.xml 
Log Message:
Mark-up typo: one Description component surrounded by <el> instead of <comp>, and another one not marked


Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.328
retrieving revision 1.329
diff -C2 -d -r1.328 -r1.329
*** wsdl20.xml	22 Aug 2005 21:24:26 -0000	1.328
--- wsdl20.xml	23 Aug 2005 10:40:55 -0000	1.329
***************
*** 9828,9832 ****
  a target namespace with the including description. Components in
  the transitive closure of the included WSDL 2.0 documents
! become part of the <el>Description</el> component of the including WSDL 2.0
  document. The included components can be referenced by QName. Note
  that because all WSDL 2.0 descriptions have a target namespace,
--- 9828,9832 ----
  a target namespace with the including description. Components in
  the transitive closure of the included WSDL 2.0 documents
! become part of the <comp>Description</comp> component of the including WSDL 2.0
  document. The included components can be referenced by QName. Note
  that because all WSDL 2.0 descriptions have a target namespace,
***************
*** 9973,9977 ****
  dereferenceable then no information about the imported namespace is
  provided by that <el>import</el> &EII;. It is possible that such lack
! of information can cause QNames in other parts of a WSDL 2.0 Description
  component to become broken references (see <specref
  ref="qnameres"/>). Such broken references are not errors of the
--- 9973,9977 ----
  dereferenceable then no information about the imported namespace is
  provided by that <el>import</el> &EII;. It is possible that such lack
! of information can cause QNames in other parts of a WSDL 2.0 <comp>Description</comp>
  component to become broken references (see <specref
  ref="qnameres"/>). Such broken references are not errors of the
Received on Tuesday, 23 August 2005 10:41:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:31:50 UTC