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

[MURATA Makoto]

>§18.11.1.1 header (@maxRId, @minRId) (complex type: CT_RevisionHeader) –
Excel uses a default value
>0 for @minRId, and a default value equal to the current value of @minRId
for @maxRId

The default for @minRid can be specified in the schema, but that for
@maxRid should
be specified in prose.

Regards,
Makoto

2017-09-08 19:47 GMT+09:00 MURATA Makoto <eb2m-mrt at asahi-net.or.jp>:

> >§18.10.1.73 pivotTableDefinition (@applyAlignmentFormats,
> @applyBorderFormats,
> >@applyFontFormats, @applyNumberFormats, @applyPatternFormats,
> @applyWidthHeightFormats,
> >@dataPosition) (complex type: CT_pivotTableDefinition) – in each case
> default value 0
>
> These atributes except @dataPosition are defined in an attribute group
> AG_AutoFormat, which is referenced by CT_RevisionAutoFormatting
> (element "raf"), CT_QueryTable (element "queryTable").  Is it OK to
> introduce these defaults values for the elements raf and queryTable?
>
> Regards,
> Makoto
>
> 2017-09-08 19:25 GMT+09:00 MURATA Makoto <eb2m-mrt at asahi-net.or.jp>:
>
>> >§18.10.1.69 pivotField (@dataSourceSort, @numFmtId) (complex type:
>> CT_PivotField) – default values
>> >of false and true respectively
>>
>> But @numFmtId is of the type ST_NumFmtId, which is derived
>> from xsd:unsignedInt
>>
>> Regards,
>> Makoto
>>
>> 2017-09-07 22:28 GMT+09:00 MURATA Makoto <eb2m-mrt at asahi-net.or.jp>:
>>
>>> Francis,
>>>
>>> Thank you for your through analysis.  I am convinced that flase is the
>>> correct default
>>> value for color, tagColor, fgColor, bgCollor elements.
>>>
>>> I have incorporated this default value (and a few more) in the
>>> repository.
>>>
>>> I can probably finish introducing default values for closing this DR
>>> by the end of this week.
>>>
>>> Regards,
>>> Makoot
>>>
>>> 2017-09-07 19:42 GMT+09:00 Francis Cave <francis at franciscave.com>:
>>>
>>>> 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>:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Praying for the victims of the Japan Tohoku earthquake
>>>>
>>>> Makoto
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Praying for the victims of the Japan Tohoku earthquake
>>>
>>> Makoto
>>>
>>
>>
>>
>> --
>>
>> Praying for the victims of the Japan Tohoku earthquake
>>
>> Makoto
>>
>
>
>
> --
>
> Praying for the victims of the Japan Tohoku earthquake
>
> Makoto
>



-- 

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/20170908/5849e242/attachment.html>