OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [office-comment] Chart types (ODF all versions)


Not easy to describe a chart type. I suggest illustrations would be more
useful here. This should mean that the descriptions can be kept to a
minimum.

Joe Raftery


-----Original Message-----
From: Alex Brown [mailto:alexb@griffinbrown.co.uk] 
Sent: 26 March 2009 05:36
To: office-comment@lists.oasis-open.org
Subject: [office-comment] Chart types (ODF all versions)

Dear all,

18.15.1 enumerates a number of "pre-defined chart types".

In all cases these are described with a few lines of text. The
descriptions are often sloppily worded and circular, depending on other
chart type descriptions.

As such, they are inadequate as a basis for any implementation, let
alone for implementations that aspire to interoperability.

So for example, for "surface charts" we are told just:

----b
The values of multiple <chart:series> (marked as being of type
chart:surface) are interpreted as a 'altitude' at a specific grid
location. The graph may visualize these using colors for height
intervals, creating color bands similar to geographical maps.
----e

Is it really though that invoking "altitude" (in quotation marks) and
mentioning "color bands similar to geographical maps" is sufficient for
_any_ kind of technical specification, let alone a standard?

The text should be corrected/expanded to provide implementers with
sufficient information to implement such features without recourse to
reverse-engineering existing applications. Many of these chart types
probably require several pages of description, helpfully backed up with
illustrations.

Alternatively, if it is the contention of the TC that this terminology
is well-defined in other standards, then reference these instead.

- Alex.


-- 
This publicly archived list offers a means to provide input to the
OASIS Open Document Format for Office Applications (OpenDocument) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: office-comment-subscribe@lists.oasis-open.org
Unsubscribe: office-comment-unsubscribe@lists.oasis-open.org
List help: office-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/office-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office


This email (and any attachment) is intended only for the attention of the addressee. It is STRICTLY CONFIDENTIAL and may be legally privileged. If you have received it in error any disclosure distribution or copying of all or any part of the contents is prohibited. While virus checked by Hoare Lea, the recipient remains responsible for the consequences of any virus received.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]