[OASIS Issue Tracker] Commented: (OFFICE-3371) chart:surface

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

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

Michael Brauer commented on OFFICE-3371:
----------------------------------------

Andreas: It seems that your proposal tries to combine the two different interpretations of surface charts into a single one with variants, to the degree that this is possible. This is good. However, it seem to make the description of a complex topic even more complex.

So, what about the following: 
1. Rather than trying to combine the two interpretations, we add them as two different chart types. This has the benefit that the descriptions of the the two cases gets simpler.
2. We give the two chart types new chart:class attribute values.
3. For chart:class="surface" we define that  dependent on the number of <chart:domain> elements either the one or the other surface chart type is meant. 
4. Optionally, we may deprecate the chart:class="surface" value. This would allow us to get rid of the implicit differentiation by the <chart:domain> elements. However, whether this step is reasonable depends on whether we believe that it may be possible to get a combine the definitions some time in a future.

> chart:surface
> -------------
>
>                 Key: OFFICE-3371
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3371
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Chart, Public Review
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Andreas Guelzow 
>            Assignee: Andreas Guelzow 
>             Fix For: ODF 1.2 CD 06
>
>
> In ODF 1.1 the desciption of chart class chart:surface is "the data points are interpreted as tabular data, where each value defines a 'height' at a specific grid location." 10.9 furtehr states that the "<chart:series> element represents a data series in a chart. If the chart requires more input data like scatter and bubble charts, <chart:domain> sub-elements must be defined that mainly contain the cell-range-address of the corresponding data."
> This would allow several surfaces to be shown in the same plot.
> In ODF1.2CD5 the description of chart:surface was changed in an incompatible way to read in 19.15.1:  The values given by a chart:values-cell-range-address attribute on multiple <chart:series> elements (marked as being of type chart:surface) are interpreted as altitudes at specific grid locations.
> Since an undefined number of series are used for a single surface it becomes impossible to have more than one surface in a chart.
> So in ODF 1.2 we require:
> <chart:series chart:values-cell-range-address="Sheet1.$B$3:.$B$8" />
> <chart:series chart:values-cell-range-address="Sheet1.$C$3:.$C$8" />
> <chart:series chart:values-cell-range-address="Sheet1.$D$3:.$D$8" />
> <chart:series chart:values-cell-range-address="Sheet1.$E$3:.$E$8" />
> while in ODF 1.1 it would have sufficed to specify:
> <chart:series chart:values-cell-range-address="Sheet1.$B$3:.$E$8" />
> which would allow additional surfaces defined by further series.
> Note that currently Gnumeric uses the second approach (extending it with two chart:domain sub elements if the x, and y values are not the default 1,2,..,5) while Excel uses the first approach.

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