Visual Signature ProfileVisual Signature Profile OASIS - DSS-X OASIS - DSS-X

AgendaAgenda

General Requirements – Digital Signature operationGeneral Requirements – Digital Signature operation

Visual Signature contentVisual Signature content

Verification OperationVerification Operation

General DefinitionGeneral Definition

The Digital Signature service will support adding a visual The Digital Signature service will support adding a visual signature inside a given document as part of a digital signature signature inside a given document as part of a digital signature operation.operation.

The verification service will supply visual related information The verification service will supply visual related information and may include visible indication related to the validity of the and may include visible indication related to the validity of the digital signature.digital signature.

Document TypesDocument Types

Q: Which documents types to support?Q: Which documents types to support?

Today, there are existing standard and proprietary Today, there are existing standard and proprietary implementations of a visible signature:implementations of a visible signature:

PDF – a visual signature is part of the PDF standardPDF – a visual signature is part of the PDF standardOFFICE 2007 – OOXML – relatively new implementationOFFICE 2007 – OOXML – relatively new implementationTIFF, Office XP/2003 – Proprietary implementationsTIFF, Office XP/2003 – Proprietary implementationsOpen Office – Are not familiar with an existing Open Office – Are not familiar with an existing implementationimplementation

A: The standard will not be limited to a certain type of A: The standard will not be limited to a certain type of documentdocument

Signature FieldSignature Field

Q: Geometry and Visual Structure of the Visible Signature?Q: Geometry and Visual Structure of the Visible Signature?

A Signature field is a “placeholder” for a digital signature and a A Signature field is a “placeholder” for a digital signature and a visible signature.visible signature.

A Signature field is identified by its xs:IDA Signature field is identified by its xs:ID

The signature field is located inside the document (page, (x,y) The signature field is located inside the document (page, (x,y) coordinates) and may contain meta information such as the coordinates) and may contain meta information such as the intended structure of the visible signature.intended structure of the visible signature.

A: The “signature field” terminology will be usedA: The “signature field” terminology will be used

Multiple Signatures per docMultiple Signatures per doc

Q: Multiple visible signature inside a Q: Multiple visible signature inside a document?document?

A document can be prepared to have many A document can be prepared to have many signature fieldsignature field

A: As part of the signature operation, a field A: As part of the signature operation, a field identification will be givenidentification will be given

Field Management operationsField Management operations

Q: Support of other operations such as Q: Support of other operations such as signature field creation, clear an existing signature field creation, clear an existing signature ?signature ?

A: No, the profile will support only a digital A: No, the profile will support only a digital signature operation. Other “field signature operation. Other “field management” operations may be handled management” operations may be handled elsewhere.elsewhere.

Usage ScenarioUsage Scenario

Three types of scenarios where identified:Three types of scenarios where identified:

Simple Workflow ScenarioSimple Workflow ScenarioThe document already contain signature fields. The client indicates The document already contain signature fields. The client indicates a single field to be signed.a single field to be signed.

Document SubmissionDocument Submission The document does not have any signature field embedded. The The document does not have any signature field embedded. The digital signature operation will generate a signature field and then digital signature operation will generate a signature field and then sign it.sign it.

Complex Signature RequestComplex Signature RequestMixtures of the above scenarios.Mixtures of the above scenarios.

Q: Will this usages scenario lead to restrictions/conformance Q: Will this usages scenario lead to restrictions/conformance levels? For example, the service will not allow creating a levels? For example, the service will not allow creating a signature field in the Workflow scenario.signature field in the Workflow scenario.

Vis. Signature displays a dig. Vis. Signature displays a dig. SignatureSignature

Q: Support cases where the Visible Signature Q: Support cases where the Visible Signature encode digital signature information?encode digital signature information?

On some documents type (for example, PDF), On some documents type (for example, PDF), the digital signature is based on the visual the digital signature is based on the visual signature and therefore the digital signature signature and therefore the digital signature cannot be encoded into the visual signature.cannot be encoded into the visual signature.

A: the profile is flexible so that depending of A: the profile is flexible so that depending of the document type, it will allow displaying the document type, it will allow displaying digital sig. content.digital sig. content.

Visible Signature contentVisible Signature content

Signer Information – items will be extracted Signer Information – items will be extracted from the signer’s certificatefrom the signer’s certificateCA information – items will be extracted from CA information – items will be extracted from the signer’s certificatethe signer’s certificateSignature timeSignature timeSigner’s Related imageSigner’s Related imageAdditional application information – Reason Additional application information – Reason for the signature operationfor the signature operationDigital Signature:Digital Signature:

Encoded digital signatureEncoded digital signatureScanable digital signatureScanable digital signature

Visible Signature contentVisible Signature content

The information is either passed to the digital The information is either passed to the digital signature service as part of a “document signature service as part of a “document submission” scenario or encoded inside the submission” scenario or encoded inside the signature field.signature field.

