dss-x — archive

[Detlef Huehnlein]

Hallo Pim, > For a project I have a requirement that covers both the > verification report profile and the visual signature profile. > The project is an electronic archival system that archives > PDF documents. To support retrieving documents based on > signature information, we want to run a verification report > on PDF documents to retrieve any signatures in them, at the > stage of adding new documents to the archive. Ideally, both > profiles could work together, so the verification report > could provide a full report for documents with visual signatures. > > For PDF documents, the verification should report on the PDF > fields "Location" and "Reason". In the verification report > schema, the Location could map to "SignatureProductionPlace". > Is that a correct assumption? yes, it would be natural to map PDF.Location to XAdES.SignatureProductionPlace. > Where would the value for the PDF signature "Reason" fit in > the verification report schema? The PDF.Reason element seems to be similar to the purpose of the XAdES.CommitmentTypeIndication element, which is a SignedDataObjectProperty and hence we should think about mapping it to this place. > In Ezer's draft Visual Signature profile, there is an added > element "SignatureReason" in > "VisualSignatureDisplayConfigType". Should the verification > report profile reference the visual signature profile and > retrieve such elements from its schema? We should try to end up with a single structure, which should be as simple as possible to cover XAdES/XMLDSig, CAdES/CMS and PDF. Hence in this case I tend to prefer to use the CommitmentTypeIndication-element instead of including the PDF-specific SignatureReason-element. What do you think? BR, Detlef > > Pim > > >