[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: AW: [dss-x] Verification Reports for Visual Signatures
Hallo Ezer, Pim,
yes, the CommitmentTypeIndication-element is somewhat more
complex, but it seems that there would be a canonical way to
embed the simple Reason-element into the CommitmentTypeIndication-element.
The CommitmentTypeIndication-element is defined as follows:
<xsd:element name="CommitmentTypeIndication" type="CommitmentTypeIndicationType"/>
<xsd:complexType name="CommitmentTypeIndicationType">
<xsd:sequence>
<xsd:element name="CommitmentTypeId" type="ObjectIdentifierType"/>
<xsd:choice>
<xsd:element name="ObjectReference" type="xsd:anyURI" maxOccurs="unbounded"/>
<xsd:element name="AllSignedDataObjects"/>
</xsd:choice>
<xsd:element name="CommitmentTypeQualifiers" type="CommitmentTypeQualifiersListType" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="CommitmentTypeQualifiersListType">
<xsd:sequence>
<xsd:element name="CommitmentTypeQualifier" type="AnyType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
Hence it would be possible to define a URI, say
urn:oasis:names:tc:dss:1.0:profiles:PDF:Reason, which
indicates that the following CommitmentTypeQualifier, which is
in open type, is or contains the Reason-element. In a similar
fashion it would be possible to specify further elements,
which are part of a pdf-signature or may appear in the future.
What do you think about this line of integration?
BR,
Detlef
>
> >
> > I think that is a good point that there are additional information
> > needed to be included in the multi-signature report profile. I
> > mentioned that in the draft of the Visual Signature profile.
> > The question is whether to include this additional
> information in the
> > multi-signature report or in the visual signature profile.
> > I think that it makes more sense to mention elements such as field
> > name and reason in the visual signature profile as an extension to
> > the multi-signature report. (I'm not sure how formally and
> technically
> > this can be achieved though...)
>
> as the verification report profile already has different
> conformance levels ("basic" and "advanced") I would prefer
> not to introduce more levels by profiling this profile, but
> the "advanced" level should cover everything, which is
> necessary to support the different signature formats.
>
> EF - OK.
>
> Concerning the SignaturePtr-structure we could easily add the
> FieldName attribute. What do you think about the potential
> mapping of the PDF.Reason-element to the
> XAdES.CommitmentTypeIndication-element (cf. XAdES, v1.3.2,
> Section 7.2.6)?
>
> EF - Reason is a simple free text while as I understand
> CommuinmentTypeIndication is a much more complex element.
> I think it is important for this profile to enable retrieval
> of additional application specific information that is
> bounded to the digital signature as a generic element
> definition that can contain xs:string.
>
> BR,
> Detlef
>
> >
> > Regards,
> > Ezer
> >
> > -----Original Message-----
> > From: Pim van der Eijk [mailto:pvde@sonnenglanz.net]
> > Sent: Tuesday, July 01, 2008 11:41 AM
> > To: dss-x@lists.oasis-open.org
> > Subject: [dss-x] Verification Reports for Visual Signatures
> >
> >
> >
> > 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
> >
> >
> > -----Original Message-----
> > From: Detlef.Huehnlein@secunet.com
> > [mailto:Detlef.Huehnlein@secunet.com]
> > Sent: 05 May 2008 14:24
> > To: dss-x@lists.oasis-open.org
> > Subject: [dss-x] Groups - 1st working draft for multi-signature
> > verification reports profile
> > (2008_05_05_oasis-dss-profile-for-comprehensive-signature-veri
> fication-repor
> > t.doc) uploaded
> >
> > Dear DSS-X-team,
> >
> > I just uploaded the first working draft for the multi-signature
> > verification reports profile.
> >
> > I'm looking forward to interesting discussions via mail
> and/or in our
> > next telco.
> >
> > Best regards,
> > Detlef
> >
> > -- Detlef Huehnlein
> >
> > The document named 1st working draft for multi-signature
> verification
> > reports profile
> > (2008_05_05_oasis-dss-profile-for-comprehensive-signature-veri
> fication-repor
> > t.doc)
> > has been submitted by Detlef Huehnlein to the OASIS Digital
> Signature
> > Services eXtended (DSS-X) TC document repository.
> >
> > Document Description:
> > This document defines a protocol and processing profile of the DSS
> > Verifying Protocol specified in Section 4 of [DSSCore],
> which allows
> > to return individual signature verification reports for
> each signature
> > in a verification request and include detailed information of the
> > different steps taken during verification.
> >
> > View Document Details:
> > http://www.oasis-open.org/apps/org/workgroup/dss-x/document.ph
> p?document_id=
> > 28182
> >
> > Download Document:
> > http://www.oasis-open.org/apps/org/workgroup/dss-x/download.ph
> p/28182/2008_0
> > 5_05_oasis-dss-profile-for-comprehensive-signature-verificatio
> n-report.doc
> >
> >
> > PLEASE NOTE: If the above links do not work for you, your email
> > application may be breaking the link into two pieces.
> > You may be able to copy and paste the entire link address into the
> > address field of your web browser.
> >
> > -OASIS Open Administration
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the
> OASIS TC that
> > generates this mail. You may a link to this group and all
> your TCs in
> > OASIS
> > at:
> > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr
> oups.php
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the
> OASIS TC that
> > generates this mail. You may a link to this group and all
> your TCs in
> > OASIS
> > at:
> > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr
> oups.php
> >
> >
>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]