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=19006#action_19006 ] 

Michael Brauer commented on OFFICE-2654:
----------------------------------------

The references appendix is C rather than B. Correction appears in OpenDocument-v1.2-part3-cd01-rev03.

The first sentence of 2.1 indeed is not required, because it only explains why there are packages. It can be removed. Further it may be better to say "OpenDocument *defines* a package file". Correction appears in OpenDocument-v1.2-part3-cd01-rev03.

Re "switch word 'creating' for 'comprising'": The spec already says comprising. It is not clear what is suggested here.
Regarding a normative reference to part1: All three parts of the ODF specification are one standard. Adding a normative reference for another part of the same standard seems not be be reasonable, or at least reaquired.

Re: Fourth line of the second paragraph: should be "but only a single document SHALL be contained":
The correct term is "can" here, because it is simply impossible that multiple documents are stored in the root. Correction appears in OpenDocument-v1.2-part3-cd01-rev03.

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

Re: Question: Are path names and file names case-sensitive? 
Section 3.8.4 states: "The notation [of a path in the manifest.xml] 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.

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.

Re: Question: Is there an advice on files that themselves are ZIP 
No, there is not such advice. Whether a directory is better stored as Zip or as individual streams depends on the consumer of a package.

Re: Are Multipart ZIP files allowed? 
The Zip specification seems to allow that Zip files are spanned across several diskettes, but is rather silent on whether this is a file format feature or just an implementation feature. Whether this is support by a ODF application is implementation specific. 

Re: There seems to be no clear reference to the serialized version of an ODF file, e.g. the mapping in a single file.
Part 3 is about packages in general. Mentioning that ODF content may be stored in a flat format rather than in a package does not belong into part 3.

Re order of 2.3 and 2.3: The conformance clauses explicitly state that the mimetype stream must be the first one. Adapting the order of the two sections is therefore not necessary, and also not reasonable. The manifest.xml is the basic file of a package. It should be defined first.


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