Uploaded image for project: 'OASIS Digital Signature Services eXtended (DSS-X) TC'
  1. OASIS Digital Signature Services eXtended (DSS-X) TC
  2. DSSX-7

Cardinality problem with DocumentHashType object schema definition

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V1_WD01
    • Fix Version/s: csprd02
    • Component/s: Core
    • Labels:
      None
    • Proposal:
      Hide

      Introduce a new container element (e.g. 'DigestInfos') to hold the set of digest infos:

      <xs:complexType name="DocumentHashType">
      <xs:complexContent>
      <xs:extension base="dss:DocumentBaseType">
      <xs:sequence>
      <xs:element ref="ds:Transforms" minOccurs="0"/>
      <xs:element name="DigestInfos" type="dss:DigestInfoType" minOccurs="1"
      maxOccurs="unbounded"/>
      </xs:sequence>
      <xs:attribute name="WhichReference" type="xs:integer" use="optional"/>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>

      <xs:complexType name="DigestInfoType">
      <xs:sequence>
      <xs:element ref="ds:DigestMethod"/>
      <xs:element ref="ds:DigestValue"/>
      </xs:sequence>
      </xs:complexType>

      Show
      Introduce a new container element (e.g. 'DigestInfos') to hold the set of digest infos: <xs:complexType name="DocumentHashType"> <xs:complexContent> <xs:extension base="dss:DocumentBaseType"> <xs:sequence> <xs:element ref="ds:Transforms" minOccurs="0"/> <xs:element name="DigestInfos" type="dss:DigestInfoType" minOccurs="1" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="WhichReference" type="xs:integer" use="optional"/> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="DigestInfoType"> <xs:sequence> <xs:element ref="ds:DigestMethod"/> <xs:element ref="ds:DigestValue"/> </xs:sequence> </xs:complexType>

      Description

      The DocumentHashType derives from DocumentBaseTyope and therefore contains an 'ID' attribute of the typ 'xs:Id'.
      Due to privacy reasons document may be hashed on client side without prior knowledge which hash algorithm is required. In other use cases several different hashes of the document are required for different signatures or timestamps.

      The current just allows one hash algorithm and value to be associated with one document.

        Attachments

          Activity

            People

            • Assignee:
              kuehne Andreas Kuehne
              Reporter:
              kuehne Andreas Kuehne
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: