W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > March 2006

2002/ws/desc/wsdl20 wsdl20-adjuncts.xml,1.158,1.159

From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 22 Mar 2006 18:26:03 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <20060322182603.5CB6D4F3FB@homer.w3.org>

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

Modified Files:
	wsdl20-adjuncts.xml 
Log Message:
Updated prevloc
Added assertion intro


Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.158
retrieving revision 1.159
diff -C2 -d -r1.158 -r1.159
*** wsdl20-adjuncts.xml	9 Mar 2006 14:46:35 -0000	1.158
--- wsdl20-adjuncts.xml	22 Mar 2006 18:26:00 -0000	1.159
***************
*** 22,26 ****
  <!ENTITY document.status "Editors' copy $Date$">
  <!ENTITY thisdoc.title "&part2.title;">
! <!ENTITY prevloc "http://www.w3.org/TR/2005/WD-wsdl20-adjuncts-20050803">
  <!-- Do not change the following for the upcoming LC: it contains text
  about the one-way MEP addition -->
--- 22,26 ----
  <!ENTITY document.status "Editors' copy $Date$">
  <!ENTITY thisdoc.title "&part2.title;">
! <!ENTITY prevloc "http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060106">
  <!-- Do not change the following for the upcoming LC: it contains text
  about the one-way MEP addition -->
***************
*** 232,235 ****
--- 232,256 ----
  	pseudo-schemas</xspecref> is the same as the one used in <bibref ref="WSDL-PART1"/>.</p>
        </div2>
+ 
+       <div2 id="assertions">
+ 	<head>Assertions</head>
+ 	<p>
+ 	  Assertions about WSDL 2.0 documents and components that are
+ 	  not enforced by the normative XML schema for WSDL 2.0 are
+ 	  marked by a dagger symbol (&#x2020;) at the end of a
+ 	  sentence. Each assertion has been assigned a unique
+ 	  identifier that consists of a descriptive textual prefix and
+ 	  a unique numeric suffix. The numeric suffixes are assigned
+ 	  sequentially and never reused so there may be gaps in the
+ 	  sequence.  The assertion identifiers MAY be used by
+ 	  implementations of this specification for any purpose,
+ 	  e.g. error reporting.
+ 	</p>
+ 	<p>
+ 	  The assertions and their identifiers are summarized in
+ 	  section <specref ref="assertionsummary" />.
+ 	</p>
+       </div2>
+ 
      </div1>
  
Received on Wednesday, 22 March 2006 18:26:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 22 March 2006 18:26:07 GMT