DR 19-0006

[Francis Cave]

In two cases the element being defined in §21.4, and therefore in the
DrawingML – Diagrams namespace, uses a content model that is defined in the
DrawingML – Main namespace, so in examples the prefix applied to the name of
element being defined should be different to the prefix applied to the names
of child elements. This applies to examples in the following sub-sections:

 

*	§21.4.3.1 bg (Background Formatting)
*	§21.4.5.6 sp3d (3-D Shape Properties)

 

The second of these was not listed below, because the examples already
contain prefixed names, but I now notice that the prefix on the parent
element is incorrect.

 

Francis

 

 

From: Francis Cave <francis at franciscave.com> 
Sent: 01 February 2019 00:46
To: SC34 <e-SC34-WG4 at ecma-international.org>
Subject: DR 19-0006

 

Murata-san and I are investigating the extent of the issue of unqualified
names in examples. So far we have identified a small number in Part 4 and a
large number in Part 1. Further investigation is needed. However, so far as
DR 19-0006 is concerned, I can be more specific as to the location of the
problem examples in Part 1 §21.4 DrawingML – Diagrams.

 

Examples in all the following sub-sections of §24.1 contain unqualified
element names that I believe should be qualified for consistency with the
way that examples are generally presented elsewhere in the specification.
Except where indicated, only a single example is involved. In all cases I
believe that the qualifying prefix ‘dgm:’ should be added to all element
names. Note that some of the sub-sections in this list are also the concern
of DR 19-0005.

 

*	§21.4.2.1 adj (Shape Adjust)
*	§21.4.2.2 adjLst (Shape Adjust List)
*	§21.4.2.3 alg (Algorithm)
*	§21.4.2.4 cat (Category)
*	§21.4.2.5 catLst (Category List)
*	§21.4.2.6 choose (Choose Element) – two examples, including one in
the attribute table
*	§21.4.2.7 clrData (Color Transform Sample Data)
*	§21.4.2.8 constr (Constraint) – ten examples, including nine in the
attribute table
*	§21.4.2.9 constrLst (Constraint List)
*	§21.4.2.12 else (Else) – two examples, including one in the
attribute table
*	§21.4.2.14 forEach (For Each) – four examples, including three in
the attribute table
*	§21.4.2.15 if (If) – seven examples, including six in the attribute
table
*	§21.4.2.17 layoutDefHdr (Layout Definition Header)
*	§21.4.2.19 layoutNode (Layout Node)
*	§21.4.2.20 param (Parameter)
*	§21.4.2.21 presOf (Presentation Of) – four examples, including three
in the attribute table
*	§21.4.2.24 rule (Rule) – six examples, including five in the
attribute table
*	§21.4.2.25 ruleLst (Rule List)
*	§21.4.2.26 sampData (Sample Data)
*	§21.4.2.29 styleData (Style Data)
*	§21.4.2.31 varLst (Variable List)
*	§21.4.3.1 bg (Background Formatting)
*	§21.4.3.2 cxn (Connection) – ten examples, including nine in the
attribute table
*	§21.4.3.3 cxnLst (Connection List)
*	§21.4.3.4 prSet (Property Set)
*	§21.4.3.5 pt (Point) – one example – Note that all the examples in
the attribute table correctly use qualified names
*	§21.4.4.4 colorsDefHdr (Color Transform Definition Header)
*	§21.4.5.1 cat (Category)
*	§21.4.5.2 catLst (Category List)
*	§21.4.5.3 desc (Style Label Description)
*	§21.4.5.8 styleDefHdr (Style Definition Header)
*	§21.4.5.10 styleLbl (Style Label)
*	§21.4.5.11 title (Title)
*	§21.4.6.1 animLvl (Level Animation)
*	§21.4.6.2 animOne (One by One Animation String)
*	§21.4.6.3 bulletEnabled (Show Insert Node)
*	§21.4.6.4 chMax (Maximum Children)
*	§21.4.6.5 chPref (Preferred Number of Children)
*	§21.4.6.7 hierBranch (Organization Chart Branch Style)
*	§21.4.6.8 orgChart (Show Organization Chart User Interface)

 

Francis

 

Click here <https://www.mailcontrol.com/sr/MZbqvYs5QwJvpeaetUwhCQ==>  to
report this email as spam.

 

This message has been scanned for malware by Forcepoint.
<http://www.forcepoint.com/> www.forcepoint.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20190225/3bc843dd/attachment-0001.html>