Mercurial > hg > ooxml
changeset 64:823ac978f4ab
scrappy first pass w/o auto features
| author | Henry S. Thompson <ht@markup.co.uk> |
|---|---|
| date | Mon, 12 Jun 2017 16:46:45 +0200 |
| parents | 9cf99d513197 |
| children | 53dd4ccac4fb |
| files | annotate.xml dresden.jpg notes.txt sample2y/workbook_indented.xml |
| diffstat | 4 files changed, 109 insertions(+), 49 deletions(-) [+] |
line wrap: on
line diff
--- a/annotate.xml Mon Jun 12 13:40:56 2017 +0200 +++ b/annotate.xml Mon Jun 12 16:46:45 2017 +0200 @@ -38,16 +38,91 @@ representation and 'char' being ASCII-only (?).</p> <p>If possible, the selected range should appear as the value of the new name <emph>without</emph> single-quotes.</p> - <p>Some top-level features should be computed, others require annotator -decision. Some features are unique to a particular selection type, others are + <p>Some features can and should be computed, others require annotator +decision. Some features and/or feature values are unique to a particular selection type, others are shared across all or some types.</p> <p>Accordingly, in order for the annotator to supply the required information, a form should pop up with all the features appropriate to the selection type. Literal or array-valued form fields will just require a value menu (allowing multiple selection in the array-valued case), but features with dictionary values will require cascading sub-forms.</p> - <p>The sections below tabulate the annotator-supplied features and their -possible values.</p> + <p>The next two sections document the annotator-supplied and +software-supplied features. Except for 'comment', whose value is free text, +allowed values are tabulated.</p> + </div> + <div> + <title>Annotator-supplied features</title> + <div> + <title>All types</title> + <list type="defn"> + <item term="comment">string: unconstrained. By its nature difficult to +exploit, really should only be used to document a problem with the available +feature&value vocabulary or structure.</item> + </list> + </div> + <div> + <title>Both one-dimensional types</title> + <list type="defn"> + <item term="type">string: <code>"data"|"key"|"label"</code> + <p>"key" is my preferred word for what Dresden call "attribute". In the +simpler cases, think of it as what you might use in an HLOOKUP or VLOOKUP cell.</p> + </item> + <item term="content">fvd: + <list type="defn"> + <item term="type">string: <code>"currency"|"date"|"datetime"|"integer"|"float"|"key"|"label"|"string"|"time"</code></item> + </list> + <p>The "key" and "label" content types are for use (as in the Dresden +paper example) where compound keys/labels are indicated by row or column spans.</p> + </item> + </list> + </div> + <div> + <title>Matrices</title> + <list type="defn"> + <item term="type">string: <code>"table"|"data"|"label"|"condition"</code></item> + <item term="content">fvd: + <list> + <item term="type">string: <code>"rows"|"columns"|"cells"</code></item> + </list> + </item> + </list> + <p>When a form for a matrix is completed, if <code>type</code> is 'data' a pop-up should offer to auto-fill +based on <code>content/type</code>. If chosen, this fills the matrix with +named ranges of the appropriate orientation (rows, columns or, in the case of +<code>cells</code>, both). If +it's not too hard, it would be good to go on to pop up the form for each +generated range +in turn, either having asked in advance for appropriate +features whose values are the same for all the ranges, or carrying forward +values from one to the next as defaults.</p> + </div> + </div> + <div> + <title>Software-supplied features</title> + </div> + <div> + <title>Issues</title> + <div> + <title>Compound labels and keys</title> + <p>There's a problem with +defining the structure I want for compound labels and keys, in that you can't +for example select the 6th column of rows 2 through 4 in the Dresden example, +to denote the "Group stage/Match 2/GA" column label:</p> + <image source="dresden.jpg" textGloss="table with three-row labels involving column spans" original="http://upcommons.upc.edu/bitstream/handle/2117/100584/KDIR_2016_47_CR.pdf" width="75%"> +<licence></licence> + </image> + <p>Excel would allow you to define a name for +F2:F4 in that spreadsheet, but I don't <emph>think</emph> you can select that +range with the mouse</p> + </div> + <div> + <title>Metadata</title> + <p>Nothing in the above proposal provides a way to annotate what Dresden +call 'Metadata'. We could simply provide another 1-D type, e.g. 'meta', I suppose, or just allow uninteresting regions to remain unannotated. +There is a difference between on the one hand informative prose such as occurs in the Dresden +example with the Metadata label, and regions whose type is just not obvious (as +e.g. lots in the Kenneth Lay sheet from the Enron dataset...</p> + </div> </div> </body> </doc>
--- a/notes.txt Mon Jun 12 13:40:56 2017 +0200 +++ b/notes.txt Mon Jun 12 16:46:45 2017 +0200 @@ -228,6 +228,12 @@ ------------ @@ string identity, to say nothing of actual value, is lost -- fix? @@ row/column/both spans [what?] + +Now using up to 4 border colours to reflect incoming refs + @@ sort these before clipping to 4 to reflect frequency + @@ use vertical layering in the cell to get the borders + more evident when a background colour is present? Already + happening, just a bit hard to see, need a 1px space? ------ enron1k/kenneth_lay__19506 contains this formula:
--- a/sample2y/workbook_indented.xml Mon Jun 12 13:40:56 2017 +0200 +++ b/sample2y/workbook_indented.xml Mon Jun 12 16:46:45 2017 +0200 @@ -1,4 +1,4 @@ -<?xml version="1.0" encoding="UTF-8" standalone="yes"?> +<?xml version='1.0' encoding='UTF-8' standalone='yes'?> <workbook mc:Ignorable="x15" xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships" xmlns:x15="http://schemas.microsoft.com/office/spreadsheetml/2010/11/main"> <fileVersion appName="xl" lastEdited="6" lowestEdited="5" rupBuild="14420"/> <workbookPr defaultThemeVersion="124226"/> @@ -14,90 +14,69 @@ <sheet name="Sheet1" r:id="rId1" sheetId="1"/> </sheets> <definedNames> -<definedName - name="_R000" - comment="{type:row, +<definedName name="_R000" comment="{type:label, content:{type:string,static:yes,unique:no,nulls:yes}, - rel:{label:down,parent:_T000}}"> + rel:{label:down,parent:_M000}}"> "Sheet1!$A$1:$H$1" </definedName> -<definedName - name="_R001" - comment="{type:column, +<definedName name="_C001" comment="{type:data, content:{type:date, static:yes,unique:no,nulls:no}, format:{nf:14}, - rel:{parent:_T000}}"> + rel:{parent:_M000}}"> "Sheet1!$A$2:$A$61" </definedName> -<definedName - name="_R002" - comment="{type:column, +<definedName name="_C002" comment="{type:data, content:{type:integer, static:yes,unique:no,nulls:no}, format:{nf:1}, - rel:{parent:_T000,reffed:[_R003]}}"> + rel:{parent:_M000,reffed:[_C003]}}"> "Sheet1!$B$2:$B$61" </definedName> -<definedName - name="_R003" - comment="{type:column, +<definedName name="_C003" comment="{type:data, content:{type:integer, static:yes,unique:yes,nulls:no}, format:{nf:1}, - rel:{parent:_T000}}"> + rel:{parent:_M000}}"> "Sheet1!$D$2:$D$61" </definedName> -<definedName - name="_R004" - comment="{type:column, +<definedName name="_C004" comment="{type:data, content:{type:integer, static:yes,unique:no,nulls:no}, format:{nf:1}, - rel:{parent:_T000,reffed:[_R009]}}"> + rel:{parent:_M000,reffed:[_C009]}}"> "Sheet1!$E$2:$E$61" </definedName> -<definedName - name="_R005" - comment="{type:column, +<definedName name="_C005" comment="{type:data, content:{type:integer, static:yes,unique:no,nulls:yes}, format:{nf:1}, - rel:{parent:_T000,reffed:[_R003]}}"> + rel:{parent:_M000,reffed:[_C003]}}"> "Sheet1!$F$2:$F$61" </definedName> -<definedName - name="_R006" - comment="{type:column, +<definedName name="_C006" comment="{type:data, content:{type:text, static:yes,unique:no,nulls:no}, format:{nf:1}, - rel:{parent:_T000}}"> + rel:{parent:_M000}}"> "Sheet1!$H$2:$H$61" </definedName> -<definedName - name="_R007" - comment="{type:column, +<definedName name="_C007" comment="{type:data, content:{type:text, static:yes,unique:no,nulls:no}, format:{nf:1}, - rel:{parent:_T000}}"> + rel:{parent:_M000}}"> "Sheet1!$J$2:$J$61" </definedName> -<definedName - name="_R008" - comment="{type:column, +<definedName name="_C008" comment="{type:data, content:{type:integer, static:no,unique:no,nulls:no}, format:{nf:1}, - rel:{parent:_T000,refs:[_R001,_R005]}}"> + rel:{parent:_M000,refs:[_C001,_C005]}}"> "Sheet1!$C$2:$C$61" </definedName> -<definedName - name="_R009" - comment="{type:column, +<definedName name="_C009" comment="{type:data, content:{type:float, static:no,unique:no,nulls:yes}, format:{nf:164,code:0.0%}, - rel:{parent:_T000,refs:[_R004,_R005]}}"> + rel:{parent:_M000,refs:[_C004,_C005]}}"> "Sheet1!$G$2:$G$61" </definedName> -<definedName - name="_T000" - comment="{type:table, +<definedName name="_M000" comment="{type:table, columns:{labels:_R000, - data:[_R001,_R002,_R008,_R003,_R004,_R005,_R009,_R006,_R007]}}"> + data:[_C001,_C002,_C008,_C003,_C004, + _C005,_C009,_C006,_C007]}}"> Sheet1!$A$1:$J$61 </definedName> </definedNames>