[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (DSSX-32) Public Comment 201809c00001s08
[ https://issues.oasis-open.org/browse/DSSX-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=71843#comment-71843 ] Andreas Kuehne commented on DSSX-32: ------------------------------------ Valid remark, the OptionalInputsVerifyType must offer a way to contain more than one distinct type of optional element. Proposed solution changing the definition of OptionalInputsVerifyType in the way as proposed in https://issues.oasis-open.org/browse/DSSX-31 for OptionalInputsSignType: drop xs:choice. > Public Comment 201809c00001s08 > ------------------------------ > > Key: DSSX-32 > URL: https://issues.oasis-open.org/browse/DSSX-32 > Project: OASIS Digital Signature Services eXtended (DSS-X) TC > Issue Type: Bug > Affects Versions: PRD01 > Reporter: Andreas Kuehne > Assignee: Andreas Kuehne > Priority: Major > Labels: PRD01_COMMENT, TC_ESI > > Comments from TC ESI to OASIS DSS-X TC on DSS-X V2 - Â8 of 19 submitted by Liaison Andreas Kuehne on behalf of Sonia Companies via message Â[201809c00001|http://lists.oasis-open.org/archives/dss-x-comment/201809/msg00001.html]Âper attachment with accessibility issues (word file) > {quote}following steering committee call on 17/09 and addition of 2 other editorial comments, the resulting pre-agreed comments are now for ESI approval for submission to OASIS DSS-X TC by 28 September > {quote} > h2. Comment Â#8: > |Clause 4.3.5.2. XML schema for OptionalInputsVerifyType >  > The definition of VerifyRequest includes the following sub-component > <xs:element minOccurs="0" name="OptionalInputs"â type="dss2:OptionalInputsVerifyType"/> >  > And clause 4.3.5.2 defines: > <xs:complexType name="OptionalInputsVerifyType"> >  <xs:complexContent> >  <xs:extension base="dss2:OptionalInputsBaseType"> >  <xs:sequence> >  <xs:choice> >  <xs:element maxOccurs="1" minOccurs="0" name="UseVerificationTime" >  type="dss2:UseVerificationTimeType"/> >  <xs:element default="false" maxOccurs="1" minOccurs="0" >  name="ReturnVerificationTimeInfo" type="xs:boolean"/> >  <xs:element maxOccurs="unbounded" minOccurs="0" >  name="AdditionalKeyInfo" >  type="dss2:AdditionalKeyInfoType"/> >  <xs:element default="false" maxOccurs="1" minOccurs="0" >  ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂname="ReturnProcessingDetails" type="xs:boolean"/> >  <xs:element default="false" maxOccurs="1" minOccurs="0" >  name="ReturnSigningTimeInfo" type="xs:boolean"/> >  <xs:element default="false" maxOccurs="1" minOccurs="0" >  name="ReturnSignerIdentity" type="xs:boolean"/> >  <xs:element maxOccurs="unbounded" minOccurs="0" >  name="ReturnAugmentedSignature" >  type="dss2:AugmentSignatureInstructionType"/> >  <xs:element maxOccurs="unbounded" minOccurs="0" >  name="ReturnTransformedDocument" >  type="dss2:ReturnTransformedDocumentType"/> >  <xs:element maxOccurs="1" minOccurs="0" >  ÂÂÂÂÂÂname="ReturnTimestampedSignature" >  type="dss2:AugmentSignatureInstructionType"/> >  <xs:element default="false" maxOccurs="1" minOccurs="0" >  name="VerifyManifests" type="xs:boolean"/> >  </xs:choice> >  </xs:sequence> >  </xs:extension> >  </xs:complexContent> > </xs:complexType> >  > Again, the sequence only has ONE child, which is a choice of the children of the <choice> component, but ONLY ONE, and consequently this schema does not allow to have more than one optional input. >  > REQUEST: EITHER SUPPRESS THE CHOICE WITHIN THE SEQUENCE OR ADD A MAXOCCURS TO THE SEQUENCE.| > |CONCLUSION: Pass the comment to DSS-X.| > {{Â}} -- This message was sent by Atlassian JIRA (v7.7.2#77003)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]