Dec 112015

NYEZ9X  ‘-’

  1. NYEZRG ‘This {post & its comments}’s ‘TOU(Terms Of Use) including copyright ©, confidentiality/privacy, info’s allowed use’ is’s default TOU(Terms Of Use) except: none.
  2. NZ23L1 ‘completeness stage’ CONSTRUCTING
  3. .

    NYEZQZ post name & ‘post image’:

    ‘{‘NOLDef’‘compare’ & {‘evaluate’ including ‘explain’} :NYG05K’} ‘in ‘NOLDef’’ :NYEZ9X

    1. NYF0IX ‘‘section history additional’ ‘in reverse start order’:’
      1. NZ2356 present name
        1. NZ23VJ ‘‘constructing: ’ factor out to #NZ23L1
          1. NZ23XC –an improvement very significant IMHO
        2. NZ23S1 updated to #NYR7NA & new point naming style ‘{generalization of latest example ‘‘representation :NYWN81’’} :NYYCRI
      2. NYF05J ‘‘constructing: {‘NOLDef’ ‘‘explain’ & ‘review’ & ‘compare’’‘in ‘NOLDef’’ ’NYEZ9X
      3. NYF0I3 ‘so post category’
        1. NYF0GR from post title
  4. NYEZQG To reply & discuss, please use’s default methods (click) except: none.
  5. NYEZQ3 remaining sections ‘definition’ + ‘post history additional’

  6. NYF0LR ‘definition’:   ‘‘definition in ‘NOLDef’ of concept’s’
    1. NYG05K remaining sections ‘compare’ & {‘evaluate’ including ‘explain’} :NYG05K
      1. NYQMII ‘usage’
        1. NYQMLV NYQMLV: intended so purpose:  to well organize/generalize {their remainder sections aka what they group}
        2. ‘in order’
      2. NYR8DQ ‘‘definition’ ‘anew’’
        1. NYQMO4 what  best accomplishes ‘NYQMLV: intended so purpose: ’
          1. NYR8DZ –been so far pretty hard
      3. NYQMPT ‘‘motivation or source or change’ ‘in reverse start order’’ split of source post.
      4. NYR7KU ‘name anew’
        1. NYR7NA‘compare’ & {‘evaluate’ including ‘explain’}’
        2. NYQMKL‘explain’ & ‘review’ & ‘compare’
        3.  ‘rendering anew’
    2. NYFJ2O ‘compare’
      1. NYR7IO ‘completeness stage’ experimental with pretty good confidence
      2.  remaining sections
      3. NYFJMB domain
        1. NWXU1I ‘-’ ‘‘same or similar’
          1. NX4GW3 usage
            1. NX4GWF instead of this, for  ‘sub’  have difference-computing functions {predefined & definable} and {‘‘a’’ selected}
              1. NX4H25 now starting to consider
          2. NWXUII ‘‘definition’ ‘anew’’
            1. NX3CUC LHS & RHS are related by their similarity, so by the degree, specifically percentage else amount,
              1. NWXUB2 of properties they both have
              2. NWXUIZ so degrees of {all} or {nothing} are not excluded unlike {”similar” with its meaning ‘1. resembling without being identical.’ apparently from Oxford}
              3. NX4FEI more specific numerical measures here depends foremost on the domain type:
                1. NX4FLP for where ‘‘relation transitivity’’ is not unknown,  this is ‘a’
                  1. NX3D3A for sets  which are countable at least roughly, this is ‘a’
                    1. NX4FH0 for human created categories
                    2. NX3CVA the # of common members, so the cardinality of intersection of the arguments.
                      1. NX3FDF if
                        1. NX421D ‘‘name’ ‘anew’’NX3CVA:1’
                          1. NX4284 ‘‘rendering’ ‘anew’’ ‘‘NX3CVA:1’’
                        2. NX4206 no other specifier (so the default)
                      2. NX4FAB so then say ‘{1 2 3} ‘same or similar’ ‘sub’ 2 {3}’
                    3. NX3F3I #NX3CVA divided by the average argument size argument cardinality
                      1. NX3F3Q where average is ‘a’
                        1. NX3EYR geometric mean
                          1. NX3F78 due to it being the arithmetic mean of logarithm
                          2. NX41QV ‘notable pros thru cons’
                            1. NX41RF appears suited for typical categorizations as, taxonomic rank, as generally each class parent class is a multiple of its average kid size.
                        2. NX3D78 arithmetic mean
                  2. NX4FM6 otherwise especially (such as general categories)
                    1. NX4G52 such as for
                      1. NX4G6N general categories & classifications
                      2. NX4G6Z common total orders,
                    2. NX4FOV the distance else number of hops between the compared elements
                      1. NX4GEM so
                        1. NX4GEX for any number x & y, ‘x ‘same or similar’ ‘sub’ y (x-y)’
                          1. NX4GA7 so for example, ‘4.4 ‘same or similar’ ‘sub’ 1.1 3.3’
          3. NWXU5H ‘‘name’ ‘anew’’
            1. NWXU4J ‘same or similar’
              1. NWYEKG ‘‘rendering’ ‘anew’’
                1. NWYEKT‘same or similar’
          4. NWYEN8 ‘‘‘Pretty Link’ entry’ ‘anew’’
            1. NWYENR 1st
      4. NYFJ53 sub/super
        1. remaining sections
        2. NYG12L per se
          1. NYI47N arguments specified by name
            1. NX5JL3 ‘-’  ‘‘adding’
              1. NX5K1Z ‘‘definition’ ‘anew’’
                1. NX5JM0 syntax: none to remove bias and instead fully focus is operation including per goal NX5YQA
                2. NX5JNX the situation where for any given parameters, all of:
                  1. NYD2B8 elements in their domains
                    1. NX5LIS #NX5JS2  & ToPt element of #NX5LKL
                    2. NX5LOO ‘addend’ element of #NX5LMA
                    3. NX5LQJ #NX5JT8 element of #NX5LP3
                    4. NX5MI6 #NX5MAH  element of  #NX5M7Z
                    5. NYD2C1 etc
                  2. NYD2CC core relationship
                    1. NX5JW3 ‘adder’{FrPt ‘addend’} = ToPt
                  3. NYD2CQ 2ndary relationship equivalent to core
                    1. NX5M6Z #NX5MAH{ToPt FrPt} = ‘addend’
                    2. NYD27T ‘adder’{ToPt  #NYD205{FrPt}} = ‘addend’
                    3. NYD2EM ‘adder’ToPt #NYD205{‘addend’}} =  FrPt
                3. NX6B8D ‘a’
                  1. NX6BC0 avoid creating negative numbers/objects where practical
                    1. NX6BE6 so for say #NX5XN5 and equivalent,
                      1. NX6BEE ensure {  ToPt  >= FrPt} –else #NX5JSY  will be negative
                    2. NYCZ9L more on this & why at
              2. NX5XHG ‘per def’
                1. NX5Y19 Rosetta Stone-ish
                  1. NX5XN5 {{#NX5JT8 equivalent} ToPt ‘sub’ #NX5JSY  FrPt}
                  2. NX5XF0 {ToPt ‘compared to’ FrPt {informally: #NX5JT8  #NX5JSY}}
                  3. NX5YFY {{#NX5JT8 equivalent} ‘weighted graph’ relation {FrPt to ToPt } has weight #NX5JSY}
                  4. NX5Y45 #NX5UYN at least #NX5W02
                2. NX5XI8 ‘notable pros thru cons’
                  1. NX5XHU per #NX5Y19, highly unifying  abstraction
                3. NX5XIP ‘same or similar’ ‘sub’
                  1. NX5YQZ <0
                    1. NX5YQA to {find & compare better syntax in various realizations, as done by this Rosetta stone}
                  2. NX5LVY 0
                    1. NX5V7N seemingly {any so universal} 2-value comparison
                    2. NX5LVB difference especially differencing
                  3. NX5UYN >0
                    1. NX5W02 if viewed from #NX5M7Z
                      1. NX5WUT in the sibling cases given here (and perhaps more even all)
                        1. NX5W3J is 1 difference (mathematics/computer science) at least informally
                      2. NX5WN9 if limited to the adding/‘removing objects from a collection’*
                        1. NX5WGB if  #NX5LKL=#NX5LMA
                          1. NX5W7T is 1 relative compliment
                          2. NX5W26 ‘represent’*ed with, rather than the objects per se, measure(s) of the objects notably counts, notably via 1 of {number  vector matrix}}
                            1. NX6ANJ for instance, for sets A & B, {cardinality {B \ A}} computed via {{cardinality B} – {cardinality B}} which is indeed equal by only requiring {A is a subset of B}.
                            2. NX5V1O is 1 [arithmetic] subtraction
                              1. NX6AFG current snapshot
                        2. NX5XAR changes/differences to text strings and potential arbitrary data
                          1. NX5XDQ is 1 data differencing
              3. NX5K5I ‘‘name’ ‘anew’’
                1. NYCZD5 NYCZD5(‘goal’): quality from most desirable roughly
                  1. NYCTOA standard name virtues ‘NXNaGo’ (as normal, some but not all are top here)
                  2. NYCZWA #NYCZWA(‘number operands’): suggests number operands
                  3. NYCU0X suggests a difference/span between two points
                    1. NYCTI3 #NYCTI3(‘direction’): suggests the direction (notably from one point to another)
                    2. NYCTH9 #NYCTH9(‘adding focus’): focuses on adding rather than subtracting (notably to get between the points)
                      1. NYCUBW I’ve always found it dizzying to think in terms of subtraction results. Rather I want to think of fill in the ‘addend’. But
                      2. NYCVVH no familiar name for this concept has this property.
                      3. NYCYJ9 Yes subtraction is how we know to compute the answer, but we don’t need to phrase the question & understand & even verify the answer (we can verify with just addition), so adding subtraction terminology (as ‘difference’ and similar do) is doing bads:
                        1. NYCYTR pushing into our face new a new operator (subtraction) and even new objects (negative numbers), so moving us away from canonical knowledge forms and adding complexity & clutter, and for no good reason I can see especially when in many case we don’t want know how to do x just get & perhaps verify the answer.
                        2. NYCYUU biasing how we are to get an answer
                        3. NYCYV5 instead of positives, focusing on negatives (subtraction & potentially negative numbers) –aesthetically not a good idea, either.
                      4. NYCYPG Similarly, constraint based programming can handle subtraction (and division, logs) via only addition (& multiplication, exponentiation, etc.)
                    3. NYDORX #NYDORX(‘any size’): can be any size, ideally including infinite
                  4. NYCTIQ #NYCTIQ(‘non-number operands’): suggests non-number operands
                2. NYD1EY #NYD1EY(‘adding’): ‘adding’
                  1. NYD1O3 ‘‘rendering’ ‘anew’’ ‘‘adding’
                  2. NYD1F7 from #NYCTBF(‘addend’)
                3. NYD1I7 ‘addition’
                  1. NYD1IZ from #NYCTBF(‘addend’)
                4. NYD1JI ‘summing’
                  1. NYD1KS from #NYD1EY(‘adding’)
                5. NYCJZOoffsetting’
                  1. NYCK8V from #NX5K6W as:
                    1. NYCK9F seems still accurate if we generalize op to vectors or equivalent, so to do destructuring/parallel (assignment), ArrayFormula, and similar op.
                    2. NYCKO0 shorter & notably simpler
                6. NX5K6W ‘1 offsetting’
                7. NX5K6K ‘[the state/condition of a ]offset’
                8. NX5VHQ ‘1 incrementing]’
                9. NX5VGB ‘1 un-decrementing’
                10. NX5K68 ‘difference’
                11. NX5K5T ‘differencing’
              4. NYCKWN ‘‘motivation or source or change’ ‘in reverse start order’’
                1. NYCPCD to capture the big picture of subtraction & difference & ‘sub’ & similar
                  1. NYCKWY accordingly ‘-ing(verb)’
              5. NYCJU2 ‘‘‘Pretty Link’ entry’ ‘anew’’ from my id for this section to /5138
              6. NX5JPQ parameter
                1. NX5JQ0 immediate
                  1. NX5JQG qty
                  2. NX6C4P function
                    1. NX5JUV ‘1’/each
                      1. NX5JT8 ‘-’   ‘‘adder’
                        1. NX6GIR domain
                          1. NX5LP3 ‘1’ ‘-’  offsetters
                        2. NYDPLN ‘‘name’ ‘anew’’
                          1. NYDPMB for qualities, see NYCZD5(for parent concept)
                          2. NYDPOY ‘adder’
                            1. NYDPSR ‘‘rendering’ ‘anew’’ ‘‘adder’
                          3. NYDPRA ‘extender’
                          4. NYDPQC ‘incrementor’
                          5. NYDPNL ‘offsetter’ –at time of id #NX5JT8
                          6. NYDPPN ‘summer’
                      2. NX5MAH ‘-’  subtractor
                        1. NX6GJY domain
                          1. NX5M7Z ‘1’ ‘-’  subtractors
                      3. NYD205 ‘-’  negator
                        1. NYD213 domain
                          1. NYD21Z ‘1’ ‘-’  negators
                        2. NYD31C warning: negation can lead to contradiction in some contexts.
                          1. NYD3E4 Specifically negation, at least when it comes to sets, is essentially absolute compliment which presumes ‘a universe U is defined’, but ZFC ‘ is the most common foundation of mathematics’ and ‘does not allow for the existence of a universal set (a set containing all sets) nor for unrestricted comprehension, thereby avoiding Russell’s paradox’
                  3. NX6GCP data
                    1. NX6GD1 for subtraction, terminology given at
                    2. NX6CKX point
                      1. NX6CLR qty 2
                      2. NX6GX1 the combo
                        1. NX5M5D domain
                          1. NX5LKL ‘-’  points
                        2. NX6D12 ‘‘name’ ‘anew’’
                          1. NX6C0M prefer match #NX5JS2/#NX5JQU per #NX6BEE
                          2. NX6DN5 ‘FrPt/ToPt’
                            1. NX6DPI source #NX6D2Q cutting to 1st 2 characters, then adding {‘Pt’ as 2-character abbreviation for ‘Point’} then putting all in CamelCase.
                            2. NX6DT3 ‘notable pros thru cons’
                              1. NX6EUK meets all 9 NXNaGo including:
                                1. NX6EV0 only 4 characters long.
                              2. NYCF3J page 1 shows no near matches further suggesting these 2 are good name choices.
                          3. NX6D2Q ‘from/to’
                            1. NX6DAE ‘notable pros thru cons’
                              1. NX6DBD very familiar
                              2. NX6DBS preposition lacking noun –con
                          4. NX6D49 ‘begin/end’
                          5. NX6D3S ‘start/stop’
                            1. NX6DFB ‘notable pros thru cons’
                              1. NX6DG8 intermediate overtone –seems con
                          6. NYD0IU ‘augend/sum’
                            1. NYD0JE from #NX6GD1
                          7. NX6CX0subtrahend/minuend
                            1. NYCVBG from #NX6GD1
                            2. NX6CZQ ‘notable pros thru cons’
                              1. NX6D01 at least for subtraction, exactly the meaning –notable pro
                              2. NX6D9E mouthful –con
                              3. NX6DJG focuses on the operator, not the purpose –notable con
                              4. NX6D94 very unfamiliar –notable con
                      3. NX6CP3 ‘1’/each
                        1. NX5JS2 ‘-’ ‘FrPt
                          1. NX6BWJ ‘‘name’ ‘anew’’ {from combo‘‘rendering’ ‘anew’’
                            1. NYDPCBFrPt
                            2. NX6FNXFrPt
                          2. NX6FJK ‘‘‘Pretty Link’ entry’ ‘anew’’ 1st
                        2. NX5JQU ‘-’   ‘ToPt
                          1. NX6FTA ‘‘name’ ‘anew’’ {from combo‘‘rendering’ ‘anew’’
                            1. NYDON1ToPt
                            2. NX6FTUToPt
                          2. NX6FPF ‘‘‘Pretty Link’ entry’ ‘anew’’ 1st
                    3. NX6GM4 subject
                      1. NX5JSY ‘-’  ‘‘addend’
                        1. NX6GRU domain
                          1. NX5LMA ‘-’  difference/offsets
                        2. NX5YYV ‘‘name’ ‘anew’’
                          1. NYCTGJ for qualities, see NYCZD5(for parent concept)
                          2. NYCTBF #NYCTBF(‘addend’): ‘addend’
                            1. NYD1R2 ‘‘rendering’ ‘anew’’ ‘‘addend’
                            2. NYCTC2 from #NX6GD1
                            3. NYCVD0 review
                              1. NYCVDZ I like it.
                              2. NYCVWW If it works, popularizing it could make a big difference due to #NYCVVH
                              3. NYCU33 meets goals except ‘notable pros thru cons’
                                1. NYCUMS has nice mnemonic: ‘addend’ is “the end” (last) of the 2 things summed’ –my idea & phrasing
                                2. NYCU5M #NYCTIQ there but weak
                                3. NYCU4E sometimes defined without regard to side of sum
                                4. NYCU3Z unfamiliar to most everyone, but that can be ok.
                          3. NYDP1B ‘extension’
                          4. NX5Z4J #NX5Z4J(‘delta’): ‘delta’
                            1. NX5ZAA per use
                            2. NYCRFX def
                              1. NYCROP except ‘versions of a file’ should be ‘item specifying the changes to cause one to become the other’
                              2. NYCREN
                              3. NYCRI6 except ‘finite’ seems too limiting.
                            3. NYD0N9 review
                              1. NYCT04 meets goals except ‘notable pros thru cons’
                                1. NYD0VK #NYCTI3(‘direction’) doesn’t feel full but pretty strong
                                2. NYD0ZE #NYCTH9(‘adding focus’) about 50% as ‘delta’ word still brings up strong images of subtraction at least how I learned it.
                                3. NYCT0L seems unfamiliar to all except techies. –con
                                  1. NX5ZR2 aka feels limited to common mathematical types per usage there, where it’s ~95% used
                          5. NYCT3L ‘diff’
                            1. NYD11G review
                              1. NYD11R still rank after #NX5Z4J(‘delta’)
                              2. NYCUPV same as for ‘difference’ except:
                                1. NYCUA1 especially short & familiar –pro
                          6. NX5Z4A ‘difference’
                            1. NX5ZPO meets goals except ‘notable pros thru cons’
                              1. NYCUFM #NYCTI3(‘direction’) weak; sometimes suggests absolute value of subtraction.
                              2. NYCUB1 fails #NYCTH9 –notably bad
                          7. NYDOPH ‘increment’
                            1. NYDOVY meets goals except ‘notable pros thru cons’
                              1. NYDOWD #NYDORX(‘any size’) fails as notably suggests small.
                              2. NYDOZX semi-familiar
                          8. NYCSLV #NYCSLV(‘offset’): offset’
                            1. NYCZID definition anew
                              1. NYCSKY def:
                              2. NYCZHU more possibilities at
                            2. NYCSO2 meets goals except ‘notable pros thru cons’
                              1. NYCZO1 #NYCTI3(‘direction’) weak; not clear operand order without extra words as ‘b offset ahead of a by x’  –notable con
                              2. NYCSP1 has typically has incorrect additional meanings of 1 of ‘A short distance’ + ‘out of line’ + ‘ diminishes or balances the effect of a contrary’  –serious con
                              3. NYDOYK #NYDORX(‘any size’) fails as strongly suggests very small –serious con
                          9. NYCSEO ‘offset amount’  –now factored out of #NX5Z4A
                            1. NYCSMJ same as NYCSLV(offset) except doesn’t confuse for verb but  ~3x longer.
                          10. NX5Z5Hpatch
                            1. NX5Z6M per use in #NX5XDQ
                            2. NX5ZJQ meets goals except ‘notable pros thru cons’
                              1. NYD1AH suggests the source/original/from is broken/leaking –con
                              2. NX5ZQJ not familiar except in software and {in certain contexts as programmers, since most instead call these ‘updates’}
                              3. NX5ZKO #NYCZWA(‘number operands’): not all, so not suitable for several contexts –notable con
                                1. NX5ZMF for instance, ‘3 hour duration’ could not well be called a ‘3 hour patch’
                          11. NYCSFH ‘portion’  –now factored out of #NX5Z4A
                            1. NYCSSI ‘notable pros thru cons’
                              1. NYCSW2 speaks no size –con
                              2. NYCSTZ speaks no end points –con
                              3. NYD0TW NYCZWA(‘number operands’): fails
                              4. NYCST3   #NYCTI3(‘direction’): none –big con
                2. NX5M51 domain
          2. NYG158 binary endofunction + maybe additional arg(s) :NYG158
            1. NZ1A66 ‘‘‘Pretty Link’ entry’ ‘anew’’ section 1st
            2. NYG19F compared et al
              1. NX5CAK ‘-’  ‘‘compared to’
                1. NX5G6B ‘‘definition’ ‘anew’’
                  1. NX5DN6 syntax: x operator y (x-y)
                  2. NX5CLO for the immediate LHS via the immediate RHS
                  3. NX5DIX compares
                    1. NX5DL7 where just as in English, ‘this’ and the immediate subject refers to the LHS and ‘that’ refers to the RHS
                  4. NZ1DMM ‘should pick first the suspected better of the two’
                    1. NZ1EFD ‘notable pros thru cons:’
                      1. NZ1ENT as an arbitrator, keeps the comparison in a standard place (unless the winner is debatable) so
                        1. NZ1EP6 avoids maintenance & clutter problems with having it two places
                        2. NZ1EPT allows readers to quickly know where to look for it.
                      2. NZ1EGG puts the comparison details in the better of the two, so
                        1. NZ1EKB showing it has been well compared (more important than showing a less-likely-to-be-used has)
                        2. NZ1EKI keeping the comparison details where they will most likely be updated
                      3. NZ1ERO when which is better is unknown or (worst) debatable, not well defined
                        1. NZ1ESG though that seems no worse the other common situations, such as for ‘‘anew’’ lists, when its unclear which should be first, which seem about just as common as this uncertainty.
                    2. NZ1E59 ‘motivations & sources & changes ‘in reverse start order’’ /5156#NYYNST
                2. NX5DQ2 ‘per def’
                  1. NX5DTV ‘notable pros thru cons’
                    1. NX5DWJ does not dictate order of compared elements so fails to reach canonical form –con
                  2. NX5DR2 ‘same or similar’ ‘sub’
                    1. NX5DS5 >0 in function
                      1. NX5DV3‘sub’
                3. NX75OM ‘compared to’
                  1. NX75P1‘in comparison to’
                    1. NX75PK created as searched for that but couldn’t find it
                    2. NX75PY now found that
                    3. NX75QA merging: TBA
                4. NX5CL3 ‘‘name’ ‘anew’’
                  1. NX5CDR ‘compared to’
                    1. NX5CE0 used 1st ~9x /5129#NOOO8N thru /5129#NWW6T8
                    2. NX5DYY ‘‘rendering’ ‘anew’’ ‘‘compared to’
                5. NX5E0Z ‘‘‘Pretty Link’ entry’ ‘anew’’ 1st
              2. NWWOPP ‘-’‘in comparison to’
                1. NWWOTU ‘‘name’ ‘anew’’
                  1. NWWOUD ‘in comparison to’
                    1. NWWOV8 ‘‘rendering’ ‘anew’’
                      1. NWWOVW‘in comparison to’
                2. NWWOXV ‘‘‘Pretty Link’ entry’ ‘anew’’
                  1. NWWOYA 1st
                3. NWWP41 ‘notable pros thru cons’
                  1. NWWP4E powerful & natural
                  2. NWWP51 2 ways to organize arguments: LHS & RHS can be flipped, with no clear resolution mechanism, creating regularly problematic redundancy
            3. NYQZXN textual diff
              1. NZ24S9 .. ‘Wikipedia’ {for at least files}
              2. NYQZYV block move {detecting so reporting ideally including diffing} :NYQZYV
                1. NYR0D3  :NYR0D3
                  1. NYR0DP #NYR0AG answer 2255628
                  2. NYR0IK ‘usage’
                    1. NYR0IS 1st: just now comparing /5138#NWYUYU with what turned out to be a slightly earlier version in an MS ExWeb buffer: perfectly identified all the moved blocks that {had messed up kdiff3 so caused me to look and find this tool as detailed}.
                    2. NYR0T4 If one’s practice is to not significantly, delete text, just as most move it, to detect text loss, simply search the for the {yellow aka deleted} to see if it’s acceptable
                  3. NZ2502 as distributed via web page, for backup, is of execution*/ & of source*/
                2. NYR0AG
                  1. NYR0BQ NYR00N find 1
                3. NYR00N
                4. NZ155Y ‘‘name’ ‘anew’’
                  1. NZ1575 present
                  2. NZ1569 ‘minimizing block moves’ –originally until just now
              3. NZ10NG Note every moved block/content normally is a big problem, specifically :NZ10NG
                1. NZ12P3 for a few smart diff programs with ‘block move {detecting so reporting ideally including diffing} :NYQZYV’ (see that), it feels
                  1. NZ17GE getting the text for diffing into these programs can be a notable problem
                    1. NZ17IB notably in default WordPress, prior version content is only displayed as a column in the table (plus with additional tag closures for every row of it but diff isn’t thrown by these), so getting that text requires 1 or more:
                      1. NZ17O4 copying the source into a program as MS ExWeb able to select & extract the single column
                      2. NZ17PQ using (so finding & obtaining) a JavaScript applet or extension to copy the column out (to say the clipboard)
                      3. NZ17RF obtaining & using a WordPress program for displaying (so obtaining in normal form) prior versions, as ‘NUZCRK .. ’ from ‘WordPress plugins NMMDBV’, though such could make privacy violations.
                2. NZ10O6 cause WordPress, kdiff3, and other standard diff programs to have their diff corrupted…
                  1. NZ1112 for all the content moved (including move not visible) plus regularly significant content near the moving
                    1. NZ124B specifically almost creates a confusing useless diff, suggesting dramatically more changes (adds and deletes) than actual, plus no obvious moves, for {any block which has moved plus the areas around where the block was (from) & now is (to)}
                    2. NZ11DG as instead each distinct block moved is almost always marked as deletion and insertion of two separate blocks,
                      1. NZ117Z specifically, if n distinct moves take place, at best only the largest block within the move region (which then typically is something which didn’t move) will be diff.
                      2. NZ11WD and then the diff program…
                        1. NZ11CG doesn’t (recursively) check how much so recognize insert/delete pair is significantly the same text (so really a move)
                          1. NZ11KB so a human must inserts & deletes which are move, and manually diff them, which highly often impractically time-consuming & error prone
                            1. NZ113P so on practice, diffs within moved blocks are not detected
                        2. NZ122S but does even more strongly try to mis-unify the moved block with the content near the move’s From & To locations, sometimes if not regularly messing up the diff for those areas.
                  2. NZ15KB so
                    1. NZ15GK for significant moves, right before & after require saving a revision
                      1. NZ15NL as while the moves still won’t be detectable by the diff rather will be a mess, at least then they won’t mess up the other diffs that the diff program can well detect :NZ15NL
                    2. NZ15KV {collect several moves all {within 1 doc xor to another doc}, plus a tiny more, and simultaneously do them at once (between these saves)}
                      1. NZ160V including for content which is moved, also do any renesting/sub-reordering it might need
                      2. NZ16AX NZ16AX: where ‘a tiny more’ is
                        1. NZ16XS pretty limited & confusing, specifically :NZ16XS
                          1. NZ16BS if moving from one doc to other(s), to not moved text…
                            1. NZ16JE in source doc, rewriting & inserts can be done
                              1. NZ16TA but not deletes, as from the resulting diff, those will be indistinguishable so readily confused with (the deletes from) the text being moved out.
                            2. NZ16LA in the target doc(s), rewriting & (responsible) deletes can be done,
                              1. NZ16UH but not inserts as from the resulting diff, those will be indistinguishable so readily confused with (the inserts from) the text being moved in.
                      3. NZ15WW ‘notable pros thru cons’
                        1. NZ15XE so much better not degrading other diffing per NZ15NL
                        2. NZ15Y3 spreads the costs & disruption of the 2 revision saves.
                        3. NZ1601 still very annoying as only a semi-big group occurs naturally including during the move, one spots edits & additions needing made but…
                        4. NZ171V additional edits ‘pretty limited & confusing, specifically :NZ16XS’, causing mistakes & frustration.
                    3. NZ1732 workarounds especially those mentioned by sibling points, are not as smoothly & probably completely but more in-practice, covered by ‘steps in order :NVSX4L’ especially search there for ‘diff’.
                      1. NZ17D3 –these 2 passages could use some syncing & merging.
          3. NYFJBP ‘binary endorelation’ + maybe additional arg(s)
            1. remaining sections
            2. NWXX1F ‘-’ ‘‘sub’
              1. NWYSMS executive summary:
                1. NWYRY2 a ‘binary endorelation’ specifier & operator which is near-maximally {simple & universal} + weight-able + composable
              2. NWXYW2 ‘‘definition’ ‘anew’’
                1. NX3GCN of syntax is
                  1. NWXY1I‘sub’(?<whitespace>..)(?<NX3FLO>..)’
                2. NX3G62 of semantics is
                  1. NWY1FF the RHS relation is
                    1. NWY201 {the {reflexive- + symmetric-‘transitive closure’} of the LHS relation} where (so limited to ) ..
                      1. NWY1ZA elements are related iff they are NX3FLO {directed distance, specifically directed path weight of ‘weighted graph’ choosing shortest path per graph distance} in {a (‘the’ if no cycles) ‘transitive reduction’ of the LHR relation}
                    2. NWY3G2 –this condition
                      1. NWY3I5 feels right else near right still recommend relying on the example usages.
                      2. NWY3K8 is notably complex
                        1. NWY3RH but still probably near as simple as it can be
                        2. NWY3OA so, for seemingly all humans, dramatically better to first look example usages to infer the definition
                  2. NX3FLO directed weight/distance variable NX3FLO
                    1. NWXY3U specifies certain directed distance
                      1. NWXY8L where
                        1. NX58PU near 0
                          1. NX58RL means near identical so very similar
                          2. NWXY9F 0
                            1. NX58X4 means
                              1. NX58Y1 describing the same thing
                              2. NX58XI self
                                1. NX58YT ‘replacement’ #NX58Y1; started at #NWXY9F
                            2. NWXYB3 specifies an equivalence relation
                        2. NX1TJS negative-positive respectively
                          1. NWXYD1 specifies a relation of items of 1 or more of
                            1. NX5955 earlier/older-later/newer (as in time & more), so
                              1. NWXYEI predecessor-successor
                              2. NWXYF2 ancestor-{descendant specifically lineal descendant}
                            2. NX5985 bigger-smaller especially in so far potential effect/significance, so
                              1. NX59H3 big-endian-ish
                            3. NWXYHX super-sub including (with quotes from is-a)
                              1. NWXYLHhypernymhyponym (supertype-subtype) relations between types (classes) defining a taxonomic hierarchy’
                              2. NWXZ3Bholonymmeronym (whole/entity/container-part/constituent/member) relations between types (classes) defining a possessive hierarchy..’
                              3. NWXZ3N not ‘concept-object (type-token) relations between types (classes) and objects (instances)’  as that is better handled by {‘1’ and equivalent}
                          2. NX1TO5 per #NWXYD1
                            1. NX1TIN <0 vs. >0
                              1. NX1V27 normally get additional values not here restated as implied ‘‘per def’’ from
                                1. NX1TSE in the definition itself notably to the degree the it is defined in terms of ‘and’ vs. ‘or’ respectively
                                2. NX1V3L in these ‘‘per def’’ declarations
                    2. NX3FSG is of type
                      1. NWXY2A a {set aka range(s)/interval(s)} of
                        1. NWY47L integers
                          1. NWY48O in the most common uses
                        2. NWY45U real numbers
                          1. NWY46U this else (other type options as integers) would be notably used for ‘weighted graph’ notably #NX0C31
                        3. NWY495 imaginary numbers
                          1. NWY4AN in no use I can think so far so seems for now this possibility can be skipped
              3. NWYCTI ‘per def’
                1. NWYS8L composing
                  1. NWYSA2 operator can be meaningfully composed
                  2. NWYCU3‘sub’ a ‘sub’ b’ = ‘‘sub’ (ab)’
                    1. NWYDNR ‘notable pros thru cons’
                      1. NWYDOC allows for compact & organized specification by, in a specification for an item such as a category, placing a related item down further in the specification outline according to the degree the relationship is known
                        1. NWYDSB example more TBA
                        2. NX4CRT example for ‘US.CA.OC {Section 8 aka HCV} NWOLZG’
                          1. NX4CYI is the immediate parent ‘US {Section 8 (housing) aka HCV(Housing Choice Voucher)} NWNP5X’, or is there up to about 2 intermediaries where 1 could reasonably be ‘US.CA {Section 8 aka HCV’ if such exists}?
                            1. NX4EPM here we represent that by say ‘‘same or similar’ ‘sub’ <0 ‘sub’ {<=-1 >-3~} ‘US {Section 8 (housing) aka HCV(Housing Choice Voucher)} NWNP5X’
                              1. NX4EXY where the sub portion simplifies to ‘‘sub’ {<=-1 >-3}’ (per #NWYCU3)
                                1. NX4F75 which can be done if desired, but sometimes it might not be, as say if we want file this under all the other ‘<0’ situations
                              2. NX4EZK where when the real distance is found, say it’s -3, (per #NWYCU3) it can be merged in with existing facts with no info conflict.
                2. NX1ER4 ordering defined without {any underlying definition in terms of some other related domain as  ‘A ⊆ B is represented as: ∀x{x∈A → x∈B}.[1]’}
                  1. NX1EYN for certain common domains
                    1. NX1EZN as category & perhaps class
                    2. NX1F3R appears the norm
                3. NWY6L8 ‘notable pros thru cons’
                  1. NWYTB5 can specify any ‘weighted graph’
                    1. NX03AL see definition especially #NWY46U
                  2. NWY6QC simply generalizes & unifies  many common ‘weighted graph’ relationships
                    1. NX1NRAhuge pro
                    2. NX1NLS including for partial order
                      1. NWY6RR including equivalences, super- & sub- with & w/o equality, ‘transitive reduction’,
                      2. NX1NM0 see examples in when combined with domain factoring
                  3. NWY6NN factors out the specific domain being studied rather than including it
                    1. NX1MXG as needed so appropriate per good knowledge factoring
                      1. NX1F5U so a big pro
                    2. NX1FD5 by design
                    3. NX1F70 which is seemingly unheard of outside of mathematics, as
                      1. NX1FBK for common reflexive partial orders and common total orders, the typical ‘operator’s implicitly tell the domain fairly (too) specifically
                        1. NX1FFD both in phrasing via
                          1. NX1FGC special symbols as notable examples:
                            1. NX1FH8 use of any of ‘{<, >, ≤, ≥}’ (quoted from current strict total order) tells the domain is partial ordered (per choice of symbols here), especially  ‘total order’ed, especially of Number
                            2. NX1LRL use of any of {‘’ ‘‘ ‘’ ‘’} (quoted from ‘sub’ equivalences) tells the domain is typically a set or class
                          2. NX1LCZ in natural-language words, as notable examples:
                            1. NX1LDW RegExp ‘(sub|super)(set|class|type)’, not just ‘sub|super’ as ‘sub’ does
                            2. NX1LGA RegExp ‘((great)*grand){0,1}((parent|(mother|father))|(child|kid|(son|daughter))|..)’, not just ~‘((great)*grand){0,1}’ as ‘‘sub’ n’ does
                            3. NX1LW8 Wikipedia (& seemingly more) choosing primary subject name ‘partially ordered set not just, ‘partial order’ or ‘partial ordering’ which is the real focus.
                        2. NX1MWX which reverses good knowledge factoring, resulting in {operators & other functions plus domains} which are too many & unified, fixed by ‘sub’
                    4. NWY6P6 which could be ‘parenting’ or super/sub class or type, or containment, or more
                  4. NWY6M0 due to #NWY6NN & #NWY6QC, covers & unifies many common ‘operator’s and conceptually unifies many common domains
                    1. NWYSQW particularly for common reflexive partial orders
                      1. NWYC12 notable examples:
                        1. NWY6X1 for social including biological parenting,
                          1. NWYC8U a significant portion of relationships within Immediate family & Extended family is much more simply expressible, specifically:
                            1. NWYB81child ‘sub’ >0’ = ‘ lineal descendant
                            2. NWY6YYchild ‘sub’  n’ = ‘(great){n-2}grandchild’ for n>=2
                            3. NWY6Y9child ‘sub’  1’ = ‘child
                            4. NWY6ZNchild ‘sub’  0’ = ‘self
                            5. NWY70Bchild ‘sub’ -1′ — ‘parent
                            6. NWYBG6child ‘sub’ -n’ — ‘(great){n-2}grandparent’ for n>=2
                            7. NWYBW9child ‘sub’ <0′ — ‘ancestor
                          2. NWYC99 a number of interesting equivalencies are possible, which can every be used to define certain key terms, as:
                            1. NWYCAE those just given
                            2. NWYCBWparent ‘sub’ -1’ = ‘child
                            3. NWYCG9grandchild ‘sub’ -1’ = ‘grandparent
                            4. NWYCIL more
                        2. NWYC45 for sets (quoting symbols),
                          1. NWYD0Csubset ‘sub’ >0’ = ‘
                          2. NWYC7Tsubset ‘sub’ ≥0’ = ‘
                          3. NWYD2Lsubset ‘sub’   0’ = ‘=’
                          4. NWYD90subset ‘sub’ ≤0’ = ‘
                          5. NWYDD5subset ‘sub’ <0’ = ‘
                          6. TBA   ‘US HUD-VASH(United States Department of Housing and Urban Development and Veterans Administration’s Supported Housing Program) NT6TFY’
                        3. NWYGDS NOLDef equivalences, especially replacing prior phrasings, as …
                          1. NX0VO5 #NWYGDH(for ‘entry’)
                          2. NX05EW #NX04PT(for ’immediate’)
                          3. more TBA
                4.    ‘same or similar’ ‘sub’
                  1.   <0
                  2.   0
                  3.   <0 common ‘1’
              4. NWXX9V ‘‘name’ ‘anew’’
                1. NWY2S2 ‘sub’
                  1. NWY2SG as in ‘sub-’ vs. ‘super-’
                  2. NWY53R ‘notable pros thru cons’
                    1. NWY51D well passes {can Mom get it by a few examples} –notable pro
                    2. NWY503 short & cute & familiar –pro
                    3. NWY50F ambiguous enough alone that new meanings can be attached –pro
                    4. NWY52Z directional –mostly pro
                  3. NWY54I like it at rank 1 of 6
                    1. NWY6F6 for reasons so far mentioned & perhaps more
                  4. NWYDU9 ‘‘rendering’ ‘anew’’
                    1. NWYEA3‘sub’
                    2. NWYE1B‘sub:’’  –not per #NWYE5Q
                2. NWYDX8 be appended with ‘:’ to indicate it is immediately followed by a particular value
                  1. NWYE5Q as this seemed to only add clutter, now decided against this.
                3. NWXY0C ‘next’
                  1. NWXY0O as in ‘next’ vs. ‘previous’
                  2. NWY6AV ‘notable pros thru cons’
                    1. NWY6A8 short & familiar –pro
                    2. NWY6BA time implication a bit strong –mixed
                    3. NWY6CJ‘replacement’’  overtone –tad con
                  3. NWY6FO now like it at rank 2 of 6
                4. NWXXA8 ‘grand’
                  1. NWXXBA where ‘grand’ as in RegExp ‘(great)*grandparent|(great)*grandchild’ except not just for biological/social parenting.
                  2. NWY2U7 ‘notable pros thru cons’
                    1. NWY2ZV a usage which is
                      1. NWY31P very familiar –notable pro
                      2. NWY31Y is first used at level 2+ not level 1+ –small con
                    2. NWY2UO notably natural as far as {sup/sub direction –another usage}
                      1. NWY2Y6 MIXED: impartial so pro but also confusing so con.
                    3. NWY5IJ use here sounds a tad awkward
                  3. NWY6I3 now like it rank 3 of 6
                5. NWXXXR ‘immediate’
                  1. NWY5BW ‘notable pros thru cons’
                    1. NWY5CO strong logical tie-in with #NWXPBQ: ‘-’ ‘immediate’ –pro
                    2. NWY5FX use here sounds awkward –con
                  2. NWY6IV now like it rank 4 of 6
                6. NWXXX8 ‘cessor’
                  1. NWY374 as a generalization of #NWY365: ‘successor’
                  2. NWY55L ‘notable pros thru cons’
                    1. NWY56G semi-short –neutral
                    2. NWY56W has no useful immediate meaning on itself, including could also be short for unrelated as ‘accessor’ –con
                  3. NWY6JF now like it rank 4 of 6
                7. NWY365 ‘successor’
                  1. NWXXZ9 as in ‘predecessor’ and especially ‘successor’
                  2. NWY4TM ‘notable pros thru cons’
                    1. NWY4WF direction clear –pro mostly
                    2. NWY4WP strong {we’re replacing} overtone, which is inaccurate  –notable con
                    3. NWY4UM 3 syllables so a bit verbose –con
                  3. NWY6K0 now like it at rank 6 of 6
              5. NWYEUG ‘‘‘Pretty Link’ entry’ ‘anew’’
                1. NWYEUP 1st
            3. NWX5VK ‘-’ ‘parent class’
              1. NX059T ‘‘name’ ‘anew’’
                1. NWX7SM ‘parent class’
              2. NWX8D3 ‘‘definition’ ‘anew’’
                1. NWX6ZE every value at any given time
                  1. NWX737 is ideally a ‘‘rendering’ that time
                2. NWXRJN where ‘parent’ here is
                  1. NWX7TP per the usage in
                    1. NWXRKF so a case of meaning ‘a source or origin of a smaller or less important part.’ from”parent” which is currently apparently quoting
                  2. NWXRK5 NOT the biological usage
                3. NWX7V9 where ‘class’ is 1 or more of:
                  1. NWX82G
                  2. NWX832
                  3. NWX8AK somewhat
                4. NWX73M a ‘binary endorelation’ with properties
                  1. NWX74W anti-transitive
                  2. NX08X8 is a
                  3. NWX78K acyclic as from and {as in}
                    1. NWX7EP including {anti-reflexive per}
            4. NWXPXY ‘-’   ‘‘subclass’
              1. NWXQ4P ‘‘name’ ‘anew’’
                1. NWXQ0S ‘subclass’
                  1. NWXQ4X ‘‘rendering’ ‘anew’’
                    1. NWXQ5A‘subclass’
              2. NWXQ2Z ‘‘definition’ ‘anew’’
                1. NWXPHQ the  RHS is a {sub or equal} class of the LHS
                2. NWXPPN reflexive?
                  1. NWXPR4 so far undecided
              3. NX04HI using/usage
                1. NX04HX in ‘‘‘definition’ ‘anew’’’ –what it was invented for
        3. NYFJ9O quantity-ish
          1. remaining sections
          2. NWXOM1 ‘-’  ‘‘1’
            1. NWXP2C ‘‘name’ ‘anew’’
              1. NWXOWA ‘1’
                1. NWXP1N ‘‘rendering’ ‘anew’’
                  1. NWXZ5X‘1’
              2. NWXOVV ‘individual’
              3. NWXOU6 ‘qty 1’
            2. NWXP0M ‘‘definition’ ‘anew’’
              1. NWXOY7 the RHS is a size/cardinality 1
              2. NWXQ9Q‘subclass’’ applies
            3. NWYF7E ‘‘‘Pretty Link’ entry’ ‘anew’’
              1. NWYFBO 1st
        4. NYFJFV distance-ish
          1. remaining sections
          2. NWXPBQ ‘-’ ‘immediate’
            1. NX04KB usage/occurrence/using
              1. NX053D instead use sub form  –due to #NX04V6
              2. NX04L7 to be preceded by a situation of {‘‘sub’ <0’ or/and ‘‘sub’ >0’} in to filter/refine that per its def
            2. NX04V6 ‘notable pros thru cons’
              1. NX04VN familiar –pro
              2. NX04WP  sub form seems always better once that syntax is understood –huge con
            3. NWXQBW ‘‘definition’ ‘anew’’
              1. NX04PT should be equivalent to ‘‘sub’ {-1,1}’   —ref to here for ‘sub’
                1. NX04YQ indeed seems in common cases, equivalent to ‘‘sub’ -1’ or ‘‘sub’ 1’ where the choice is generally obvious
              2. NWXQTA RHS’s relation is a ‘transitive reduction’ of the LHS relation
              3. NWXRFC as in ‘immediate ancestor’ or ‘immediate predecessor’
                1. NWXT7P so meaning ‘2. nearest in time, relationship, or rank.’ quoting from”immediate” apparently currently quoting from oxford meaning
            4. NWXPF8 ‘‘name’ ‘anew’’
              1. NWXPDV ‘immediate’
    3. NYFIZP‘evaluate’
      1. NYR3EY ‘completeness stage’ experimental.
      2. NYR3GL ‘‘definition’ ‘anew’’
        1. NYR6TK so far #NYQMO4 takes precedence.
        2. NYR3GX the result or process of respectively ‘compare’ing an item’s aspect(s) against those of another item, often a standard item.
          1. NYR43P for subject s, standard std, and each aspect s, the result/process of determining ax where {(a(std) adder ax) equals a(s)}
      3. NYQN2W ‘name anew’
        1. NYR8JI ‘measure’
        2. NYQN3X ‘evaluate’ :NYQN3X
          1. NYR6QT ‘rendering anew’ ‘‘evaluate’
          2. NYR8L2 ‘per def’
            1. NYR8LK judgmental
        3. NYQN3M ‘review’
          1. NYR6OB ‘replacement’  ‘‘evaluate’ :NYQN3X’ per #NYR6K8
          2. NYR6J1 aspect #NYR6HT review
            1. NYR6K8 for basics as this, overspecifying –con
            2. NYR235 often the case, so pro
          3. NYR6GM ‘per def’
            1. NYR6HT #NYR6HT‘with the possibility or intention of instituting change if necessary’ says Oxford
            2. NYR281 ‘same or similar’ ‘sub <0 ‘1’ ‘evaluate’ notably NYQN3X
      4. NYPAKF ‘‘‘Pretty Link’ entry’ ‘anew’’  section 1st
      5. remaining sections
      6. NYR4GE uni/multi aspect
        1. NYR4HE uni aspect
          1. NYDNSD ‘-’ ‘‘place’’ details
            1. ‘completeness stage’
            2. NYQPWD ‘usage’
              1. ‘in order’
              2. NYQOP2 NYQOP2: expected
                1. NYQOPR major due especially to NYQPDI
            3. NYDN76 ‘‘definition’ ‘anew’’
              1. NYR891 answers ‘Where the subject?’
              2. NYDNEP taking the subject as ‘ToPt’, specifies 0 or more of  {1st ‘addend’, 2nd ‘adder’, and 3rd ‘FrPt’, where all but 1st may be defaulted}  —KEY
                1. NYDQ2F –use of ‘adding’ is
                  1. NYDS0F a major if not the top use of  ‘adding’ in reality
                    1. NYDQ3H which seems people don’t see at least not immediately & directly
                      1. NYDRWN so defining in this way seems a major improvement
                        1. NYDSGH Indeed, without this, Oxford gets it wrong
            4. NYE3IO ‘per def’
              1. NYPHM2 question form
                1. NYPHMA ‘where’ aka ‘what place’
              2. NYQOUY as a specifier,
                1. NYQQW8 of default
                  1. NYQQWW can be done by placing it 1st
                    1. NYQQXK –note here inspired by case ‘NYQQBA: the default’
                2. NYQPN0 provides a standard for specifying
                3. NYQOVC NYQOVC: allows reasoning & history (for an item’s placement) to be attached it, including…
                  1. NYQPBO indirectly so then also
                    1. NYQPAH applies to all its instances, not just to itself notably where it’s defined
                      1. NYQPDI NYQPDI: doesn’t clutter up the instances or even the template for them with their placement details
                  2. NYQPMK directly
              3. NYE3ID ‘same or similar’ ‘sub’
                1. NYE3I5 -1 ‘1’  ‘dimensions, 0 or more NME6CK
                2. 0
                  1. NYE3OL ‘Wikipedia’ currently none closest; closest is NYE3U4(‘location (geography)’) which is not NYDWMK(spacetime independent).
                  2. NYE3P6 ‘maker’ ‘‘place’
                3. NYE3SI 1 (on this site) ‘1’
                  1. NYE3SZURL LGYMHK
                  2. NYE3U4location (geography) NME7SB
              4. NYQOZD ‘compared to’  {placing items in a particular arrangement to explain the arrangement} ‘notable pros thru cons’
                1. NYQP7ENYQOVC: allows reasoning & history (for an item’s placement) to be attached it, including…’
            5. ‘‘motivation or source or change’ ‘in reverse start order’’
            6. NYDNTR ‘‘name’ ‘anew’’
              1. NYDO7S all ‘‘rendering’ ‘anew’’: see category rendering
              2. NYDTGO NYDTGO(‘goal’): name qualities from most preferred roughly:
                1. NYDVUK standard name virtues ‘NXNaGo’ (as normal, some but not all are top here)
                2. NYDTJD #NYDNEP
                3. NYDTY0 readily but not necessarily cover the subject’s
                  1. NYDWMK NYDWMK(spacetime independent): both in or/and out of ‘spacetime NME6MG
                  2. NYDU0G with regard to other object(s) as reference point(s) which…
                    1. NYDU4C NYDU4C(‘relative’): could be any: called specifying ‘relatively’ & ‘relative’ position/place/etc
                    2. NYDU6S NYDU6S(‘absolute’): are standards so generally fixed & universal, called specifying ‘absolutely’ & ‘absolute’ position/place/etc
                    3. NYDU9T for example, see the choices for
                  3. NYDUE9 NYDUE9(‘orientation’): orientation
                  4. NYDTZM NYDTZM(‘area’): area/boundary so size
              3. NYE2R8 ‘place’
                1. NYE2RT from
                  1. NYE2W2 no need to include other variants as ‘place/region/location/..’ as the are generally subsets so {can and better} be defined as subcategories which recommend this one in general.
                  2. NYE2VU NYDSJU(‘place’) ranking 1st as of ~2hr ago.
              4. NYDO7F ‘location/position’
              5. NYDOH8 ‘location or/and position’
              6. NYDMJ6 ‘location (position)’ ‘‘rendering’ ‘anew’’  ‘‘location (position) NQ8DU1’’ –starting at time of name’s id
              7. NYDNAT common names {position, location, & similar}
                1. NYDNDS commonality
                  1. NYDTRE have the intended meaning but each with restrictions
                  2. NYDSDS major (by Oxford) defs {#NYCJJJ, #NYDSEW, NYDSJU(‘place’)} define in terms of each other (circular def) plus {#NYDSSU(‘point in space’) which it doesn’t define}, so, for this core meaning, except for identifying 4 near-or-exact synonyms, really defines nothing.
                  3. NYDTC1 sheds some light but is informal, incomplete, and apparently just one person’s quick response
                2. NYDSJU NYDSJU(‘place’): ‘place’
                  1. NYDWDP meets NYDTGO(‘goal’) except ‘notable pros thru cons’
                    1. NYDWEK NYDUE9(‘orientation’) offered weakly –somewhat bad
                  2. NYDSKY
                    1. NYDSOO –defines in terms of #NYDMRG(‘position’) and  #NYDSSU(‘point in space’)
                3. NYDWYI ‘region’
                  1. NYDX18 meets NYDTGO(‘goal’) except ‘notable pros thru cons’
                    1. NYDX2F NYDUE9(‘orientation’) not offered –bad
                  2. NYDWYU now my fix of NYDWT3(‘region of graph’)
                4. NYDMQI #NYDMQI(‘location’): ‘location’
                  1. NYDMWZ meets NYDTGO(‘goal’) except ‘notable pros thru cons’
                    1. NYDN5P NYDU6S(‘absolute’) –mildly favored –tiny bad
                    2. NYDMUW NYDUE9(‘orientation’) not offered –bad
                  2. NYCJ9Z meanings 2 so including 5 –starting at time of name’s id
                  3. NYCJJJ
                    1. NYDSRQ defines in terms of  #NYDSJU(‘place’) & #NYDMRG(‘position’)
                5. NYDMRG NYDMRG(‘position’): ‘position’
                  1. NYDMUF meets NYDTGO(‘goal’) except ‘notable pros thru cons’
                    1. NYDMZ9 NYDU4C(‘relative’), especially nearby, favored –a somewhat bad
                    2. NYDMVZ NYDTZM(‘area’) not specified –bad
                  2. NYDSEW
                    1. NYDSQ0 defines in terms of  #NYDSJU(‘place’) & #NYDMQI(‘location’)
                6. NYDSSU NYDSSU(‘point in space’): ‘point in space’
                  1. NYDWJQ meets NYDTGO(‘goal’) except ‘notable pros thru cons’
                    1. NYDWLP fails  NYDWMK(spacetime independent) as being in it –bad
                    2. NYDWKP NYDTZM(‘area’) limited to 0 –very bad
                  2. NYDT2O gives ‘No exact match found’
                7. NYDWT3 NYDWT3(‘region of graph’): region of graph’
                  1. NYDWU7 meets NYDTGO(‘goal’) except ‘notable pros thru cons’
                    1. NYDWUQ very unfamiliar (except to those well appreciating graph theory, that a graph could map seemingly anything) –huge con
                  2. NYDWWS as of 2 min ago, my fix of NYDSSU(‘point in space’)
            7. NYPHVD ‘‘‘Pretty Link’ entry’ ‘anew’’ section 1st
            8. remaining sections
              1. NYPFDP ‘-’  ‘‘display place’
                1. ‘replacement’
                2. ‘completeness stage’
                3. NYCCWC ‘usage’
                  1. ‘in order’
                  2. NYCCZQ like many a position, specification
                    1. NYCCWU best relatively
                      1. NYCD56 as the number of siblings can 1 or more: change, be unknown, have unknown position
                      2. NYCD4J to what would be
                        1. NYCCYI nearest
                        2. NYCCYO before or after
                          1. NYCCYZ choosing one consistently
                            1. NYCD2A can be a good idea as suggests a canonical form
                4. NYCCVG ‘‘definition’ ‘anew’’
                  1. NYCCW0 for an ‘outline (list) NQVTOY’ of items, specifies {where aka  the ‘place’} in the outline
                    1. NYQOM4 NYQOM4: so for the items of {‘(NOLDef) template :NXK3IQ’, foremost ‘per se :NXK3MU’}, specifies the subject’s {order specifically placement} within that outline.
                5. NYQOMX ‘‘motivation or source or change’ ‘in reverse start order’’  NYQOM4
                6. NYPHPR ‘name anew’
                  1. NYPHS2 ‘display ‘place’
                    1. NYPI0F ‘rendering anew’ ‘‘display place’
                  2. NYPHQ2 ‘display position’ –starting at time of about #NYCCWC
          2. NYFIVE ‘-’ ‘explain’
            1. NYR7BT ‘completeness stage’ experimental
            2. ‘‘‘Pretty Link’ entry’ ‘anew’’ section 1st
            3. remaining sections
            4. NZ1CIW ‘-’ type
              1. ‘‘definition’ ‘anew’’
              2. NZ1CNI ‘motivations & sources & changes ‘in reverse start order’’ tofile /5156#NYY7Y7
              3. remaining sections
              4. NZ1DB2 ‘-’ algorithm/method/strategy
                1. ‘‘definition’ ‘anew’’
                2. NZ1DDW ‘motivations & sources & changes ‘in reverse start order’’ tofile /5156#NYYBH6
                3. remaining sections
                4. NZ1DG8 ‘-’ representation
                  1. ‘‘definition’ ‘anew’’
                  2. NZ1DGV ‘motivations & sources & changes ‘in reverse start order’’ tofile /5156#NYYBN3
                  3. remaining sections
              5. NX5E7A ‘-’‘usage’
                1. NX579W ‘‘definition’ ‘anew’’
                  1. NYR83V answers ‘use of the subject: where & by who how & when?’
                  2. NX57BT for the immediate LHS via the immediate RHS
                  3. NX57CH specifies usage potentially including
                    1. NX57F4 where as 1st & last & typical
                    2. NX57G3 how many
                    3. NX57IU how as examples & typical
                    4. NX57G7‘replacement’
                      1. NX5IM3 NOT doing this
                        1. NX5IMU now started considering
                      2. NX5IOU ‘notable pros thru cons’
                        1. NX5IKQ follows from expression ‘use instead’ & ‘instead use’ (what inspired this) –pro
                        2. NX5IRS focus on doing something else where as other specifics are on doing it –notable con
                      3. NX5GQS as case say  #NX4GW3
                    5. NX57J5 possibly more
                2. NX57JR ‘per def’
                  1. NX57K8 ‘same or similar’ ‘sub’
                    1. NX57L0 <0 NOT necessarily ‘‘per def’
                3. NX579E ‘‘name’ ‘anew’’
                  1. NX57YF ‘usage’
                    1. NX57YM at & starting~ #NX0AD2 then /5129##NX1UCG then #NX4GW3
                    2. NX5E5Q ‘‘rendering’ ‘anew’’ ‘‘usage’
                  2. NX584U ‘using/usage’ at & starting #NX04HI
                  3. NX57TF ‘usage/occurrence/using’ at & when #NX04KB
                  4. NX578Y ‘usage & use’ or similar
                    1. NX57OV starting 2015.10.15~
                4. NX5E82 ‘‘‘Pretty Link’ entry’ ‘anew’’ 1st
                5. remaining sections
                6. NYQPZJ type
                  1. NYQQ07 actual
                    1. NYQQBA NYQQBA: the default
                  2. NYQPZR intended
                    1. NYQQ5H ‘per def’  ‘same or similar’ ‘sub’ 0  ‘purpose’
                    2. NYQQQ6 ‘usage’  ‘in order’ 1st ‘NYQMLV: intended so purpose’
                    3. remaining sections
                    4. NX5G75 ‘-’  ‘‘replacement’
                      1. NX5IYF ‘replacement’
                        1. NX5IYR being considered due cons (of #NX5GUM)
                      2. NX5GFP ‘‘definition’ ‘anew’’
                        1. NX5GD5 syntax: x operator {x operated on} {operation other details}
                        2. NX5GSI operation: replacement
                        3. NX58CG at least when present & valid, this op’s listing rank seems to be 1st
                          1. NX58EZ as case say  #NX4GW3
                          2. NX58GD to alert readers 1st thing ‘this should no longer be used’
                      3. NX5GJL ‘per def’
                        1. NX5I8W syntax lists in 1st then 2nd so chronological order
                          1. NX5ICD also matching #NX5955
                          2. NX5IB8 observation inspired by #NX3OQE
                        2. NX5GUM ‘notable pros thru cons’
                          1. NX5HL4 performing is seemingly essential for {‘‘congruence closure’’ plus appropriate function} –key pro
                          2. NX5IEI #NX5I8W –pro
                          3. NX5GHH to this key point ASAP  –pro
                          4. NX5JGE when directed to others, a violation of ‘don’t tell me what to do, just tell me your preferences’ –seeming small con
                          5. NX5GIB lacks other types comparison notably per #NX5GNQ –con
                          6. NX5IWE lacks specification of degree, as ‘replacement from most to least preferred’  –notable con
                        3. NX5GMQ ‘same or similar’ ‘sub’
                          1. NX5GNA >0  in function
                            1. NX5GNQ‘sub’
                      4. NX5I41 ‘‘name’ ‘anew’’
                        1. NX5GW6 ‘replacement’
                          1. NX5HUQ ‘‘rendering’ ‘anew’’ ‘‘replacement’
                        2. NX5HZO ‘replaced by’
                          1. NX5HZJ as originally used until now at #NX58YT–what inspired this
                          2. NX5I0O ‘notable pros thru cons’
                            1. NX5I13 puts in tense (past) which is not appropriate in all cases (as for ‘groom a replacement’) –notable con
                      5. NX5HQX ‘‘‘Pretty Link’ entry’ ‘anew’’ 1st
                  3. NYQQ00 expected  ‘-’
                    1. NYQQ7V ‘usage’  ‘in order’ 1st ‘NYQOP2: expected’
                7. NYPFTW ‘-’‘in order’
                  1. ‘usage’
                  2. NYPFUY ‘‘definition’ ‘anew’’
                    1. NYPFVJ for ‘‘usage’’, tells where the subject was used in order.
                      1. NYPFX6 usually the 1st usage is significant, commonly the subject’s initial ‘‘motivation or source or change’ ‘in reverse start order’’.
                    2. NYPIN4 if no ‘order by’ is specified, it defaults to time going forward aka ‘chronological order’
                  3. NYQ4L9 ‘‘motivation or source or change’ ‘in reverse start order’’ for usage use
                    1. NYQ4NJ came up with in this a week or so ago and started doing it informally, then formalized it today.
                    2. NYQ4LJ it seems good & interesting history to record the 1st uses, and generally best to do so in order.
                  4. NYPFYB ‘name anew’ ‘in order’
                    1. NYPFYS ‘rendering anew’  ‘‘in order’
                  5. NYR2ND ‘per def’
                    1. NYR2QE is seemingly puproseless with just {1 entry plus a few short entries}.
                  6. NYPFZE ‘‘‘Pretty Link’ entry’ ‘anew’’ section 1st
                    1. NYPG66 giving subject its own link in case it has more uses beyond its present parent (‘‘usage’‘)
            5. NOW3JL ‘-’  ‘‘motivation or source or change’
              1. NXKC0K ‘‘definition’ ‘anew’’
                1. NYR81P answers ‘What caused the subject?’
                2. NXKC3N unless specified otherwise, the 1st motivation is
                  1. NXKC5T for the initial/1st use else uses
                    1. NXKC63 which is to be specified by ‘‘usage’
                    2. NXKCA3 notably expecting Necessity is the mother of invention
              2. NOW3K9 ‘‘name’ ‘anew’’
                1. NXKCISmotivation or source or change
                  1. NXKCJW per preferring singular form
                  2. NXKCL4 ‘‘rendering’ ‘anew’’ ‘‘motivation or source or change’
                2. NOW3KNmotivations+sources+changes’
                  1. NOW3KZ ‘motivations & sources & changes ‘in reverse start order’’
                    1. NOW3N0 replacing every ‘ & ’ with ‘+’
                    2. NOW3MD extracting from NOM7X9
                  2. NOW3QS ‘‘rendering’ ‘anew’’
                    1. NOW3RB‘motivations+sources+changes NOW3JL’
              3. NOM5R5 ‘-’  ‘‘‘motivation or source or change’ ‘in reverse start order’’
                1. NOM5VC “reverse’ order picked to match ‘name in reverse start order’ & others
                2. NRDVKU ‘replacement’ (possibly just in name): TBA per  NRDVPL
                3. NOM7E5 ‘name ‘in reverse start order’’
                  1. NXKCP5‘motivation or source or change’ ‘in reverse start order’
                    1. NXKCSN ‘‘rendering’ ‘anew’’ ‘‘‘motivation or source or change’ ‘in reverse start order’’
                  2. NYP9OM ‘‘‘Pretty Link’ entry’ ‘anew’’ 1st –created at time of #NXKCSN
                  3. NOM7X9 now to next: ‘motivations & sources & changes ‘in reverse start order’
                    1. NOM87C ‘motivations & sources & changes ‘in reverse start order’’
                      1. NOM8I6 realized I could instead more clearly put ‘motivations’ in the name
                      2. NOM8GF started draft quote:
                        1. NOM7NA ‘sources’ NOM7NA
                          1. NOM7UL ‘definition ‘in reverse start order’’
                            1. NOM7UY includes motivations
                      3. NOM8FN wanted to extend ‘source’ to include motivation
                      4. NOM87W found it useful to place reason NOM0OU under  NOM4G3 which was then labeled ‘changes & sources in reverse start order’
                    2. NWWQ2U ‘‘rendering’ ‘anew’’
                      1. NWWQ3X‘motivations & sources & changes ‘in reverse start order’’
                        1. NWWQ4M beginning seemingly very soon after #NOM8I6
                  4. NOM7EU now originally to next: changes & source‘in reverse start order’
        2. NYR4IC multi-aspect
          1. NOM6YI ‘-’‘notable pros thru cons’
            1. NYPBBS ‘‘name’ ‘anew’’
              1. NYPBE5 ‘notable pros thru cons’
                1. NYPBFS ‘‘rendering’ ‘anew’’ ‘‘notable pros thru cons’’ :NYPBFS
              2. NX7UCF ‘notable pros thru cons:’
                1. NX7UEF ‘‘rendering’ ‘anew’’  ‘‘notable pros thru cons:’
                  1. NX7UG2 started probably at time of ID #NOM6YI
            2. NONS6V possible alternatives
              1. NONS7P ‘motivations & sources & changes ‘in reverse start order’’
            3. NYP9JC ‘‘‘Pretty Link’ entry’ ‘anew’’ 1st –created at time of #NX7UEF
          2. NVWNQ9 ‘-’ ‘‘unique pros thru cons’
            1. NVWNQX ‘‘name’ ‘anew’’
              1. NVWNOI ‘unique pros thru cons’
                1. NYPBJ8‘unique pros thru cons’
                2. NVWNT0 ‘‘rendering’ ‘anew’’‘unique pros thru cons’NVWNQ9
            2. NVWNV7 background
              1. NVWNVU an alternative to  ‘‘notable pros thru cons’
              2. NVWNYD designed to be used for each of multiple items being compared that any given attribute is only listed once –where it is most present– instead of say being multiply listed as notably a pro for one and the lack-of-it as a con for another.
            3. NYP9FR ‘‘‘Pretty Link’ entry’ ‘anew’’ 1st –created at time of #NVWNT0

  7. (for this post) my ‘motivation’ (and, TBA, its achievement)
  8. ‘success of this’
  9. ‘annex’
  10. NYF0E6 ‘NOLDef’ so this is a ‘DestinyArchitect creation’‘so post category’  that.
  11. NYEZOJ ‘post history additional’‘‘post history additional’ ‘in reverse start order’:’
    1. NZ62CX ‘{post.status.snapshot{;date ’20151210Thu11553pst‘;after ID ’minutes 0‘;revision ’3? List not shown! Perhaps from not being published.‘;version1.0‘;words ’7133‘;as ’due to q(NZ5XMS last ASAP Chrome restart), saving & sharing sooner than normal‘;doNY0WO6 with 902 replacements then Publish 1‘}}’
    2. NZ14R3 continue improving: updates #NZ1DMM thru #NZ1E59 + #NZ24S9 + #NZ2502 thru #NZ17D3 + #NZ1CIW thru #NZ1DGV
    3. NZ13HC NZ13HC: ‘{post.status.snapshot{;date ’20151207Mon2329pst‘;after ID ’minutes 0‘;revision ’2‘;version0.2‘;words ’6123‘;as ’OS crash NZ0HER causes this to give no ‘autosave’ warning so check diffs manually but {can’t as that was the 1st revision so are none} but find unconverted KCGUIDs revealing updates {#NYEZ9X thru #NYFJMB + #NYFJ53 thru  #NYI47N + #NYG158 thru #NYG19F + #NYQZXN thru #NYFJBP + heading #NYFJ9O + heading #NYFJFV + #NYFIZP thru
      + #NYQPWD thru #NYQOPR#NYR891 + #NYPHM2 thru #NYQPMK + #NYQOZD thru #NYQP7E + #NYPHVD thru #NYPFDP + #NYQOMX thru #NYR7BT#NYQPZJ thru #NYQQQ6 + #NYQQ00 thru #NYPG66 + #NYR81P#NYR4IC mostly thru #NYPBFS + #NYP9JC + #NYPBJ8 + #NYP9FR thru history #NYEZ1H} ‘;do ’continue editing starting with #NXS2YK with 836 replacements‘}}’
    4. NYPIIT {additions from scanning down text: #NYF05J + heading NYFIVE(‘explain’)+NYPFTW(‘in order’) thru last entry #NYPIN4 + #NYP9OM + heading #NYFIZP(‘review’) + #NYPAKF + #NYPBFS especially + #NYPBJ8 especially + heading NYFJ53(‘super/sub’) +heading ‘NYG12L: per se’ +  heading #NYG12L(‘arguments specified by name’) + heading ‘NYFJBP: ‘binary endorelation’ + maybe additional arg(s)’ + ‘NYPHMA: ‘where’ aka ‘what place’’ especially + ‘ NYPFDP: ‘-’ ‘‘display place’’’ thru last entry ~#NYPI0F + heading ‘NYFJ9O: quantity-ish’ + heading ‘NYFJFV: distance-ish’ + possibly a few more} + do all #NYPBE5 updates, so ~38.
    5.  template
      1.  ‘{post.status.snapshot{;date ’20151120Fri1439pst‘;after ID ’minutes 0‘;revision ’1~‘;version1.0‘;words ’1227‘;as ’finished all present updates‘;doNY0WO6 with 75 replacements then Publish 1‘}}’
    6. NYNSKH from move to here, seeing ‘‘usage’’ link breaking, fix links from move to here & some to elsewhere: source gives 22 and here gives 0; afterwards have 4 & 13 respectively including (the rest: 22-(13+4)) moved to other places.
    7. NYEZOD content: add: initial content
    8. NYEZ1H ‘{post.status.snapshot: date ’20151126Thu0046pst‘;after ID’ minutes 0‘;revision ’1‘;version0.1‘;words ’181‘;as ’/5138#NYEZ4O ‘;do ’following NXBIBI with {{template plus no source text} last {addition if known else history entry} /5225#NYC96Q, create {this ‘document’}‘}’.