Chapter 14, Security, Control, and Digital Signatures
XFA Specification
Signed Forms
414
<reasons>
</filter>
</signData>
</event>
</field>
Then the additional information inserted into the XML digital signature could look like this:
<Signature Id=”mySIg” xmlns="http://www.w3.org/2000/09/xmldsig#">
<SignedInfo>
...
<Object>
<SignatureProperties>
<SignatureProperty ...>
<x:xmpmeta xmlns:x='adobe:ns:meta/'>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:Description rdf:about=""
xmlns:xmp="ns.adobe.com/xap/1.0/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xfa="http://www.xfa.org/schema/xfa-template/2.4/">
<xmp:CreateDate>2005-08-15T17:10:04Z</xmp:CreateDate>
<dc:description>Approved</dc:description>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>
</SignatureProperty>
</SignatureProperties>
</Object>
</SignedInfo>
</Signature>
Example
The following form presents buttons for signing, verifying, and unsigning the form. The signature includes
the root element of the data document and all of its content, but nothing else. When the signature is
present it is enclosed in an element called
signatures
which is placed within the
datasets
element.
Note the use of a prototype to avoid repeating information in each
signData
element.
<?xml version="1.0" encoding="UTF-8"?>
<?xfa generator="AdobeDesigner_V7.1" APIVersion="2.4.5277.0"?>
<xdp:xdp xmlns:xdp="http://ns.adobe.com/xdp/" ...>
<template xmlns="http://www.xfa.org/schema/xfa-template/2.1/">
<subform name="form1" ...>
<pageSet>
...
</pageSet>
<subform ...>
<field name="field1" ...>
...
</field>
<field name="field2" ...>
...
</field>
<field name="field3" ...>
...