Public Comment 201809c00001s02: textual clarification regarding <ds:Manifest>

XMLWordPrintable

    • Hide

      Extend the SiognbedReference component with another element:

      <xs:attribute name="InManifest" type="xs:boolean" use="optional" default="false"/>

      Show
      Extend the SiognbedReference component with another element: <xs:attribute name="InManifest" type="xs:boolean" use="optional" default="false"/>

      Comments from TC ESI to OASIS DSS-X TC on DSS-X V2 -  2 of 19 submitted by Liaison Andreas Kuehne on behalf of Sonia Companies via message  201809c00001 per attachment with accessibility issues (word file)

      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

      Comment  #2:

      Clause 4.2.1. “An input document can also be a <ds:Manifest>, allowing the client to handle manifest creation while using the server to create the rest of the signature.”
      An initial search of the keywords ds:Manifest and Manifest does not hit any sentence explaining or developing how this situation can be managed and what does “allowing the client to handle manifest creation” actually means.
       
      REQUEST: CLARIFY THE TEXT, MAYBE ADDING SOME ADDITIONAL TEXT IN THE PROCESSING CLAUSES FOR THE CASE THE INPUTDOCUMENT CONTAINS A DS:MANIFEST, IF NOT, DELETE IT.
       
      AK: Just took text as it was in DSS v1.0: it was as it is. There is no problem in adding more text. Most of the text was taken from old v1.0 to prevent additional problems to compliant implementations.
      CONCLUSION: Pass the comment to DSS-X.

            Assignee:
            Andreas Kuehne (Inactive)
            Reporter:
            Andreas Kuehne (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: