OASIS Digital Signature Services eXtended (DSS-X) TC

Hi all, I checked back with the TC Handbook regarding the promotion of the current draft of the core to CS. There is another 7 day ballot required and some work to do by the admins ( http://docs.oasis-open.org/TChandbook/Reference/CommitteeSpecs.html ). So I guess we are not that far from having the core 2.0 in the 'CS' state. But I would prefer to review the core regarding the RFC 2119 wording and assertion demarcation (and a few other minors). I presume that the volume of the 'assertion' changes may require another review period. We could move the current draft to CS and later on do the process with a core 2.0.1 again. This approach will not produce too much overhead as there are many other documents in the pipeline for the same process (Metadata, X.509, JWS). What's your opinion? Greetings, Andreas -- Andreas KÃhne Chair of OASIS DSS-X phone: +49 177 293 24 97 mailto: kuehne@trustable.de Trustable Ltd. Niederlassung Deutschland Gartenheimstr. 39C - 30659 Hannover Amtsgericht Hannover HRB 212612 Director Andreas KÃhne Company UK Company No: 5218868 Registered in England and Wales

Hi, IMHO we should fix the minors and then move it to CS. BR, dh -----UrsprÃngliche Nachricht----- Von: dss-x@lists.oasis-open.org <dss-x@lists.oasis-open.org> Im Auftrag von Andreas Kuehne Gesendet: Dienstag, 16. April 2019 16:03 An: dss-x <dss-x@lists.oasis-open.org> Betreff: [dss-x] Promotion of DSS-X core 2.0 to CS Hi all, I checked back with the TC Handbook regarding the promotion of the current draft of the core to CS. There is another 7 day ballot required and some work to do by the admins ( http://docs.oasis-open.org/TChandbook/Reference/CommitteeSpecs.html ). So I guess we are not that far from having the core 2.0 in the 'CS' state. But I would prefer to review the core regarding the RFC 2119 wording and assertion demarcation (and a few other minors). I presume that the volume of the 'assertion' changes may require another review period. We could move the current draft to CS and later on do the process with a core 2.0.1 again. This approach will not produce too much overhead as there are many other documents in the pipeline for the same process (Metadata, X.509, JWS). What's your opinion? Greetings, Andreas -- Andreas KÃhne Chair of OASIS DSS-X phone: +49 177 293 24 97 mailto: kuehne@trustable.de Trustable Ltd. Niederlassung Deutschland Gartenheimstr. 39C - 30659 Hannover Amtsgericht Hannover HRB 212612 Director Andreas KÃhne Company UK Company No: 5218868 Registered in England and Wales --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php