-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: PRD01
-
Fix Version/s: None
-
Component/s: Core
-
Labels:
-
Environment:
PDF and PAdES sigbature are not subject of the core but of the forthcoming AdES profile. Nothing to do here for the DSS-x core 2.0 .
-
Resolution:
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 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 #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:
LR: I have not been able to read the specification, but I plan to do it.