FW: DRs waiting for MS experts

Thu Sep 13 00:03:07 CEST 2018

Re-sending on Alfred’s behalf, as he got a lot of messages regarding the inability to deliver when he posted this earlier today. Rex

From: Alfred Hellstern <Alfred.Hellstern at microsoft.com> 
Sent: Wednesday, September 12, 2018 5:31 PM
To: Rex Jaeschke <rex at RexJaeschke.com>; SC 34 WG4 <e-SC34-WG4 at ecma-international.org>
Subject: RE: DRs waiting for MS experts

I’ve included additional answers for some of the DRs relating to SML. Find them under 2018-09-12 below.

From: Rex Jaeschke <rex at RexJaeschke.com <mailto:rex at RexJaeschke.com> > 
Sent: Friday, September 7, 2018 6:28 PM
To: SC 34 WG4 <e-SC34-WG4 at ecma-international.org <mailto:e-SC34-WG4 at ecma-international.org> >
Subject: FW: DRs waiting for MS experts

Here’s more feedback (which includes that circulated recently). Rex

-------------------------------------

Raised because of problems

17-0016                                SML: Reference Sequence (sqref) Examples?

2018-09-12 Alfred Hellstern:

Response from our product team:

Excel does not consider the term ‘range’ in the descriptive text to have a specific technical meaning. For ST_sqRef we support the list of ranges defined in the schema, which includes both single cells and references to multiple cells.

17-0017                                SML: Column Width and Formatting       

2018-09-12 Alfred Hellstern:

Partial response from our product team:

In section 2.1.596 of MS_IO29500 we describe our implementation of col. Part a and b specific the minimum and maximum allowed values. Since 1 is the minimum value, it is 1 based indexing. Part f describes how we calculate width, which partially addresses the question relating to the width of col C.

The product team is still looking into the other questions about the col properties

17-0029                                SML: Quoting of Worksheet Names Containing Periods 

2018-09-04 Alfred Hellstern:

Alfred Hellstern: For the new questions in Charlie’s last comment, it would be better to open a new request since they are more broad than the original request and represent an increase in scope.

Response from our product team:

In his most recent comment, Charlie mentioned the original ask has been resolved. One clarification that can be made is to the EBNF to indicate that the first character of an unquoted name should be further restricted to also exclude ‘.’ and 0-9. 

2018-09-12 Alfred Hellstern:

Additional response from our product team:

Our intent by “names should be further restricted to also include ‘.’ and 0-9” is that those items need to be added to the list of characters that require quotation marks, not that they replace the existing list in the documentation. The existing list in MS-OI29500 2.1.861 does already include %. To the question around which version the issue existed in and was resolved in, since we have been unable to reproduce the issue internally, we are unable to comment on which versions experienced the behavior.

18-0009                                DML: 2D-Transforms     

2018-09-07 Alfred Hellstern:

Product team will look into this next quarter

18-0010                                SML: Optional spans and r attributes in sheet rows and cells?

2018-09-12 Alfred Hellstern:

Response from our product team:

The standard specifies that the span attribute is for optimization purposes only, and the proposed changes are overly prescriptive of functionality that is not correct. We propose making no change to the attribute.

We do agree the at the current definition of the ‘r’ attribute being default creates confusion.  We published an implementor’s note describing how we interpret the omitted attribute:  “If this attribute is not specified, the cell shall be located in the column with the index that is 1 greater than that of the previous cell in the parent row collection. If this attribute is not specified and the cell is the first c element in the parent row collection, the cell shall be located in the first column.” We do believe for clarity it makes sense to add the description of how to handle an omitted ‘r’ attribute on the CT_Cell element. We propose using our implementer’s note or something similar as the replacement text.

18-0011                                SML: Tables and Query Tables   

Raised by reviewing ISO/IEC 29500

15-0020                WML: Make clear where in transitional WML can VML occur

2018-09-07 Alfred Hellstern:

Response from our product team:

1)     shapeDefaults – standard states only vml-officeDrawing.xsd is allowed. Schema is consistent with this.

