The element contains a signature or timestamp of some sort. This element is returned in a sign response message, and sent in a verify request message. It may contain one of the following child elements:
An XML signature [XMLDSIG].
An XML, RFC 3161 or other timestamp (see section 5.1).
A base64 encoding of some non-XML signature, such as a PGP [RFC 2440] or CMS [RFC 3852] signature. The type of signature is specified by its Type attribute (see section 7.1).
This is used to point to an XML signature in an input (for a verify request) or output (for a sign response) document in which a signature is enveloped.
As described above in 2.4.1
A contains the following attributes:
This identifies the input document as in section 2.4.2 being pointed at (see also ID attribute in section 2.4.1).
a) This identifies the signature element being pointed at.
b) The XPath expression is evaluated from the root node (see section 5.1 of [XPATH]) of the document identified by WhichDocument after the XML data was extracted and parsed if necessary. The context node for the XPath evaluation is the document’s DocumentElement (see section 2.1 Well-Formed XML Documents [XML]).
c) About namespace declarations for the expression necessary for evaluation see section 1 of [XPATH]. Namespace prefixes used in XPath expressions MUST be declared within the element containing the XPath expression. E.g.: . See also the following example below. A piece of a XML signature of a containing a with a XPath filtering element that includes inline namespace prefixes declaration. This piece of text comes from one of the signatures that were generated in the course of the interoperability experimentation. As one can see they are added to the element:
The signature is valid with respect to XML Signature core validation. In addition, the message also contains VerifyManifestResults.
Note: In the case that the core signature validation failed no attempt is made to verify the manifest.
The processing of the request failed due to an error not covered by the existing error codes. Further details should be given in the result message for the user which may be passed on to the relevant administrator.