DR-17-0027, "SML: omissions and inconsistencies in the specification of attributes"

Francis Cave francis at franciscave.com
Thu Sep 7 12:42:54 CEST 2017


Murata-san

 

You make a good point. The same default value might not make sense in all these cases. The four cases you mention are in fact the only cases where a SpreadsheetML element uses the complex type CT_Color:

 

§18.3.1.15 color

§18.3.1.93 tabColor

§18.8.3 bgColor

§18.8.19 fgColor

 

In all these cases the description of @auto is the same: 

 

A boolean value indicating the color is automatic and system color dependent.

 

I’ve checked MS-OI29500, and the notes for each of the first three elements (i.e. excluding fgColor) all cross-refer to one another, indicating that what is said about one also applies to the other two. That suggests that Excel uses a default value of false for @auto in all the cases color, tabColor and bgColor.

 

On checking the MS-OI29500 notes for §18.8.19 fgColor, I find that this too cross-refers to the notes on the other three elements, which I take to imply that Excel also uses the default value of false for @auto in this case.

 

The second paragraph under §18.3.1.15 color states:

 

                The auto attribute shall not be used in the context of data bars.

 

A strict interpretation would mean that it is an error to include @auto in the context of the element dataBar. For example, the following is non-conformant according to the prose, although allowable according to the schema: 

 

            <dataBar>

                <cfvo type="min"/>

                <cfvo type="max"/>

                <color auto="false" rgb="FF638EC6"/>

            </dataBar>

 

However, I have tested this in Excel, and Excel does not complain. LibreOffice does not complain either.

 

Kind regards,

 

Francis

 

 

 

From: eb2mmrt at gmail.com [mailto:eb2mmrt at gmail.com] On Behalf Of MURATA Makoto
Sent: 07 September 2017 03:15
To: SC 34 WG4 <e-SC34-WG4 at ecma-international.org>
Subject: Re: DR-17-0027, "SML: omissions and inconsistencies in the specification of attributes"

 

> §18.3.1.93 tabColor (@auto) (complex type: CT_TabColor) – default value false

 

The complex type is CT_Color.  But this complex type is shared by elements 

such as color, tabColor, fgColor, and bgColor.  If we introduce a default value to 

this complex type, it will apply to these elements.  Is this OK?

 

Regards,

Makoto

 

2017-09-06 23:23 GMT+09:00 Rex Jaeschke <rex at rexjaeschke.com <mailto:rex at rexjaeschke.com> >:

 





 

-- 


Praying for the victims of the Japan Tohoku earthquake

Makoto

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20170907/bde8c0ca/attachment.html>


More information about the sc34wg4 mailing list