The configuration includes sub-elements, The configuration includes sub-elements, each element (text or image) will be each element (text or image) will be incorporated to the signature field in a incorporated to the signature field in a certain located identified by (x,y) certain located identified by (x,y) coordinates.coordinates.

DSSSign operationDSSSign operation

The profile adds the following information The profile adds the following information that should be passed to the digital signature that should be passed to the digital signature service:service:

Document Type: PDF, OOXML, Open Office, …Document Type: PDF, OOXML, Open Office, …

Field IDField ID

Visual Signature PositionVisual Signature Position

Visual Signature configurationVisual Signature configuration

DSSSign operation – document typeDSSSign operation – document type

Document Content and type – using the <Document> element Document Content and type – using the <Document> element in the DSSSign request. <Base64Data> will include the in the DSSSign request. <Base64Data> will include the document content.document content.The MimeType attribute will include the type of the document.The MimeType attribute will include the type of the document.

PDF – “application/pdfPDF – “application/pdf “ODF – “application/vnd.oasis.opendocument.text”DOCX – “application/vnd.openxmlformats-officedocument.wordprocessingml.document”TIF - image/tiff

If the document is sent via <AttachmentReference> the mime If the document is sent via <AttachmentReference> the mime type will be taken.type will be taken.

Mime Type is a mandatory parameter.Mime Type is a mandatory parameter.

DSSSign operation – optional inputsDSSSign operation – optional inputs

<xs:complexType name=VisualSignatureConfiguration”><xs:complexType name=VisualSignatureConfiguration”>

<xs:sequence><xs:sequence>

<xs:element name=”DocumentID” type=xs:ID” use=”optional”/><xs:element name=”DocumentID” type=xs:ID” use=”optional”/>

<xs:element ref=”FieldName” type=xs:string” use=”optional”/><xs:element ref=”FieldName” type=xs:string” use=”optional”/>

<xs:element ref=”VisualSignaturePosition” use=”optional”/><xs:element ref=”VisualSignaturePosition” use=”optional”/>

<xs:element ref=”VisualSignatureDisplayConfig” use=”optional”/><xs:element ref=”VisualSignatureDisplayConfig” use=”optional”/>

<xs:element name=”other” type=”dss:AnyType”/><xs:element name=”other” type=”dss:AnyType”/>

</xs:choice></xs:choice>

</xs:complexType></xs:complexType>

DocumentID will be used if several documents need to be signed.DocumentID will be used if several documents need to be signed.

Should the VisualSignaturePosition defined as abstract? If so should the profile Should the VisualSignaturePosition defined as abstract? If so should the profile include position terminology relevant to document types?include position terminology relevant to document types?

DSSSign operation – PositionDSSSign operation – Position

<xs:element name="VisualSignaturePosition" type=”VisualSignaturePositionType”><xs:element name="VisualSignaturePosition" type=”VisualSignaturePositionType”><xs:complexType name=VisualSignaturePositionType”><xs:complexType name=VisualSignaturePositionType”>

<xs:choice><xs:choice><xs:element ref=”SimpleVisualSignaturePosition”/><xs:element ref=”SimpleVisualSignaturePosition”/><xs:element name=”other” type=”dss:AnyType”/><xs:element name=”other” type=”dss:AnyType”/>

</xs:choice></xs:choice></xs:complexType></xs:complexType>

<xs:complexType name=SimpleVisualSignaturePosition”><xs:complexType name=SimpleVisualSignaturePosition”><xs:sequence><xs:sequence>

<xs:element name=”<xs:element name=”PageNumberPageNumber” type=”xs:integer”/>” type=”xs:integer”/><xs:element name=”<xs:element name=”TopLeft-XTopLeft-X” type=”xs:integer”/>” type=”xs:integer”/><xs:element name=”<xs:element name=”TopLeft-YTopLeft-Y” type=”xs:integer”/>” type=”xs:integer”/><xs:element name=”<xs:element name=”WidthWidth” type=”xs:integer” use=”optional”/>” type=”xs:integer” use=”optional”/><xs:element name=”<xs:element name=”HeightHeight” type=”xs:integer” use=”optional”/>” type=”xs:integer” use=”optional”/>

</xs:sequence></xs:sequence></xs:compelxType></xs:compelxType>

DSSSign operation – ConfigurationDSSSign operation – Configuration

<xs:element name="<xs:element name="VisualSignatureDisplayConfigVisualSignatureDisplayConfig" " type=”VisualSignatureDisplayConfigType”>type=”VisualSignatureDisplayConfigType”>

<xs:complexType name=<xs:complexType name=VisualSignatureDisplayConfigTypeVisualSignatureDisplayConfigType”>”><xs:sequence ><xs:sequence >

