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-3525) ODF 1.2 19.387office:value-type inconsistencies with Errata 02

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

Dennis Hamilton updated OFFICE-3525:

        Fix Version/s: ODF 1.2 CD 06
    Affects Version/s: ODF 1.2 CD 05

> ODF 1.2 19.387 office:value-type inconsistencies with Errata 02
> ---------------------------------------------------------------
>                 Key: OFFICE-3525
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3525
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Sub-task
>          Components: Database, Fields, Part 1 (Schema), Table, Text
>    Affects Versions: ODF 1.2 CD 05
>         Environment: This task applies to OpenDocument-v1.2-cd05-part1-editor-revision_04.odt
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>             Fix For: ODF 1.2 CD 06
> The restructuring of the treatment of 18,387 with a table has resulted in defects that cause deviation from ODF 1.0 Errata 02.  There are also improvements.
>  1. There are contradictory statements concerning the office:value-type="string" case.  This is apparently because "office:value" is stated when "Value Attribute" is intended.
>  2. office:value-type="void" only applies for a form property type and there is no accompanying Value Attribute in that case.
> This task is only for reconciliation of Errata 02, so only only new defects that are inconsistent with the schema and the coverage of the corresponding Errata 02 items and related defect reports are treated here.
> However, it is very confusing to have one table that applies to all cases of office:value-type, especially for the form-property-type-and-value-list case where there are multiple elements in a list that have the individual value Attribute cases, based on the office:value-type attribute of the parent element.  It takes considerable effort to analyze the schema to establish what the allowed cases actually are depending on the element where an office:value-type attribute is allowed.
> I also don't think the note about table cells versus field values is helpful.
> The meta:value-type definition seems to work without all of this, although I notice there is no statement there about omission of an office:string-value attribute when meta:value-type="string" (the default).
> And, finally, percentage is not precisely defined.  The example suggests that there is no difference between percentage and float, so is 1% a value of "1.00  or "0.01"?  If "0.01" is this really a type or is it a style/value-entry/formula-result trigger for adjustments made before seting the office:value attribute?

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]