- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 26 Jan 2006 17:27:41 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/test-suite In directory hutz:/tmp/cvs-serv15554/test-suite Modified Files: assert-yourself.html Log Message: updated assignments of sections to editors Index: assert-yourself.html =================================================================== RCS file: /sources/public/2002/ws/desc/test-suite/assert-yourself.html,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** assert-yourself.html 7 Dec 2005 23:02:10 -0000 1.1 --- assert-yourself.html 26 Jan 2006 17:27:39 -0000 1.2 *************** *** 6,10 **** <h1>Assert Yourself!</h1> <address><a href="mailto:ryman@ca.ib.com">Arthur Ryman, IBM</a></address> ! <address>Updated 2005-12-07</address> <h2>Introduction</h2> --- 6,10 ---- <h1>Assert Yourself!</h1> <address><a href="mailto:ryman@ca.ib.com">Arthur Ryman, IBM</a></address> ! <address>Updated 2006-01-26</address> <h2>Introduction</h2> *************** *** 31,52 **** attributes: <ul> ! <li>id - a required identifier. The identifier consists of a ! descriptive prefix and a four-digit numeric suffix separated by a dash, ! as in <code>Import-0001</code> . The numeric suffix must be globally ! unique across all our specifications. Once this number is assigned, it ! never changes. It may be removed but will never be reused. The ! identifier as a whole must be stable since implementers will refer to ! it.</li> ! ! <li>class - a required classification of the assertion. The valid classes are: document, component, message, and exchange. ! A document assertion is a requirement on WSDL 2.0 documents, e.g. that a document must not import its own namespace. ! A component assertion is a requirement on WSDL 2.0 components, e.g. that an Interface must not extend itself. ! A message assertion is a requirement on concrete Web service messages, e.g. that a SOAP message body satsifies a certain XML schema. ! An exchange assertion is a requirement on Web service message exchanges, e.g. that a fault may replace a message.</li> ! ! <li>required - an optional boolean that indicates if the assertion is a requirment. The default is true. Set this to false for ! SHOULD, SHOULD NOT, etc. (Note: this is currently unsupported. I'll add it later.)</li> </p> </ul> </body> </html> --- 31,421 ---- attributes: <ul> ! <li><code>id</code> - a required identifier. The identifier consists of ! a descriptive prefix and a unique numeric suffix separated by a ! dash, as in <code>Import-0001</code> . The numeric suffix must be ! globally unique across all our specifications. Once this number is ! assigned, it never changes. It may be removed but will never be reused. ! The identifier as a whole must be stable since implementers will refer ! to it.</li> ! ! <li><code>class</code> - a required classification of the assertion. ! The valid classes are: <code>document</code>, <code>component</code>, <code>message</code>, ! and <code>exchange</code>. ! <ul> ! <li>A <code>document</code> assertion is a requirement on WSDL 2.0 ! documents, e.g. that a document must not import its own namespace.</li> ! <li>A <code>component</code> assertion is a requirement on WSDL 2.0 ! components, e.g. that an Interface must not extend itself.</li> ! <li>A <code>message</code> assertion is a requirement on concrete Web ! service messages, e.g. that a SOAP message body satsifies a certain ! XML schema.</li> ! <li>An <code>exchange</code> assertion is a requirement on Web service ! message exchanges, e.g. that a fault may replace a message.</li> ! </ul> ! </li> ! ! <li><code>required</code> - an optional boolean that indicates if the ! assertion is a requirment. The default is true. Set this to false for ! SHOULD, SHOULD NOT, etc. (Note: this is currently unsupported. I'll add ! it later.)</li> </p> </ul> + <h2>Review Assignments</h2> + <table border="1"> + <tr> + <th>Editor</th> + <th>Id Range</th> + <th>Part</th> + <th>Section</th> + </tr> + <tr> + <td>Arthur</td> + <td>1100000</td> + <td>1</td> + <td>1. Introduction</td> + </tr> + <tr> + <td>Arthur</td> + <td>1200000</td> + <td>1</td> + <td>2. Component Model</td> + </tr> + <tr> + <td>Arthur</td> + <td>1201000</td> + <td>1</td> + <td>2.1 Description</td> + </tr> + <tr> + <td>Roberto</td> + <td>1202000</td> + <td>1</td> + <td>2.2 Interface</td> + </tr> + <tr> + <td>Roberto</td> + <td>1203000</td> + <td>1</td> + <td>2.3 Interface Fault</td> + </tr> + <tr> + <td>Roberto</td> + <td>1204000</td> + <td>1</td> + <td>2.4 Interface Operation</td> + </tr> + <tr> + <td>Roberto</td> + <td>1205000</td> + <td>1</td> + <td>2.5 Interface Message Reference</td> + </tr> + <tr> + <td>Roberto</td> + <td>1206000</td> + <td>1</td> + <td>2.6 Interface Fault Reference</td> + </tr> + <tr> + <td>Glen</td> + <td>1207000</td> + <td>1</td> + <td>2.7 Feature</td> + </tr> + <tr> + <td>Glen</td> + <td>1208000</td> + <td>1</td> + <td>2.8 Property</td> + </tr> + <tr> + <td>Jonathan</td> + <td>1209000</td> + <td>1</td> + <td>2.9 Binding</td> + </tr> + <tr> + <td>Jonathan</td> + <td>1210000</td> + <td>1</td> + <td>2.10 Binding Fault</td> + </tr> + <tr> + <td>Jonathan</td> + <td>1211000</td> + <td>1</td> + <td>2.11 Binding Operation</td> + </tr> + <tr> + <td>Jonathan</td> + <td>1212000</td> + <td>1</td> + <td>2.12 Binding Message Reference</td> + </tr> + <tr> + <td>Jonathan</td> + <td>1213000</td> + <td>1</td> + <td>2.13 Binding Fault Reference</td> + </tr> + <tr> + <td>Jean-Jacques</td> + <td>1214000</td> + <td>1</td> + <td>2.14 Service</td> + </tr> + <tr> + <td>Jean-Jacques</td> + <td>1215000</td> + <td>1</td> + <td>2.15 Endpoint</td> + </tr> + <tr> + <td>Jean-Jacques</td> + <td>1216000</td> + <td>1</td> + <td>2.16 XML Schema 1.0 Simple Types Used in the Component Model</td> + </tr> + <tr> + <td>Jean-Jacques</td> + <td>1217000</td> + <td>1</td> + <td>2.17 Equivalence of Components</td> + </tr> + <tr> + <td>Jean-Jacques</td> + <td>1218000</td> + <td>1</td> + <td>2.18 Symbol Spaces</td> + </tr> + <tr> + <td>Jean-Jacques</td> + <td>1219000</td> + <td>1</td> + <td>2.19 QName resolution</td> + </tr> + <tr> + <td>Jean-Jacques</td> + <td>1220000</td> + <td>1</td> + <td>2.20 Comparing URIs and IRIs</td> + </tr> + <tr> + <td>Roberto</td> + <td>1300000</td> + <td>1</td> + <td>3. Types</td> + </tr> + <tr> + <td>Arthur</td> + <td>1400000</td> + <td>1</td> + <td>4. Modularizing WSDL 2.0 descriptions</td> + </tr> + <tr> + <td>Arthur</td> + <td>1500000</td> + <td>1</td> + <td>5. Documentation</td> + </tr> + <tr> + <td>Arthur</td> + <td>1600000</td> + <td>1</td> + <td>6. Language Extensibility</td> + </tr> + <tr> + <td>Arthur</td> + <td>1700000</td> + <td>1</td> + <td>7. Locating WSDL 2.0 Documents</td> + </tr> + <tr> + <td>Arthur</td> + <td>1800000</td> + <td>1</td> + <td>8. Conformance</td> + </tr> + <tr> + <td>Arthur</td> + <td>1900000</td> + <td>1</td> + <td>A. The application/wsdl+xml Media Type</td> + </tr> + <tr> + <td>Amy</td> + <td>2100000</td> + <td>2</td> + <td>1. Introduction</td> + </tr> + <tr> + <td>Amy</td> + <td>2200000</td> + <td>2</td> + <td>2. Predefined Message Exchange Patterns</td> + </tr> + <tr> + <td>Amy</td> + <td>2300000</td> + <td>2</td> + <td>3. Predefined Extensions</td> + </tr> + <tr> + <td>Umit</td> + <td>2400000</td> + <td>2</td> + <td>4. Predefined Operation Styles</td> + </tr> + <tr> + <td>Charlton</td> + <td>2500000</td> + <td>2</td> + <td>5. WSDL SOAP Binding Extension</td> + </tr> + <tr> + <td>Charlton</td> + <td>2501000</td> + <td>2</td> + <td>5.1 XML Syntax Summary (Non-Normative)</td> + </tr> + <tr> + <td>Charlton</td> + <td>2502000</td> + <td>2</td> + <td>5.2 Identifying the use of the SOAP Binding</td> + </tr> + <tr> + <td>Charlton</td> + <td>2503000</td> + <td>2</td> + <td>5.3 SOAP Binding Rules</td> + </tr> + <tr> + <td>Charlton</td> + <td>2504000</td> + <td>2</td> + <td>5.4 Specifying the SOAP Version</td> + </tr> + <tr> + <td>Charlton</td> + <td>2505000</td> + <td>2</td> + <td>5.5 Specifying the SOAP Underlying Protocol</td> + </tr> + <tr> + <td>Charlton</td> + <td>2506000</td> + <td>2</td> + <td>5.6 Binding Faults</td> + </tr> + <tr> + <td>Charlton</td> + <td>2507000</td> + <td>2</td> + <td>5.7 Binding Operations</td> + </tr> + <tr> + <td>Charlton</td> + <td>2508000</td> + <td>2</td> + <td>5.8 Declaring SOAP Modules</td> + </tr> + <tr> + <td>Charlton</td> + <td>2509000</td> + <td>2</td> + <td>5.9 Declaring SOAP Header Blocks</td> + </tr> + <tr> + <td>Charlton</td> + <td>2510000</td> + <td>2</td> + <td>5.10 WSDL SOAP 1.2 Binding</td> + </tr> + <tr> + <td>Charlton</td> + <td>2511000</td> + <td>2</td> + <td>5.11 Conformance</td> + </tr> + <tr> + <td>Hugo</td> + <td>2600000</td> + <td>2</td> + <td>6. WSDL HTTP Binding Extension</td> + </tr> + <tr> + <td>Hugo</td> + <td>2601000</td> + <td>2</td> + <td>6.1 Identifying the use of the HTTP Binding</td> + </tr> + <tr> + <td>Hugo</td> + <td>2602000</td> + <td>2</td> + <td>6.2 HTTP Syntax Summary (Non-Normative)</td> + </tr> + <tr> + <td>Hugo</td> + <td>2603000</td> + <td>2</td> + <td>6.3 HTTP Binding Rules</td> + </tr> + <tr> + <td>Hugo</td> + <td>2604000</td> + <td>2</td> + <td>6.4 Specifying the HTTP Version</td> + </tr> + <tr> + <td>Hugo</td> + <td>2605000</td> + <td>2</td> + <td>6.5 Binding Operations</td> + </tr> + <tr> + <td>Hugo</td> + <td>2606000</td> + <td>2</td> + <td>6.6 Declaring HTTP Headers</td> + </tr> + <tr> + <td>Hugo</td> + <td>2607000</td> + <td>2</td> + <td>6.7 Specifying HTTP Error Code for Faults</td> + </tr> + <tr> + <td>Hugo</td> + <td>2608000</td> + <td>2</td> + <td>6.8 Serialization Format of Instance Data</td> + </tr> + <tr> + <td>Hugo</td> + <td>2609000</td> + <td>2</td> + <td>6.9 Specifying the Transfer Coding</td> + </tr> + <tr> + <td>Hugo</td> + <td>2610000</td> + <td>2</td> + <td>6.10 Specifying the Use of HTTP Cookies</td> + </tr> + <tr> + <td>Hugo</td> + <td>2611000</td> + <td>2</td> + <td>6.11 Specifying HTTP Access Authentication</td> + </tr> + <tr> + <td>Hugo</td> + <td>2612000</td> + <td>2</td> + <td>6.12 Conformance</td> + </tr> + </table> </body> </html>
Received on Thursday, 26 January 2006 17:27:45 UTC