<xs:element name=”<xs:element name=”ShowLabelsShowLabels” type=”xs:boolean” use=”optional”>” type=”xs:boolean” use=”optional”><xs:choice minOccures=”0” maxOccures=”unbounded”><xs:choice minOccures=”0” maxOccures=”unbounded”>

<xs:element ref=”VisualSignatureItem”/><xs:element ref=”VisualSignatureItem”/></xs:choice></xs:choice>

</xs:sequence ></xs:sequence ></xs:complexType></xs:complexType>

<xs:complexType name=<xs:complexType name=VisualSignatureItemVisualSignatureItem”>”><xs:sequence><xs:sequence>

<xs:element name=”<xs:element name=”ItemNameItemName” type=”xs:String”/>” type=”xs:String”/><xs:element name=”<xs:element name=”ItemValueItemValue” type=”dss:AnyType” use=”optional”/>” type=”dss:AnyType” use=”optional”/><xs:element name=”<xs:element name=”ItemFontItemFont” type=”xs:string” use=”optional”/>” type=”xs:string” use=”optional”/><xs:element ref=”<xs:element ref=”ItemPositionItemPosition” />” />

</xs:sequence></xs:sequence></xs:compelxType></xs:compelxType>

DSSSign operation – ConfigurationDSSSign operation – Configuration

<xs:element name="<xs:element name="VisualSignatureDisplayConfigVisualSignatureDisplayConfig" " type=”VisualSignatureDisplayConfigType”>type=”VisualSignatureDisplayConfigType”>

<xs:complexType name=<xs:complexType name=VisualSignatureDisplayConfigTypeVisualSignatureDisplayConfigType”>”><xs:sequence ><xs:sequence >

<xs:element name=”<xs:element name=”ShowLabelsShowLabels” type=”xs:boolean” use=”optional”>” type=”xs:boolean” use=”optional”><xs:choice minOccures=”0” maxOccures=”unbounded”><xs:choice minOccures=”0” maxOccures=”unbounded”>

<xs:element ref=”VisualSignatureItem”/><xs:element ref=”VisualSignatureItem”/></xs:choice></xs:choice>

</xs:sequence ></xs:sequence ></xs:complexType></xs:complexType>

<xs:complexType name=<xs:complexType name=VisualSignatureItemVisualSignatureItem”>”><xs:sequence><xs:sequence>

<xs:element name=”<xs:element name=”ItemNameItemName” type=”xs:String”/>” type=”xs:String”/><xs:element name=”<xs:element name=”ItemValueItemValue” type=”dss:AnyType” use=”optional”/>” type=”dss:AnyType” use=”optional”/><xs:element name=”<xs:element name=”ItemFontItemFont” type=”xs:string” use=”optional”/>” type=”xs:string” use=”optional”/><xs:element ref=”<xs:element ref=”ItemPositionItemPosition” />” />

</xs:sequence></xs:sequence></xs:compelxType></xs:compelxType>

DSSSign operation – ConfigurationDSSSign operation – Configuration

<xs:complexType name=<xs:complexType name=ItemPositionItemPosition”>”>

<xs:choice><xs:choice>

<xs:element ref=”SimpleVisualSignatureElementPosition”/><xs:element ref=”SimpleVisualSignatureElementPosition”/>

<xs:element name=”other” type=”dss:AnyType”/><xs:element name=”other” type=”dss:AnyType”/>

</xs:choice></xs:choice>

</xs:compelxType></xs:compelxType>

<xs:complexType name=<xs:complexType name=SimpleVisualSignatureElementPositionSimpleVisualSignatureElementPosition”>”>

<xs:sequence><xs:sequence>

<xs:element name=”TopLeftX” type=”xs:integer”/><xs:element name=”TopLeftX” type=”xs:integer”/>

<xs:element name=”TopLeftY” type=”xs:integer”/><xs:element name=”TopLeftY” type=”xs:integer”/>

</xs:sequence></xs:sequence>

</xs:compelxType></xs:compelxType>

Should the position be defined as an abstract type here as well?Should the position be defined as an abstract type here as well?

DSSVerify operation DSSVerify operation

Optional Inputs:Optional Inputs:

Field ID – Only the digital signature that is linked to the given Field ID – Only the digital signature that is linked to the given signature field is verified.signature field is verified.IncludeVisibleIndication – The Verify service will embed a visual IncludeVisibleIndication – The Verify service will embed a visual indication into the visible signature that indicates the validation indication into the visible signature that indicates the validation status of the digital signature.status of the digital signature.

Optional output:Optional output:

Field ID – The ID of the validated field.Field ID – The ID of the validated field.

DocumentWithSignature:DocumentWithSignature:

In the case of IncludeVisibleIndication, the updated document is In the case of IncludeVisibleIndication, the updated document is retrieved.retrieved.

Conformance Conformance

Is Conformance necessary?Is Conformance necessary?Should we take the Should we take the