Re: [dss-x] Visible Signature Profile

[kuehne@trustable.de]

Hi all,

as we can see with some of Pims comments the Visible Signature Profile tends to move into a PDF-specific direction very easily. On the other hand the profile is very sparse in its functionality to produce visible elements. So I would like to suggest to seperate the different concerns :

1. filling out ( invisible ) signature placeholders signing and verifying of
  - PDF
  - MS Office docs
  - OO docs
  - ...

2. filling out visible signature placeholders ( like bar codes or the autrian variant )

3.document management to insert, update and remove signature placeholders for signature representation and verification results

The first two tasks I would consider to be part of DSS's scope, but task 3 I would like to sort out to the different groups with expertise in these specific areas. Even the 'good old' PDF holds some many pitfalls regarding to its several types of signatures and related settings. Some may be true for the other office-type document standards.

Don't let us build a profile that's fail immediately in real life : 'Don't overprint the first signature with the second !', 'I need to add an additional page for the signature ...', 'I need to add a new signature beneath an exsiting signature ...', 'The verification result should placed reight bound to its signature ...' and all the other requirements only customers can think of ...

Greetings

Andreas

From: Pim van der Eijk <pvde@sonnenglanz.net>
To: Ezer Farhi <Ezer@arx.com>; Konrad Lanz <Konrad.Lanz@labs.cio.gv.at>
Cc: dss-x <dss-x@lists.oasis-open.org>
Sent: Friday, January 9, 2009 4:28:18 PM
Subject: RE: [dss-x] Visible Signature Profile

Hello Ezer,
 
Thanks for sending the updated draft. Here are some comments:
-  Some of the extension element are general extension elements, or document type-specific extensions elements rather than extensions related to the signature being "visual" or displayed. An example is the PDF "reason", "location", ContactInfo".  It would be clean to separate those from the visual aspects. E.g. PDF "location" is the same as XAdES "SignatureProductionPlace".
-  If this profile is to support manipulation of PDF documents, it would be nice if it would support explicitly setting the P entry for MDP signatures in the DSS request. "A value of 1 for P indicates that the document is intended to be final; that is, any changes invalidate the signature. The values 2 and 3 permit modifications that are appropriate for form field or comment workflows."
-  There is a relation with the multiple verification report profile:  when verifying e.g. a PDF document, the verify response should list the validity report of signatures that includes field names (as they typically express user roles).
-  2.3.1.2.1.2 <IncludeVisibleIndication/>, could we have something like <VisualDisplayConfig /> here so that in addition to visual validation status other verification information can be displayed visually?  E.g. the time and date of validation. Is this to be used in conjunction with <ReturnUpdatedSignature/>?
-  2.3.2.2 refers only to <Base64Data/>, but the server could also return the modified document as an attachment.
 
Good weekend and talk to you on Monday.
 
Kind regards,
 
Pim
 

 
 

From: Ezer Farhi [mailto:Ezer@arx.com]
Sent: 06 January 2009 13:36
To: Pim van der Eijk; Konrad Lanz
Cc: dss-x
Subject: [dss-x] Visible Signature Profile

Hi Pim and Konrad,

 

On next Monday we will progress with the Visible Signature profile.

 

I thought of going through a presentation that summarizes the current status of the profile in terms of requirements/decisions made so far and presenting the basic structure of the profile.

 

Attached to this email, a first draft of the presentation as well as an updated profile document.

 

Appreciate if you can go over the presentation and help me with ideas/remarks you have.

 

Also, appreciate remarks on the updated profile document.

 

Best Regards,

Ezer