Element InputDocuments Element InputDocuments The element is used to send documents to a DSS server, whether for InputDocuments signing or verifying. An input document can be any piece of data that can be used as input to a signature or timestamp calculation. An input document can even be a signature or timestamp (for example, a pre-existing signature can be counter-signed or timestamped). InputDocuments element MUST contain zero or more of the following elements respectively: Document, TransformedData, and DocumentHash in any [DSS-3.5-1] ∆ Element Document The element with cardinality [0, ∞] contains documents respectively and as specified Document in section 3.5.4 . Element TransformedData The element with cardinality [0, ∞] contains the binary output of a chain of TransformedData transforms applied by a client as specified in section 3.5.5 . Element DocumentHash The element with cardinality [0, ∞] contains the hash values as specified in DocumentHash section 3.5.6 . Format specific implementations including mappings to the generic terms are defined in 9.5 and 10.5 respectively.
Element InputDocuments Element InputDocuments The InputDocuments element is used to send documents to a DSS server, whether for signing or verifying. An input document can be any piece of data that can be used as input to a signature or timestamp calculation. An input document can even be a signature or timestamp (for example, a pre-existing signature can be counter-signed or timestamped). InputDocuments element MUST contain zero or more of the following elements respectively: Document, TransformedData, and DocumentHash in any ∆ [DSS-3.5-1] Element Document The Document element with cardinality [0, ∞] contains documents respectively and as specified in section 3.5.4 . Element TransformedData The TransformedData element with cardinality [0, ∞] contains the binary output of a chain of transforms applied by a client as specified in section 3.5.5 . Element DocumentHash The DocumentHash element with cardinality [0, ∞] contains the hash values as specified in section 3.5.6 . Format specific implementations including mappings to the generic terms are defined in 9.5 and 10.5 respectively.
dss-core-v2.0-wd01-2016-06-26.docx