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] Updated: (OFFICE-2243) manifest:versionill-specified and misleading

     [ http://tools.oasis-open.org/issues/browse/OFFICE-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Brauer updated OFFICE-2243:

    Fix Version/s:     (was: ODF 1.2 Part 3 CD 1)

> manifest:version ill-specified and misleading
> ---------------------------------------------
>                 Key: OFFICE-2243
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2243
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Packaging
>    Affects Versions: ODF 1.2 Part 3 CD 1
>         Environment: This issue applies to the Public Review form of ODF 1.2 Part 3 cd01 all formats (files OpenDocument-v1.2-part3-cd01.odt, etc.) and to the corresponding schema (file OpenDocument-manifest-schema-v1.2-cd1.rng)
>            Reporter: Dennis Hamilton
> Section 3.8.14 manifest:version describes an optional attribute for the <manifest:file-entry> element.
> The naming of this attribute invites confusion with a possible version of the manifest XML file.  [I attest that I was laboring under exactly that confusion. -- orcmid]
> Taking manifest:version as described and as specified in the schema, however, the following questions arise:
> 1. There is no normative language of any sort associated with this element.  There is also no statement concerning this element in the conformance clauses of the Part 3 specification.
> 2. There is no stipulation on how this value is obtained other than it has a relationship to the MIME type specified in the required manifest:media-type entry of the <manifest:file-entry> element.  
> 3. There is no stipulation on consistency between this value and however version is determinable for the (sub-)document or file identified in the required manifest:full-path attribute.  
> 4. There is no stipulation on when this attribute shall/should be present or if it is always optional, regardless of any multiple versions of a format that might be associated with the same MIME type.
> 5. There is no indication of any obligations of a package producer to provide this attribute value, or when it is expected that it can be provided.
> 6. There is no indication of what behavior a package consumer might or might not associate with the presence/absence of this attribute.
> Basically, it is not clear what useful purpose is served by this attribute and what convention achieves that purpose.
> It also seems that this is too intertwined with knowledge of what all the documents and subdocuments are and what that means with respect to the specific version of a document format that is being carried in an ODF 1.2 package.  Maybe such constraints with regard to versions of subdocuments and other constituent files are a matter for ODF 1.2 Part 1 where it is possible to say something meaningful in the case of that specific format.

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]