OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (OFFICE-2561) ODF 1.2 Part 1 CD04:protection-key string encoding underspecified



    [ http://tools.oasis-open.org/issues/browse/OFFICE-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846#action_17846 ] 

Dennis Hamilton commented on OFFICE-2561:
-----------------------------------------

The [rfc2045] maximum line-size is irrelevant to the application for attribute values, although white space should continue to be ignored.  If there is a version of a Base64 specification that uses the same encoding but doesn't impose a line-length limit, that could be cited instead.  I chose [rfc2045] because it is already included in the ODF 1.2 Part 1 CD04 Normative References.

> ODF 1.2 Part 1 CD04: protection-key string encoding underspecified
> ------------------------------------------------------------------
>
>                 Key: OFFICE-2561
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2561
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Table, Text
>    Affects Versions: ODF 1.2 Part 1 CD 4 
>         Environment: This issue applies to all forms of ODF 1.2 Part 1 CD04 and to earlier working drafts and CDs as well.  The issue also applies to ODF 1.1 and ODF 1.0.
>            Reporter: Dennis Hamilton
>            Priority: Minor
>             Fix For: ODF 1.2
>
>
> The data type for table:protection-key (19.699) and text:protection-key (19.852) is given as string.
> Although those digest algorithms identified in section 5.9 of [xmlenc-core] specify that those results are to be converted to Base64 encodings, the specific Base64 encoding is not identified.
> Because it is permissible to introduce additional, arbitrary digest algorithms, it is also not clear what encoding is to be used for their results, especially for algorithms that only specify their results as sequences of bits.
> Inspection of examples in [xmlenc-core] reveals that MIME Base 64 encoding is being used.  This proposal establishes that encoding as the encoding that is used for all protection-key attribute values.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]