[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (DSSX-38) Public Comment 201809c00001s14
[ https://issues.oasis-open.org/browse/DSSX-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Hagen updated DSSX-38: ----------------------------- Description: Comments from TC ESI to OASIS DSS-X TC on DSS-X V2 - 14 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 #14: |LR: I have not been able to read the specification, but I plan to do it.| |Frederick: We have some few comments. Maybe we could bring them later on or present them now| |Clause 4.3.4. Â COMMENTS: They are SignatureType refer to 7.1, which does not exist. It should be 9.1. When I look to the URIs we are missing URIs for PDF signatures| |AK: we took the URIs coming from DSS 1.0.| |JC: after DSS 1.0 became a OASIS standard, a number of profiles were created for managing PDF signatures (generation) as well.| |LR: there is a component drafted that you can pass to the server with a pdf document asking to the server to generate a PAdES signature.| |AK: the list is informal in the core, not limiting anything. I will take a look to the ETSI Profile for signing.| |CONCLUSION: raise the comment to OASIS DSS-X| Â (!)ÂSuggest to ignore for the sake of PRD01 comment processing to ignore the first line above that states: {quote}{{LR: I have not been able to read the specification, but I plan to do it.}} {quote} was: Comments from TC ESI to OASIS DSS-X TC on DSS-X V2 - 14 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} Â > Public Comment 201809c00001s14 > ------------------------------ > > Key: DSSX-38 > URL: https://issues.oasis-open.org/browse/DSSX-38 > Project: OASIS Digital Signature Services eXtended (DSS-X) TC > Issue Type: Bug > Affects Versions: PRD01 > Reporter: Andreas Kuehne > Priority: Major > Labels: PRD01_COMMENT, TC_ESI > > Comments from TC ESI to OASIS DSS-X TC on DSS-X V2 - 14 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 #14: > |LR: I have not been able to read the specification, but I plan to do it.| > |Frederick: We have some few comments. Maybe we could bring them later on or present them now| > |Clause 4.3.4. > Â > COMMENTS: > They are SignatureType refer to 7.1, which does not exist. It should be 9.1. When I look to the URIs we are missing URIs for PDF signatures| > |AK: we took the URIs coming from DSS 1.0.| > |JC: after DSS 1.0 became a OASIS standard, a number of profiles were created for managing PDF signatures (generation) as well.| > |LR: there is a component drafted that you can pass to the server with a pdf document asking to the server to generate a PAdES signature.| > |AK: the list is informal in the core, not limiting anything. I will take a look to the ETSI Profile for signing.| > |CONCLUSION: raise the comment to OASIS DSS-X| > Â > (!)ÂSuggest to ignore for the sake of PRD01 comment processing to ignore the first line above that states: > {quote}{{LR: I have not been able to read the specification, but I plan to do it.}} > {quote} -- 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]