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-2654) Public Commentsregarding part 3, Section 2.1



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

Dennis Hamilton commented on OFFICE-2654:
-----------------------------------------

NOTE: In ODF 1.2 Part 1 CD01-rev08, this issue now applies to section 3.1

In response to these three questions, it is claimed that the Zip specification specifies the answers.  Where in the Zip specification and what are the answers?  I don't believe there is such information for at least two of these and the third is at best inferred from the size of a length field.  Furthermore, some of the answers, such as they might be, will consist of deference to file-system characteristics, a consideration that does not apply to ODF unless we pick a file system for which compatibility is expected.

"1. Re: Question: Which character sets are support in file names? 
"This is defined by the Zip specification. ODF has no additional constrains. 

"2. Re: Question: Are path names and file names case-sensitive? 
"Section 3.8.4 [now 4.8.4] states: "The notation [of a path in the manifest.xml [why not of the manifest:full-path attribute value?]] is the same as for the "filename" fields of the Zip file's central directory." This means names must appear in the manifest as they appear in the zip file. Whether they are case sensitive is part of the Zip specification. 

3. Re: Question: What is the maximum allowed depth of the nested directory structure. 
This is defined by the Zip specification. ODF has no additional constrains. 

> Public Comments regarding part 3, Section 2.1
> ---------------------------------------------
>
>                 Key: OFFICE-2654
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2654
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Sub-task
>          Components: Packaging
>    Affects Versions: ODF 1.2 Part 3 CD 1
>            Reporter: Michael Brauer
>            Assignee: Michael Brauer
>             Fix For: ODF 1.2 Part 3 CD 2
>
>
> Section 2.1: General.
> The first paragraph is unclear, some information should be added while
> other information - like the first part of the first sentence - is
> overly explanatory, not entirely correct and makes the spec less future
> proof. It points to the wrong appendix. Suggested alternative:
> OpenDocument uses a package file to store the XML content of a document
> as separate parts together with associated data as file entries in a
> nested directory structure in a single package file. Some of the file
> entries should be compressed to further reduce the storage and
> bandwidth footprint of the package. The package is a Zip file [ZIP],
> whose structure is described in Appendix C. ODF Packages impose
> additional structure on the Zip file to accomplish the representation
> of OpenDocument Format documents.
> The first line of the second paragraph: switch word 'creating' for
> 'comprising'. The same line has a non-descript link to 'OpenDocument
> part 1', rather than a specific bibliographic reference.
> Fourth line of the second paragraph: should be "but only a single
> document SHALL be contained".
> Question: Which character sets are support in file names?
> Question: Are path names and file names case-sensitive?
> Question: What is the maximum allowed depth of the nested directory
> structure? Question: Is there an advice on files that themselves are ZIP
> Question: Are Multipart ZIP files allowed?
> Question: There seems to be no clear reference to the serialized
> version of an ODF file, e.g. the mapping in a single file.
> ------------
> It would be more logical to switch 2.3 and 2.2, given the order in
> which the information needs to be implemented. Currently it is only
> implicitly clear that the file mentioned in 2.3 needs to be the first
> file in the Zip container.

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