2)     hdrShapeDefaults – standard states only vml-officeDrawing.xsd is allowed. Schema is consistent with this.

3)     pict- need to investigate code to determine if it’s possible to write out both vml.xsd and vml-officeDrawing.xsd. Schema allows both namespaces, but standard indicates only vml.xsd is allowed.

4)     background- proposal is to insert a new section between 14.1 and 14.2 called Main Document Story that includes a new item describing use of VML for the background element, indicating that vml.xsd and vml-officeDrawing.xsd are allowed. This is consistent with the schema. I agree.

5)     object- proposal is to insert a new section after 14.3.2, to describe VML for object element, indicating that vml.xsd and vml-officeDrawing.xsd are allowed. This is consistent with the schema. I agree.

6)     Pml.xsd and sml.xsd- I’m not sure about this portion of the DR. Those appear to be related to PPT and XL Strict XML? (Correct me if I’m wrong here).

So I think we need to investigate 3) a little more, and I need help understanding whether 6) is really an item for us?

17-0002                PML:?sld?is missing its attributes

2018-09-07 Alfred Hellstern:

Response from our product team:

The DR refers to the three references to “sld”, and details confusion about what is defined where. The MS experts went through the documentation and it seems like everything is in fact correctly documented, but with the below errors/exceptions:

1.      19.3.1.38 needs to have its title and description updated. The existing description text should be removed as it incorrectly refers to another part.

a.      Title: sld (Presentation Slide)

b.      Description: This element specifies an instance of a presentation slide. Within a presentation slide are contained all elements that describe the objects and their corresponding formatting.

2.      19.2.1.31 needs to have its title updated.

a.      Title: sld (Slide Relationship Entry)

3.      19.2.2.14 needs to have its title updated

a.      Title: sld (Outline Slide Relationship Entry)

17-0004                DML: element?nvContentPartPr?exists in the schema but not in prose

2018-09-04 Alfred Hellstern:

Product team will look into this next quarter

17-0008                Shared ML:?version?attribute of?vstream?is missing from prose

2018-09-04 Alfred Hellstern:

Response from our product team:

It needs to be documented as a GUID string and something like “version is arbitrary and defined by the author of the specific property”.

17-0013                SML: Make clear where in transitional SML can VML occur

17-0014                PML: Make clear where in transitional PML can VML occur

2018-09-07 Alfred Hellstern:

Response from our product team:

              The answer to the question whether “VML in PML documents can occur only in vmlDrawing.xml?”, then the answer is “Yes”.

17-0021                DML: wild cards in the complex type CT_GraphicalObjectData of dml-main.xsd and dml-main.rnc

2018-09-07 Alfred Hellstern:

Product team will look into this next quarter

18-0005                DML: Reference to Non-Existent Child Elements of <c:layout>

Raised by the mixture

13-0014                PML: omissions and inconsistencies in the specification of attributes

2018-09-07 Alfred Hellstern:

Response from our product team:

yes it is a string of letters

16-0006                DML: Diagrams, Charts and SpreadsheetML Drawings: omissions and inconsistencies in the specification of attributes            

2018-09-07 Alfred Hellstern:

Product team will look into this next quarter

Click here <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.mailcontrol.com%2Fsr%2FMZbqvYs5QwJvpeaetUwhCQ%3D%3D&data=02%7C01%7CAlfred.Hellstern%40microsoft.com%7Cb2bdf55d58074547921808d6152ae3f2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636719671302091812&sdata=AsLns2SiXF%2BLxeVKm1pT3CWNU2NKAZL0Cc7cL7pBbjs%3D&reserved=0>  to report this email as spam.

This message has been scanned for malware by Forcepoint.  <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.forcepoint.com%2F&data=02%7C01%7CAlfred.Hellstern%40microsoft.com%7Cb2bdf55d58074547921808d6152ae3f2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636719671302091812&sdata=xSw8LlVzeWELfoeimoB%2BOw9GLpXdz2cBsVl32PzIVs4%3D&reserved=0> www.forcepoint.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20180912/10f48763/attachment-0001.html>