Mercurial > hg > ooxml
comparison annotate.html @ 68:95faecfcc1b5
consistent defn style
| author | Henry S. Thompson <ht@markup.co.uk> |
|---|---|
| date | Mon, 12 Jun 2017 17:20:24 +0200 |
| parents | d0edaceb04b6 |
| children |
comparison
equal
deleted
inserted
replaced
| 67:b66bcfae65d6 | 68:95faecfcc1b5 |
|---|---|
| 96 information, a form should pop up with all the features appropriate to the | 96 information, a form should pop up with all the features appropriate to the |
| 97 selection type. Literal or array-valued form fields will just require a value | 97 selection type. Literal or array-valued form fields will just require a value |
| 98 menu (allowing multiple selection in the array-valued case), but features with | 98 menu (allowing multiple selection in the array-valued case), but features with |
| 99 dictionary values will require cascading sub-forms.</p><p>The next two sections document the annotator-supplied and | 99 dictionary values will require cascading sub-forms.</p><p>The next two sections document the annotator-supplied and |
| 100 software-supplied features. Except for 'comment', whose value is free text, | 100 software-supplied features. Except for 'comment', whose value is free text, |
| 101 allowed values are tabulated.</p></div><div><h2>3. Annotator-supplied features</h2><div><h4>3.1. All types</h4><dl class=" "><dt><b><a name="comment">comment</a></b></dt><dd>string: unconstrained. By its nature difficult to | 101 allowed values are tabulated.</p></div><div><h2>3. Annotator-supplied features</h2><div><h4>3.1. All types</h4><ul class="naked "><li><a name="comment"><b>comment</b></a> |
| 102   string: unconstrained. By its nature difficult to | |
| 102 exploit, really should only be used to document a problem with the available | 103 exploit, really should only be used to document a problem with the available |
| 103 feature&value vocabulary or structure.</dd></dl></div><div><h4>3.2. Both one-dimensional types</h4><dl class=" "><dt><b><a name="type">type</a></b></dt><dd>string: <code>"data"|"key"|"label"</code><p>"key" is my preferred word for what Dresden call "attribute". In the | 104 feature&value vocabulary or structure.</li></ul></div><div><h4>3.2. Both one-dimensional types</h4><ul class="naked "><li><a name="type"><b>type</b></a> |
| 104 simpler cases, think of it as what you might use in an HLOOKUP or VLOOKUP cell.</p></dd><dt><b><a name="content">content</a></b></dt><dd>fvd: | 105   string: <code>"data"|"key"|"label"</code><p>"key" is my preferred word for what Dresden call "attribute". In the |
| 105 <dl class=" "><dt><b><a name="type">type</a></b></dt><dd>string: <code>"currency"|"date"|"datetime"|"integer"|"float"|"key"|"label"|"string"|"time"</code></dd></dl><p>The "key" and "label" content types are for use (as in the Dresden | 106 simpler cases, think of it as what you find as the first row/column of the 2nd argument to an HLOOKUP/VLOOKUP call.</p></li><li><a name="content"><b>content</b></a> |
| 106 paper example) where compound keys/labels are indicated by row or column spans.</p></dd></dl></div><div><h4>3.3. Matrices</h4><dl class=" "><dt><b><a name="type">type</a></b></dt><dd>string: <code>"table"|"data"|"label"|"condition"</code></dd><dt><b><a name="content">content</a></b></dt><dd>fvd: | 107   fvd: |
| 107 <ul class=" "><li>string: <code>"rows"|"columns"|"cells"</code></li></ul></dd></dl><p>When a form for a matrix is completed, if <code>type</code> is 'data' a pop-up should offer to auto-fill | 108 <ul class="naked "><li><a name="type"><b>type</b></a> |
| 109   string: <code>"currency"|"date"|"datetime"|"integer"|"float"|"key"|"label"|"string"|"time"</code></li></ul><p>The "key" and "label" content types are for use (as in the Dresden | |
| 110 paper example) where compound keys/labels are indicated by row or column spans.</p></li></ul></div><div><h4>3.3. Matrices</h4><ul class="naked "><li><a name="type"><b>type</b></a> | |
| 111   string: <code>"table"|"data"|"label"|"condition"</code></li><li><a name="content"><b>content</b></a> | |
| 112   fvd: | |
| 113 <ul class="naked "><li><a name="type"><b>type</b></a> | |
| 114   string: <code>"rows"|"columns"|"cells"</code></li></ul></li></ul><p>When a form for a matrix is completed, if <code>type</code> is 'data' a pop-up should offer to auto-fill | |
| 108 based on <code>content/type</code>. If chosen, this fills the matrix with | 115 based on <code>content/type</code>. If chosen, this fills the matrix with |
| 109 named ranges of the appropriate orientation (rows, columns or, in the case of | 116 named ranges of the appropriate orientation (rows, columns or, in the case of |
| 110 <code>cells</code>, both). If | 117 <code>cells</code>, both). If |
| 111 it's not too hard, it would be good to go on to pop up the form for each | 118 it's not too hard, it would be good to go on to pop up the form for each |
| 112 generated range | 119 generated range |