DR-15-0023, "SML: Comments"

[MURATA Makoto]

Dear colleagues,

We also have to consider what is needed for Question 1.

>Question 1: Is it essential to use a VML file in order to do this? If
> so, shouldn't this be explained in the specification?

>Response 1: Excel only supports this through VML. We leave it to the
> standards body to decide if it wants to allow other supported ways
> of doing this.

Here is my take.

This limitation is specific to Excel.  OOXML certainly allows the use
of DrawingML.  It does not mandate the use of VML either.

If we save an Excel document with a comment as strict OOXML, we have a
drawingML document as well a VML document.  This drawingML document
contains no graphical information.  But this is just a design choice
in the design of Excel.  Nothing in OOXML prevents this DrawingML
document from having rich graphical information.

Excel always generates a VML document for an Excel document with
comments, even when we use strict OOXML (through MCE).  But
this is not a requirement of OOXML.  This is strictly a design choice
by Excel.  Nothing in OOXML mandates the use of VML.

I thus believe that no actions by WG4 are required for this quiestion.
Microsoft might want to document their design choice if they have not
done so already.

Regards,
Makoto

2017-04-06 22:32 GMT+09:00 MURATA Makoto <eb2m-mrt at asahi-net.or.jp>:

> To close this DR, it remains to provide words to implement the
> response 2 from the Seoul Meeting.  (Schema changes for response 3
> are already provided.)
>
> I propose to replace
>
>   The attribute is required and shall be unique across all comments in
>   shared workbooks.
>
> by
>
>   In shared workbooks, the attribute is required and shall be unique
>   across all comments.
>
> Regards,
> Makoto
>
> 2017-02-23 20:52 GMT+09:00 MURATA Makoto <eb2m-mrt at asahi-net.or.jp>:
>
>> I wrote:
>>
>> While trying to implement schema change, I find that
>> the complex type CT_CommentPr does not define
>> @rowHidden and @colHidde either.  They appear in
>> prose.
>>
>>
>> This issue is now in  separte DR, which is DR17-0006 — SML:
>> various attributes missing from the schema.
>>
>> Changing the schema for allowing @uiObject is covered by a
>> separate branch
>>
>> https://app.assembla.com/spaces/IS29500/git/commits/e6d224aa
>> 55818184e7b38e0f6ff16d8e5faa735d
>>
>> If this DR is closed in Seattle, I will merge this branch to the COR4
>> branch.
>>
>> Regards,
>> Makoto
>>
>> 2016-12-21 21:31 GMT+09:00 MURATA Makoto <eb2m-mrt at asahi-net.or.jp>:
>>
>>> While trying to implement schema change, I find that
>>> the complex type CT_CommentPr does not define
>>> @rowHidden and @colHidde either.  They appear in
>>> prose.
>>>
>>> I can provide schema fragments for them.  But
>>> are they optional or required?  If optional, what
>>> is the default value?
>>>
>>> Regards,
>>> Makoto
>>>
>>> 2016-09-22 11:36 GMT+09:00 MURATA Makoto <eb2m-mrt at asahi-net.or.jp>:
>>>
>>>> Changing the schema for allowing @uiObject is easy.  But what
>>>> is the default when this attribute is not specified?
>>>>
>>>> Regards,
>>>> Mkaoto
>>>>
>>>> 2016-09-20 21:03 GMT+09:00 Rex Jaeschke <rex at rexjaeschke.com>:
>>>>
>>>>> If a schema person could produce the (few) required schema lines, we
>>>>> might
>>>>> be able to close this one soon.
>>>>>
>>>>> Rex
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> 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/20170407/f84e1c15/attachment.html>