Hi Thorsten, with removing the keyinfo as child from manifest and writing the other keyinfo in lowercase, I have no further concerns. The attachment has on page third a diagram, of how I think it should be. Kind regards Regina OASIS Issues Tracker schrieb am 04.06.2018 um 17:35: [
https://issues.oasis-open.org/browse/OFFICE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=70089#comment-70089 ] Thorsten Behrens edited comment on OFFICE-3940 at 6/4/18 3:34 PM: ------------------------------------------------------------------ Hi Regina, no objections - the original proposal was just trying to be as close as possible to xmlenc-core1 - technically, there's no reason to have that extra level. Note though that (as your schema reflects), there can be more than one encrypted-key. As for the case, again that was inspired by xmlenc-core - for that one, let's simply lowercase it, there's no further duplications of CNAMES just differeing in case - or would the removal of the KeyInfo as noted above be enough to address your concern there, too? was (Author: thorsten.behrens): Hi Regina, no objections - the original proposal was just trying to be as close as possible to xmlenc-core1 - technically, there's no reason to have that extra level. Note though that (as your schema reflects), there can be more than one encrypted-key. As for the case, again that was inspired by xmlenc-core - for that one, let's simply lowercase it, there's no further duplications of CNAMES just differeing in case. Add OpenPGP-based XML encryption -------------------------------- Key: OFFICE-3940 URL:
https://issues.oasis-open.org/browse/OFFICE-3940 Project: OASIS Open Document Format for Office Applications (OpenDocument) TC Issue Type: New Feature Components: Packaging Affects Versions: ODF 1.3 Reporter: Thorsten Behrens Priority: Major Fix For: ODF 1.3 Currently ODF supports password-based encryption, using a user-provided string of characters to encrypt an AES session encryption key. That is not ideal in the context of sharing documents securely with wider audiences, since one always needs a secure sidechannel to distribute the passphrase. This proposal builds on top of
https://www.w3.org/TR/2002/REC-xmlenc-core-20021210/ for XML encryption, and essentially extends the ODF manifest markup with a few nodes to denote OpenPGP key material plus transport encryption for the session key -- This message was sent by Atlassian JIRA (v7.7.2#77003) --------------------------------------------------------------------- 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 Attachment: ManifestDiagramm 3940.odg Description: application/vnd.oasis.opendocument.graphics