issues in the examples

[martin.raepple@sap.com]

As mentioned in the TC call yesterday, here is a list of a few (minor) issues regarding the examples I found in the latest draft (2005/03/26):
1. Page 28, line 861 (example for listTargetsRespone): Both <target> elements contain an element <identifier>, which should be <targetID> according to the ListTargetsResponstType schema.
2. Page 46, line 1294 (example for modifyRequest): Even though the syntax of the XPath string in <component> is correct, it doesn't match to the Person schema returned by the modifyResponse on page 47, line 1300 ff. In the response, <email> appears as an element of <Person>, so the correct XPath would be /Person/email to select email
3. Page 53, line 1464 (example for cancelResponse): Attribute asyncRequestID is missing, since it is required according to the schema. The correct response would be <cancelResponse asyncRequest="8488" status="success"/>
4. Page 57, line 1582 ff: According to the text, <statusResponse> should contain the element <currentResult>, not <addResponse> as shown in the example at line 1584 ff.
5. Page 57, line 1593 ff: According to the text and the closing tag </currentResult> in the example below, the subelement of <statusResponse> should be <currentResult> and not <addResponse>
6. Page 58, line 1606 ff: same as #5 (replace <addResponse> with <currentResult>)
7. Page 88, line 2445 (example for searchRequest): same as #2: email treated as an attribute in XPath statement, but actually an element in searchResponse
8. Page 93, line 2601 (example for searchRequest): same as #7

Martin