1. Visual Signature Profile OASIS - DSS-X Session 2

2. Agenda Action Items from previous discussions Signature Operation Verification Operation

3. Action Items Support PDF Certify Operation A new Optional Parameter called: DocumentRestrictionLevel of type integer was added. This parameter defines the state of the restrictions the documents turns to when the digital signature operation is completed. Scenarios Vs. Conformance A new Optional Parameter called: VisualSignaturePolicy was added. This value is mandatory and define restrictions to the input parameters. For example, in the case of a simple workflow operation, the client is not allowed to send any configuration for the created visual signature. FieldName type A simple string is used instead of xs:ID.

4. Visible Signature Content

5. Visible Signature content Signer Information – items will be extracted from the signer’s certificate CA information – items will be extracted from the signer’s certificate Signature time Signer’s Related image Additional application information – Reason for the signature operation Digital Signature: Encoded digital signature Scanable digital signature

6. Visible Signature content – Cont. The information is either passed to the digital signature service as part of a “document submission” scenario or encoded inside the signature field. The configuration includes sub-elements, each element (text or image) will be incorporated to the signature field in a certain location. The location is abstract and a simple location type is defined.

7. Signature Operation

8. DSSSign operation The profile adds the following information that should be passed to the digital signature service: Visual Signature Policy – According to scenario Document Type: PDF, OOXML, Open Office, … Field ID Document Restriction Level Visual Signature Position Visual Signature configuration

9. DSSSign operation – document type Document Content and type – using the element in the DSSSign request. will include the document content. The MimeType attribute will include the type of the document. PDF – “application/pdf PDF – “application/pdf “ ODF – “application/vnd.oasis.opendocument.text” DOCX – “application/vnd.openxmlformats-officedocument.wordprocessingml.document” TIF - image/tiff … If the document is sent via the mime type will be taken. Mime Type is a mandatory parameter.

10. DSSSign operation – optional inputs </xs:choice></xs:complexType> DocumentID will be used if several documents need to be signed.

11. DSSSign operation – Sig. Position <xs:complexContent> </xs:compelxType>

12. DSSSign operation – Configuration </xs:choice> </xs:complexType> <xs:sequence> </xs:sequence></xs:compelxType>

13. DSSSign operation – Element Position <xs:complexContent> </xs:complexContent></xs:compelxType> The coordinates are relative to the visible signature rectangle (signature block)

14. DSSSign operation – Element Value <xs:complexContent> </xs:compelxType> In the same manner Images and URI are defined.

15. Signature Verification Operation

16. DSSVerify operation Optional Inputs: Field ID Only the digital signature that is linked to the given signature field is verified. VisibleIndicationFormat The Verify service can optionally embed a visual indication into the visible signature. The visible indication can include the following: Validation Mark – V, X, ? Verification Time – The time of verification action Verification Scope – An indication to the level of certification Optional output: Field ID – The ID of the validated field. DocumentWithSignature: In the case of IncludeVisibleIndication, the updated document is replied.

17. General Questions Can the reference include “functionality” of a given product such as Adobe Reader or MS Office? Should we avoid this? Is it required to include examples in the profile or is it the scope of another document? Next Step?