Mercurial > hg > ooxml

comparison annotate.xml @ 67:b66bcfae65d6

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
consistent defn style
author Henry S. Thompson <ht@markup.co.uk>
date Mon, 12 Jun 2017 17:20:14 +0200
parents 53dd4ccac4fb
children
comparison
equal deleted inserted replaced
66:d0edaceb04b6 67:b66bcfae65d6
52 </div> 52 </div>
53 <div> 53 <div>
54 <title>Annotator-supplied features</title> 54 <title>Annotator-supplied features</title>
55 <div> 55 <div>
56 <title>All types</title> 56 <title>All types</title>
57 <list type="defn"> 57 <list type="1defn">
58 <item term="comment">string: unconstrained. By its nature difficult to 58 <item term="comment">string: unconstrained. By its nature difficult to
59 exploit, really should only be used to document a problem with the available 59 exploit, really should only be used to document a problem with the available
60 feature&amp;value vocabulary or structure.</item> 60 feature&amp;value vocabulary or structure.</item>
61 </list> 61 </list>
62 </div> 62 </div>
63 <div> 63 <div>
64 <title>Both one-dimensional types</title> 64 <title>Both one-dimensional types</title>
65 <list type="defn"> 65 <list type="1defn">
66 <item term="type">string: <code>"data"|"key"|"label"</code> 66 <item term="type">string: <code>"data"|"key"|"label"</code>
67 <p>"key" is my preferred word for what Dresden call "attribute". In the 67 <p>"key" is my preferred word for what Dresden call "attribute". In the
68 simpler cases, think of it as what you might use in an HLOOKUP or VLOOKUP cell.</p> 68 simpler cases, think of it as what you find as the first row/column of the 2nd argument to an HLOOKUP/VLOOKUP call.</p>
69 </item> 69 </item>
70 <item term="content">fvd: 70 <item term="content">fvd:
71 <list type="defn"> 71 <list type="1defn">
72 <item term="type">string: <code>"currency"|"date"|"datetime"|"integer"|"float"|"key"|"label"|"string"|"time"</code></item> 72 <item term="type">string: <code>"currency"|"date"|"datetime"|"integer"|"float"|"key"|"label"|"string"|"time"</code></item>
73 </list> 73 </list>
74 <p>The "key" and "label" content types are for use (as in the Dresden 74 <p>The "key" and "label" content types are for use (as in the Dresden
75 paper example) where compound keys/labels are indicated by row or column spans.</p> 75 paper example) where compound keys/labels are indicated by row or column spans.</p>
76 </item> 76 </item>
77 </list> 77 </list>
78 </div> 78 </div>
79 <div> 79 <div>
80 <title>Matrices</title> 80 <title>Matrices</title>
81 <list type="defn"> 81 <list type="1defn">
82 <item term="type">string: <code>"table"|"data"|"label"|"condition"</code></item> 82 <item term="type">string: <code>"table"|"data"|"label"|"condition"</code></item>
83 <item term="content">fvd: 83 <item term="content">fvd:
84 <list> 84 <list type="1defn">
85 <item term="type">string: <code>"rows"|"columns"|"cells"</code></item> 85 <item term="type">string: <code>"rows"|"columns"|"cells"</code></item>
86 </list> 86 </list>
87 </item> 87 </item>
88 </list> 88 </list>
89 <p>When a form for a matrix is completed, if <code>type</code> is 'data' a pop-up should offer to auto-fill 89 <p>When a form for a matrix is completed, if <code>type</code> is 'data' a pop-up should offer to auto-fill