Changes between Version 68 and Version 69 of Discovery/DiscoveryWebServiceMEDIN


Ignore:
Timestamp:
02/03/10 17:22:23 (9 years ago)
Author:
sdonegan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Discovery/DiscoveryWebServiceMEDIN

    v68 v69  
    329329    Textual information regarding success / failure / errors.  
    330330  <Documents>:: 
    331     If some documents have been successfully returned, a <documents> element is present and will contain a child <!DocumentFull> element for each document retrieved. In the case where some but not all documents are successfully returned, the <Documents> element will contain populated <!DocumentFull> elements for the successfully-retrieved documents, but <!DocumentFull> elements containing a populated <!DocumentId> but unpopulated <Document> element for those where retrieval failed. If NO documents are successfully returned, however, then the <Status> is set to false and no <Documents> element is included in the doPresentResponse message. 
     331    If some documents have been successfully returned, a <!Documents> element is present and consists of the same structure as the <!Documents> element in the !DoSearchReturn element depending on the values entered in the <!RetrieveCriteria> element in the !DoPresent request. 
    332332 
    333333The <Document> element, if present and populated, contains the retrieved document as an encapsulated string representation of the XML. Depending on the client used to display the payload document, it either appears contained within a <![CDATA[ ... ]]> construct, or as XML with the opening angle brackets "<" escaped as "&lt;". Most XML parsers should successfully parse the string to reconstruct the XML document, but it is returned in this form to avoid namespace issues.