[OASIS Issue Tracker] Commented: (OIC-5) Plugfest, subpackages(chart in spreadsheet)

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/OIC-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20062#action_20062 ] 

Dennis Hamilton commented on OIC-5:
-----------------------------------

I noticed that I can't find this JIRA issue on the OIC JIRA dashboard because it is marked as closed.

Svante,

I looked at the use of "relative path" in the [Zip] specification at http://www.pkware.com/documents/APPNOTE/APPNOTE_6.2.0.txt.  

This is only one occurrence of the term, and it is never defined.  (This is an extremely informal document.)

The use of "relative path" is in the context of whether or not path information is added to a Zip document filename in the Zip directory when a file is moved into the Zip. Those specification authors were not thinking about URLs at all, but about hierarchical file systems.  Also, there is no indication of "relative-to-what," although the utilities I use allow me to say how much information from the original location of the files is included in the Zip.  The Zip authors were not thinking about producers and consumers of Zip packages that worked with the package directly as a container and not as a means for archiving file-system data.

Here's the specific mention that I think we are talking about:

"file name: (Variable)

          The name of the file, with optional relative path.
          The path stored should not contain a drive or
          device letter, or a leading slash.  All slashes
          should be forward slashes '/' as opposed to
          backwards slashes '\' for compatibility with Amiga
          and Unix file systems etc.  If input came from standard
          input, there is no file name field."

The file name field occurs in what is called the local file header (it is a block of data that precedes the data of the file).  It is repeated in the file header that is also provided in the "central directory," near the end of the Zip package.  

It appears that the value of manifest:full-path for a package file (not a sub-document) should be an exact match for a file name entry in the Zip directory.  There is no Zip filename match for a sub-document manifest:full-path entry. There may be one or more package files that have the subdocument full-path value as the leading part of the Zip file name, however.

> Plugfest, subpackages (chart in spreadsheet)
> --------------------------------------------
>
>                 Key: OIC-5
>                 URL: http://tools.oasis-open.org/issues/browse/OIC-5
>             Project: OASIS Open Document Format Interoperability and Conformance (OIC) TC
>          Issue Type: Improvement
>          Components: ODF11-InteropProfile
>            Reporter: Bart Hanssens
>            Assignee: Bart Hanssens
>             Fix For: Working Draft
>
>
> From the tests performed on the The Hague plugtest wiki.
> Testing spreadsheets with an embedded chart revealed that some implementations use 
> <draw:object xlink:href="./Object 1"...
> While other(s) use:
> <draw:object xlink:href="Object 1/"...
> (The latter seems to be better)
> ODF 1.1 mentions sub packages in 9.3.3 Objects (Object Data), but  the wording can be improved
> "For objects that have an XML representation, the link references the sub package of the object. The object is contained within this sub page exactly as it would as it is a document of its own."
> And perhaps 17.5, Usage of IRIs Within Packages
> "A relative-path reference (as described in §6.5 of [RFC3987]) that occurs in a file that is contained in a package has to be resolved exactly as it would be resolved if the whole package gets unzipped into a directory at its current location. The base IRI for resolving relative-path references is the one that has to be used to retrieve the (unzipped) file that contains the relative-path reference."

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