Notice show of hands on now to say base64Binary was The remaining minor issues was Re: [office] Groups - OpenDocument-v1.3-wd09-part2-packages.odt uploaded

[Patrick Durusau <patrick@durusau.net>]

Regina,

Notes on the rest of your post:

On 8/9/19 6:11 PM, Regina Henschel wrote:

Hi Patrick,

<snip>

Page 8
Suspicious [RNG] in item E)

Removed.

Page 15
item 4.8, The e in encrypted-key is not part of the "element" character style.

For that matter it should also have < and > in element style.

item 4.9, The word 'element' should have default character style.

done

Page 16
item 4.12, The words 'element contains' should have default character style.

and <manifest:PGPKeyID> should be in element style

item 4.13, The word 'element' should have default character style.

Done.

Page 16
item 4.14, 4.15 It is not good to have in both cases the word 'contains'. In case of CipherValue 'contains' is correct, because the raw encrypted data are the direct content of the element. But in case of CipherData the encrypted data is not the direct content. [xmldsig-core1] has the wording 'envelopes' in that case.

Envelopes is correct in xmldsig-core1 because the content model allows an identifier for encrypted data OR the CipherValue child element. Maybe either one.

What about just saying: The <manifest:CipherData> element contains a <manifest:CipherValue> element.

???

Inconsistent use with base64, 'a base64Binary sequence' (4.12) or 'a base64-encoded' (4.13) or 'in BASE64 encoding' (4.16.2, 4.16.5) or 'encoded as base64binary' (4.16.12)

Show of hands, is there a favorite or one that is standard usage?

Page 18
item 4.16.7, The second 'For a ' should be aligned with the first one.

Done.

All of these, plus the show of hands on base64Binary will appear in OpenDocument-v1.3-wd10-part2-packages.odt

Hope you are having a great week!

Patrick

Kind regards
Regina




Patrick Durusau schrieb am 07-Aug-19 um 03:58:

/Submitter's message/
Greetings!

Apologies for the delay but the light finally came on for the PGP encryption element additions. Not nearly as difficult as I thought it would be.

I will post a clean version tomorrow with a view of preparing for a vote on a committee draft.

Hope everyone is having a great week!

Patrick
-- Patrick Durusau
*Document Name*: OpenDocument-v1.3-wd09-part2-packages.odt <https://www.oasis-open.org/apps/org/workgroup/office/document.php?document_id=65742>
------------------------------------------------------------------------
*Description*
All issues applied.
Download Latest Revision <https://www.oasis-open.org/apps/org/workgroup/office/download.php/65742/latest/OpenDocument-v1.3-wd09-part2-packages.odt>
Public Download Link <https://www.oasis-open.org/committees/document.php?document_id=65742&wg_abbrev=office>
------------------------------------------------------------------------
*Submitter*: Patrick Durusau
*Group*: OASIS Open Document Format for Office Applications (OpenDocument) TC
*Folder*: 1.3 Drafts
*Date submitted*: 2019-08-06 18:57:46

---------------------------------------------------------------------
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

-- 
Patrick Durusau
patrick@durusau.net
Technical Advisory Board, OASIS (TAB)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau 

Attachment: signature.asc
Description: OpenPGP digital signature