OASIS Open Mailing List Archives  ·  All Lists  ·  dss-x  ·  2008-07

dss-x — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

Groups - 1st working draft for multi-signature verification reports profile =?UTF-8?B?KDIwMDhfMDVfMDVfb2FzaXMtZHNzLXByb2ZpbGUtZm9yLWNvbXByZWhlbnNp?= =?UTF-8?B?dmUtc2lnbmF0dXJlLXZlcmlmaWNhdGlvbi1yZ


Hello Detlef, Ezer and others, 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? Where would the value for the PDF signature "Reason" fit in the verification report schema? 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? Pim

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]