Oct 292015
 

NWYUYU ‘intro & overall’

  1. NWZ059 ‘This {post & its comments}’s ‘TOU(Terms Of Use) including copyright ©, confidentiality/privacy, info’s allowed use’ is JotHere.com’s default TOU(Terms Of Use) except: none.
  2. .

    NWZ0V8 post name & ‘post image’:

    ‘‘constructing: {‘NOLDef’ {‘weighted graph’ & related}} ‘in ‘NOLDef’’ ’NWYUYU

    1. NWZ0VS ‘‘section history additional’ ‘in reverse start order’:’
      1. NXKHDI present
        1. NXKHFI follow /4670#NXK0JA plus fix the link
      2. NX2XMJ ‘‘constructing‘‘‘definition in ‘NOLDef’ ..’..’’ of {‘NOLDef’ {‘weighted graph’ & related}} ’NWYUYU
        1. NX3OQE ‘ & similar’ ‘replacement’ ‘& related’
        2. NX2XSX more accurate with new wording
        3. NX2XS4 cut ‘concepts’ as just too much here
      3. NWZ0W6 ‘‘constructing‘‘‘definition in ‘NOLDef’ of concept’s’’ of {‘NOLDef’ {partial order relations & similar}} ’NWYUYU
      4. NWZ0WQ ‘so post category’
        1. NWZ836 ‘NOLDef NWZ578’
          1. NWZ7QW ‘this site’s documentation for its users NQBFBL’ –as implied but not yet in practice
        2. NWZ84P ‘in NOLDef NWZ6UN’
  3. NWZ05J To reply & discuss, please use JotHere.com’s default methods (click) except: none.
  4. NWZ060 ‘for remainder, sections overall  ‘definition’ + TBA+ ‘contributors’ + ‘post history additional’

  5. NWZ067 ‘‘‘definition in ‘NOLDef’ of concept’s’’ of…:  ‘‘definition in ‘NOLDef’ of concept’s’
    1. NYIQHC:  ‘-’  ‘‘operation/phrase’
      1. NYJFHE:  ‘usage’
        1. NYJFHP:  top
          1. NYJFK4:  as language, including mathematics & all others, seemingly can’t exist without it, as no meaningful expressions can be made.
          2. NYJG1B:  so IMHO should be taught to everyone ASAP
            1. NYJG2C:  as, for math, right after teaching ones 1st 2 to 4  ‘operator’/operations (typically standard arthimetic, so add, multiply, etc)
              1. NYJHK9:  so around 4th grade.
      2. NYIRM2:   ‘‘definition’ ‘anew’’
        1. NYIS1I:  a connection
          1. NYJ92A:  which, if utilized to unify particular instances of its values, is a calculation
          2. NYJ87T:  between its values
            1. NYJ9R9:  where each which can be, and mostly is, {particular, meaning used as a component of other operation(s) and/or be 1 constant}
            2. NYJA10:  of type
              1. NYJ8A2:  the ‘operator’ with
                1. NYJA9I:  the quantity being 1
              2. NYJ8D2: the operand(s), with
                1. NYJA7O:  the quanity is the arity
                2. NYJBRV:  the domain of each operand, taken together, is the domains
                3. NYJA80:  the collective possible values, specificaly the cartesian product of the domains, is the domain
              3. NYJ9MA:  the output/result/value(term source) aka meaning(term source), with
                1. NYJAAP:  the quantity being 1
                2. NYJGWF:  the values possible or constrained to the range
                3. NYJAPY:  the values possible is the image, with
                  1. NYJCV6:  a certain superset is the codomain
                    1. NYJCWO:  which is {the 1st or last of the domains} typically, including for ‘operation on 1 set’
                4. NYJH5P:  the image else the codomain is the range
                  1. NYJH7J:  so, because the terms’s ambiguity, seemingly a term to avoid
        2. NYJ9HZ:  called the operator being applied to these operands or the application of the operator to the operands
      3. NYIR98:   ‘per def’  ‘same or similar’ ‘sub’
        1. <0
        2. NYJIDS:  0 ‘Wikipedia’
          1. NYIQIL:    https://en.wikipedia.org/wiki/Operation_(mathematics) especially https://en.wikipedia.org/wiki/Operation_(mathematics)#General_description except
            1. NYJBE4:  presently every defintion of meaning (there & on that article & often on related articles, plus on all other instructional texts I recall)
              1. NYJFNT:  is weak
                1. NYJFUQ:  why?
                  1. NYJHQB:  my guess is (similar reasons)
                    1. NYJFV5:  because it’s so incredibly basic, as perhaps like walking, those who really get it then don’t want to bother to stop & explain it.
                    2. NYJHPQ:  because we don’t teach it early, by the time someone finally gets it, because it’s so incredibly basic so far back, then few want want to go back that far and explain it, creating a nasty catch-22.
                2. NYJFP1:  which given top use, is terrible IMHO
                  1. NYJFXB:  including causing even me, a top MIT CS grad
                    1. NYJGR2:  suffering from the ‘range’ meaning‘s confusion until just now writing that point!
                    2. NYJGQH:  not to really start seeing & getting all these concepts until midway thru college
                      1. NYJGAF:  until being introduced to such abstractions by my personal study of symbolic computation plus the MIT CS courses
                        1. NYJGNG:  introductory (6.001 but a much earlier year) when it covered constraint programming
                        2. NYJGPU:  discrete math (6.042 but a much earlier year)
                      2. NYJHEY:  when instead IMHO ~4th grade seems appropriate for me & most to be taught this
                3. NYJFO6:  specifically from most problematic,
                  1. NYJHH9:  does not seem to emphasize its top importance
                  2. NYJBB4:  is missing, often notably, all the core related components, for instance
                    1. NYIRTA:  ‘a calculation from zero or more input values (called “operands“) to an output value’ is missing  ‘operator’ , general arity, domain, codomain, etc.
                  3. NYJC1U:  is not a nicely-broken down outline, which, IMHO, is dramatically more readable & usable.
                  4. NYJ9DV:  ‘calculation’ should be replaced with ‘connection’ per distinction #NYJ92A
                  5. NYIRSD:  ‘An operation ω ’ should be ‘An operator ω’
                  6. NYJBKV:  sometimes gives detail that instead belongs in the the defintion of subcomponents, for instance
                    1. NYJBNZ:  ‘power of the codomain’ belongs in my ‘operation on 1 set’
          2. NYJIEB:  https://en.wikipedia.org/wiki/Phrase
      4. NYJI4Y:  ‘‘name’ ‘anew’’
        1. NYJIDG:  ‘operation/phrase
          1. NYJLT1:  ‘‘rendering’ ‘anew’’ ‘‘operation/phrase’
        2. NYJI8T:  ‘operation’  –starting at concept’s id time
      5. NYJLMA:  ‘‘‘Pretty Link’ entry’ ‘anew’’ section 1st
      6. ‘for remainder, sections overall
      7. NYIRMG:  is represented by an expression of form…
        1. NYJDZ8:  _ (name TBA)
          1. NYJE08:  the by far most typical (form), at least for human consumption
          2. NYJDX4:  gives only & all the operation’s components except
            1. NYJD7X:  the expression itself stands for the result
              1. NYJDKZ:  which, if placed…
                1. NYJDA8:  within another operation or statement, is serving as an operator or operand within that determined by the placement.
                2. NYJDLH:  top level, is being asserted as being universally true, so then saying the expression is tautology and perhaps an axiom.
        2. NYJE19:  a tuple/row consisting of a primary id, plus a foreign id (referencing another or this such id) for each of {the values including  the result}
        3. NYJE7L:  a number of others possible
      8. NYJUH0:  ‘-’ ‘‘‘operation/phrase’ ‘default connections’’’ (aka ‘precidence’)
        1. NYJRH3:   ‘usage’
          1. NYJRHC:  never else minimally relying on defaults here
            1. NYJRJV:  is so far NOT the norm in popular communications
            2. NYJVUB:  is done by…
              • NYJVTB:  programming language
                1. NYJRKM:  LISP (so meanly called ‘Lots Silly Parenthesis’)
                2.  Scheme
              • is done by data langauge
              • NYJVGY:  is done by XML so potentially all HTML
                1. NYJVKL:  somewhat unobviously: because parantheticals are done not by ‘(..)’ or other familar equivalents, but by done  ‘<tag ..>..</tag>’ so not using  pathethesis per se, so perhaps per that, sneaking into acceptance as likely required)
            3.  
              1. NYJVNG:  which is extremely {famous & proven}
            4. NYJRMD:  I recommend 
              1. NYJROF:  with the minimal exception of
                1. NYJS1F:  {method call/member-access} is left-associative
                  1. NYJS4H:  as in many cases here #NYJS0T would not hold, including
                    1. NYJS6Z:  including for pure functional results in near infinite parenthesization, including infinte if interactivity added
                2. NYJT76:  possibly (low) a few others I’ve not yet conceived.
              2.  NYJSAB:  as, from biggest reasons:
                1. NYJSEZ:  clarity should always be preferred whenever practical (which it is), including
                  1. NYJSIF:  such defaults are complex and often not well understood (plus we may want to change), so bugs & misunderstandings are commonly introduced
                2. NYJU20:  the number of parentheticals then requiring addition which one would typically otherwise skip/save, is quite managable, including:
                  1. NYJS0T: small, usually no more than ~5 levels, so a small constant addition.
                  2. NYJSB7:  with any respectable text editor & viewer (so providing good paren matching & jumping), as Brackets and most famously emacs, properly makes matching is easy plus has power features
                    1. NYJSM6:  my guess is the lack of such editors & viewers being commonplace is the biggest reason such for the present norm even for languages we’ve developed in recent history.
                3. NYJV3U:  makes language parsing dramatically simpler
                  1. NYJV4L:  significantly enabling helpful syntactic tools, as example
                    1. NYJV83:  readily enables powerful editor & viewer features as expression jumping & especially code folding
                  2. NYJVAJ:  significantly encouraging the development of custom languages by demonstrating one doesn’t don’t need a fancy parser to have a a new powerful programming/expression language
                  3. NYJTU6:  only a few languages allow custom (operators, here called functions or similar) to have precidence
                    1. NYJTWO:  by overloading the built-in operators with no change in their precidence (so same parser works)
                      1. NYJTXK:  feels like the norm
                    2. NYJT9A:  customizing/overriding these defaults, so customizing precidence, appears hard (requring an advanced parser) & rare
                      1. NYJU5T:  Mathematica seems to have it per Q&A
                      2. NYJTRG:  F# may have it per article
                      3. NYJTJY:  Perl 6 may have it; possible example
                      4. NYJTTH:  relevant discussion http://mortoray.com/2012/07/13/can-the-ideal-language-allows-custom-operators/
        2. NYJQ2H:  ‘‘definition’ ‘anew’’
          1. NYJQ2Q:  rule(s) telling what operation(s) connections to make by default when this info is not specified by an operation(s) expression.
            1. NYJQEO:  especially telling, for each ‘operator’ (given else implied) by the expression, which of the expression’s other values, including result values & possibly implied values, are to be its operands
              1. NYJQZQ:  which in most potentially all cases means what {parentheses groups (to denote ‘precidence’ as that that link details) plus possibly its operand(s)} are to be inserted into the expression to correct, hopefully fully, for it here being incomplete else shorthanded.
        3. NYJUYO:  ‘per def’  ‘same or similar’ ‘sub’
          1. <0
          2. NYJQSF:  0 ‘Wikipedia’ https://en.wikipedia.org/wiki/Order_of_operations except
            1. NYJQNG:  ‘order’, especially ‘order of operation’ so referring to ‘procedures to perform first in order to evaluate’
              1. NYJQPM:  is a common view as typically this is also the same but
              2. NYJQPZ:  is wrong as gets into the still seperate issue of evaluation strategy
        4. NYJPUC:  ‘‘name’ ‘anew’’
          1. NYJUD0:   ‘‘rendering’ ‘anew’’ ‘‘‘operation/phrase’ ‘default connections’’
          2. NYJPX5:  root: ‘operation/phrase’
          3. NYJUCE:  ‘default connections’
          4. NYJPXP:   ‘default grouping’
          5. NYJUKI:  ‘operator precidence’
            1. NYJUPV:  problem from worst first:
              1. NYJUSU:  topic generalized here (debatably) to cover other NYJUCE(‘default connections’) notably default operand values.
              2. NYJURB:  if precidence is taken (as it it commonly) is beyond syntac grouping but to evalaution order, then #NYJULJ applies.
          6. NYJUK2:  ‘order of operations
            1. NYJULJ:  killer problem #NYJQNG
        5. ‘for remainder, sections overall
      9. NX1HOJ ‘-’  ‘‘operator’
        1. NX1IPK ‘‘definition’ ‘anew’’
          1. NYJE9Q:  per the operator
          2. NYJNXW:  in some contexts, may be implied. Example:
            1. NYJO3W:  ‘xy’ can mean ‘x*y’ where ‘*‘ is multiplication
            2. NYJO53:  ‘red dog’ can mean ‘dog intersect red’
          3. NYJOAF:  just another of the operand(s)
            1. NYJOCX:  a possiblity
              1. NYJODK:  which is rare but conceivable
            2. NYJOF6:  makes computablity complex possibly impossible
            3. NYJOIS:  natural notably long term proper
              1. NYJOJQ:  probably not
          4. NYJOYG:  for a clause ‘operation/phrase’, the verb –at least on quick look
          5. NX1IPX [replaced] (probably) a function specified by a standard symbol
            1. NYJEAZ:   ‘replacement’  #NYJE9Q
        2. ‘notable pros thru cons:’
        3. NX1HWV  ‘per def’ ‘same or similar’ ‘sub’
          1. NX1HXB <0
            1. NX1HXK ‘1’  ‘function’ per #NX1IPX
          2. NX1HYJ 0
            1. NX1HZB ‘Wikipedia’ ‘‘anew’
              1. NYISNA:  #NYIRSD
              2. NX1I3L #NYIQIL instances ‘operator’
              3. NX1HZU https://en.wikipedia.org/wiki/Operator_(computer_programming)
              4. NX1I5I https://en.wikipedia.org/wiki/Operator_(mathematics) except
                1. NYJPOT:  as far as domains & codomains possible, appears incomplete
                2. NYJPP5:  no mention of ‘symbol’
                3. NYJPQ1:  no mention of ‘precidence’
          3. NX1IMS >0 common (including suggested much more confusingly from here)
            1. NX1IM8 inequality { ≤, ≥} applied to real numbers
              1. NX1IMK but notably applicable not to complex numbers as that here has only a  ‘reflexive partial order’}
        4. NX1HTT ‘‘name’ ‘anew’’
          1. NX1HUD ‘operator’
            1. NX1HV3 ‘‘rendering’ ‘anew’’ ‘‘operator’
        5. NYEYE3:  ‘‘section history additional’ ‘in reverse start order’:’
          1. NYIR65:  location: from /5129#NWWQ6B kid last to here
          2. NYEYED:  location: from /5138#NWZ067 kid to here
    2. NYIPF4:  ‘-’   ‘‘function’
      1.  ‘‘definition’ ‘anew’’
      2. NYIPR9:   ‘per def’  ‘same or similar’ ‘sub’
        1. <0
        2. NYIPR1:  0 ‘Wikipedia’ https://en.wikipedia.org/wiki/Function#Math.2C_computing_and_engineering
      3. NYIPFX:  ‘‘name’ ‘anew’’ ‘function’ ‘‘rendering’ ‘anew’’ ‘‘function’
      4. NYIPH6:  ‘‘‘Pretty Link’ entry’ ‘anew’’ section 1st
      5. ‘for remainder, sections overall
      6. NYIPWQ:  ‘-’   ‘‘binary ‘function’’
        1.  ‘‘definition’ ‘anew’’
        2. NYIPYK:   ‘per def’  ‘same or similar’ ‘sub’
          1. <0
          2. NYIPZ9:  ‘Wikipedia’ https://en.wikipedia.org/wiki/Binary_function
        3. NYIPVJ:  ‘‘name’ ‘anew’’ ‘binary ‘function’‘‘rendering’ ‘anew’’ ‘‘binary ‘function’’
        4. ‘for remainder, sections overall
    3. NX0B3C ‘-’ ‘‘weighted graph’
      1. NX0BMO ‘notable pros thru cons:’
        1. NX0BN7 seemingly among the top most universal structured/formal knowledge representations
        2. NX0CK5 naturally ‘‘sub’ >0′ properties apply, so say #NX0BP4
      2. NX0BZJ where every weight is
        1. NX0C1N 1 or 0
          1. NX0C23 is potentially any ‘binary endorelation’
        2. NX0C31 can be a number other than 1 or 0
          1. NX0C6W is used as the primary formal/structured means for optimizing travel and resource distribution
      3. NX2PZ7 ‘per def’ ‘same or similar’ ‘sub’
        1. NX2PZX <0
          1. NX2Q0A ‘1’ weighted multigraph
        2. NX2Q0W 0
          1. NX0DTV{binary aka 2-input} function from V*V to Number’ (where V is any set, called the vertices)
            1. NX2Q1V in some cases also a real-valued function
          2. NX2Y03 ‘Wikipedia’
            1. NX2Y3A https://en.wikipedia.org/wiki/Glossary_of_graph_theory#Weighted_graphs_and_networks
            2. NX2Y3K https://en.wikipedia.org/wiki/Graph_(mathematics)#Weighted_graph
            3. NYIO9Q:  https://en.wikipedia.org/wiki/Graph_(abstract_data_type) including ‘Structures that associate values to the edges
        3. NX2QB3 <0 common ‘1’
          1. NX2QBN ‘binary endorelation’
      4. NX0BAH ‘‘name’ ‘anew’’
        1. NX0BBKweighted graph
          1. NX0BQU ‘‘rendering’ ‘anew’’
            1. NX0BR1‘weighted graph’
        2. NX0BKO ‘weighted ‘binary endorelation’
        3. NX0CELnetwork
          1. NX0CFK  ‘notable pros thru cons:’
            1. NX0CFX 2nd most common term for this –pro
            2. NX0CGD many less formal meanings –notable con
      5. ‘for remainder, sections overall
      6. NYIO1V:  ‘-’
        1.  ‘‘definition’ ‘anew’’
        2.   ‘per def’  ‘same or similar’ ‘sub’
          1. <0
          2. 0
            1.  ‘Wikipedia’
            2. ‘notable pros thru cons:’
        3.  ‘‘name’ ‘anew’’ ‘‘binary endorelation’ reflexivity’ ‘‘rendering’ ‘anew’’ ‘‘‘binary endorelation’ reflexivity’
        4. NYGL37 ‘‘‘Pretty Link’ entry’ ‘anew’’ section 1st
        5. ‘for remainder, sections overall
      7. NX0CIA ‘-’‘binary endorelation’
        1. NYINEE:  ‘‘definition’ ‘anew’’:
          1. NYINEZ:  see Wikipedia entries except as noted.
          2. NYFOVR –with variables/preface ‘for all x and y in [‘binary endorelation’X (it holds that)…’
        2. NX0CO7 ‘notable pros thru cons:’
          1. NX0CMR seemingly the most common of its superclass
        3. NX0BXJ ‘per def’ ‘same or similar’ ‘sub’
          1. NX0CPH <0
            1. NX0CQG ‘1’ ‘weighted graph’
          2. NX0JBC 0
            1. NX0JBN ‘Wikipedia’ https://en.wikipedia.org/wiki/Binary_relation#Relations_over_a_set
              1. NX0JDE –an excellent reference.
          3. NX1RFZ >0 common
            1. NX1RGA NX1RGA‘Wikipedia’ https://en.wikipedia.org/w/index.php?title=Binary_relation&oldid=684344533#Relations_over_a_set ‘Some important properties’
            2. NYFKJD by most salient/biggest features first:
              1. NX1RNP transitivity amount
              2. NX1RW0 symmetry:
                1. NYFOMB -1:  ‘1’  ‘’total: .. xRy or yRx (or both). This definition for total is different from left total in the previous section. For example, ≥ is a total relation.’
                  1. NYFP62 ‘per def’ ‘same or similar’ ‘sub’ <0  ‘reflexive’ per here
                2. NX1RZJ 1: ‘1’  ‘symmetric: ..if xRy then yRx. “Is a blood relative of” is a symmetric relation, because x is a blood relative of y if and only if y is a blood relative of x.’
                3. NX1S2N 0: ‘1’ ‘antisymmetric: ..if xRy and yRx then x = y. For example, ≥ is anti-symmetric (so is >, but only because the condition in the definition is always false).[18]
                  1. NX1S2V ‘same or similar’ ‘sub’ >0 common ‘1’ ‘asymmetric: ..if xRy then not yRx. A relation is asymmetric if and only if it is both anti-symmetric and irreflexive.[19] For example, > is asymmetric, but ≥ is not.’
              3. NYHZ2Q ‘binary endorelation’ reflexivity’
        4. NX0DGE ‘‘name’ ‘anew’’
          1. NX0DGMbinary endorelation
            1. NX0E4A ‘‘rendering’ ‘anew’’
              1. NYHSK0‘binary endorelation’
              2. NX0E4M‘binary endorelation’
          2. NX0IKZhomogeneous binary relation
          3. NX0IURsimple directed graph permitting loops
            1. NX0J5P quoting from here then {linking ‘simple’ and depluralizing}
          4. NX0IA8 ‘directable binary-weighted uni-graph
            1. NX0ILN where my additions of…
              1. NX0IMB ‘directable’ to insure it’s not undirected but not require it be directed.
              2. NX0INI ‘binary-weighted’ to make sure it’s not a general ‘weighted graph’
              3. NX0IOO ‘uni-graph’ to make sure it’s not a multigraph
        5. ‘for remainder, sections overall
        6. NYGN07 ‘-’  ‘‘‘binary endorelation’ P closure’
          1. NYGN42 ‘‘name’ ‘anew’’ ‘‘binary endorelation’ P closure’ ‘‘rendering’ ‘anew’’ ‘‘‘binary endorelation’ P closure’
          2. NYGN3P ‘per def’ ‘same or similar’ ‘sub’
            1. NYGN3B -1 ‘1’ P
            2. NYGN32 ‘Wikipedia’s P closure’: 0 ‘Wikipedia’ https://en.wikipedia.org/wiki/Closure_(mathematics)#P_closures_of_binary_relations
        7. NYFKHL common
          1. ‘for remainder, sections overall
          2. NX1S4P ‘-’  ‘‘‘binary endorelation’ reflexivity’
            1. NYHRTF ‘‘definition’ ‘anew’’
              1. NYHRPO the reflexivity of a relation on given scale.
            2. NYHRSC degree/amount
              1. NYHXW1 Yes:  ‘1’ ‘reflexive ‘binary endorelation’’
              2. NYHY8W No: ‘1’
                1. NX1S7Mirreflexive (or strict): .. not xRx. For example, > is an irreflexive relation, but ≥ is not.’
            3.   ‘per def’  ‘same or similar’ ‘sub’
              1.  <0  {graded Yes/No measure of a property’s presence}
              2. 0
                1.  ‘Wikipedia’
                  1.  https://en.wikipedia.org/w/index.php?title=Transitivity&oldid=688335497#Logic_and_mathematics especially on ‘relation’
                  2.  NX1RGA reflexive
                2. ‘notable pros thru cons:’
            4. NYHYRO ‘‘name’ ‘anew’’ ‘‘binary endorelation’ reflexivity’ ‘‘rendering’ ‘anew’’ ‘‘‘binary endorelation’ reflexivity’
            5. ‘for remainder, sections overall
            6. NX1S6T ‘-’ ‘‘reflexive ‘binary endorelation’’
              1. NYHXXM ‘‘definition’ ‘anew’’
                1. NYHXXAreflexive: .. xRx. For example, “greater than or equal to” (≥) is a reflexive relation but “greater than” (>) is not.’
              2. NYHY1V ‘per def’
                1. NYHY1O ‘notable pros thru cons:’
                2. ‘same or similar’ ‘sub’
                  1. <0
                    1. ‘1’ ‘binary endorelation’
                  2.  0
                    1.  ‘Wikipedia’ NX1RGA -> https://en.wikipedia.org/wiki/Transitive_relation
                  3. NX1QPY >0 common
              3. NYHSD4 ‘‘name’ ‘anew’’
                1. NYHSDV ‘reflexive ‘binary endorelation’’ ‘‘rendering’ ‘anew’’ ‘‘reflexive ‘binary endorelation’’
          3. NX1ZHK ‘-’ ‘‘relation transitivity’
            1. NX280M ‘‘definition’ ‘anew’’
              1. NX2813 the degree on this scale a relation has transitivity
            2. NX1ZU8 degree/amount
              1. NX1ZYW Yes
                1. NX1RO7 ‘1’ ‘‘transitive relation’
                2. NX1VBD ‘per def’ ‘unique pros thru cons’
                  1. NX2003 for any 2 elements, to identify between them any {transitive connection, a powerful thing}, tests required are just 3 {aRb &  aRb, plus {a=b} iff R is not reflexive} instead of up to the path length
                  2. NX1VBQ per #NX28LS, with limited exception, representing & reasoning in general requires {computation or storage which are somewhat interchangeable} of size O(~n or n^2 or perhaps more)
                    1. NX2JWY except for seemingly
                      1. NX2K08 partial equivalence thanks to good union-find (aka disjoint-set) algorithms
                      2. NX2L0R under the hood doing No but appearing Yes by internally bridging that gap via
                        1. NX2K9P where a difference between any 2 pair can be generally computed in time proportionate to the size of the element ids as
                          1. NX2K6O ‘total order’ over say numbers or strings in most cases
                          2. NX2KJB bloom filter or equivalent on a {‘‘partial order’’ as pure transitive seems not enough there}
                        2. NX2KUQ using memoization but could be a crap-shoot
              2. NX2N69 totally unknown to moderate No
                1. NX2CBU totally unknown
                2. NX2N8A minimal No
                  1. NX2NBQ ‘1’ intransitive
                3. NX09GH ‘No for path length <=2’
                  1. NX2NFD ‘1’  “antitransitive
                    1. NX2NJ0 note the name ‘anti-transitive’ is misleading as
                      1. NX2NLY suggest it would completely undoes what transitive does but transitive makes connections of large path length but
                      2. NX2NO3 this definition only says ‘No for path length <=2’
                        1. NX09OC as transitive cases recursively implied, notably {e(1)Re(2) & .. & e(n-1)Re(n) and e(1)Re(n)} for n>3, this anti-trans def misses
                4. NX2N7Z ‘per def’ ‘unique pros thru cons’
                  1. NX2CC5 low indeed lowest computation costs
                  2. NX2JHE bad {consistency & duplicate detection} for where transitivity is intended (normal) but here being informally maintained
              3. NX2CFN No
                1. NX2KWS  ‘per def’ ‘unique pros thru cons’
                  1. NX2JH2 low indeed lowest costs for storage so also duplicate detection & updates
                  2. NX2P67 ‘can also be found in time O(nm)’*
                2. NX1RQ0 ‘1’
                  1. NX090F ‘-’ ‘‘transitive reduction’
                    1. NX09XQ ‘‘definition’ ‘anew’’: given in its name.
                    2. NX0A3R ‘notable pros thru cons:’
                      1. NX0A42 key if not essential as a canonical form for most {{compactly representing} + {effectively reasoning about (example: for distance)}} any partial order, by both humans & computers
                        1. NX0A9J this point I have never seen mentioned anywhere
                          1. NX0ABS which surprises me & I can’t explain it.
                    3. NX0AD2 usage
                      1. NX0AGQ as a product of some specification
                        1. NX0ADV –as its name core ‘reduction’ suggests
                        2. NX0APY ideally with warnings where the specification {over-specified or (if cycles aren’t allowed) introduced a cycle}
                        3. NX0AIM a good idea
                        4. NX0AJJ ironically I’ve never seen this usage
                      2. NX0AKE specified directly
                        1. NX0AM8 such as specifying a factor of primes
                        2. NX0AL9 so with the assumption/hope that it matches what should be
                          1. NX0AOB often without any validation of that
                        3. NX0ATE is the usage I’ve so far always seen
                    4. NWXRAS   ‘per def’
                      1. NX2OB3 ‘same or similar’ ‘sub’
                        1. NWXRE0 <0 ‘1’ “antitransitive”
                        2. NWXQDU <=0 its source
                        3. NX2OL0 0
                          1. NX2OCH ‘Wikipedia’ https://en.wikipedia.org/wiki/Transitive_reduction including
                            1. NX2P2D ‘can also be found in time O(nm), a bound that may be faster than the matrix multiplication methods for sparse graphs’ which are typical.
                        4. NX2OLK >0 common {same as for transitive}
                    5. NX095B ‘‘name’ ‘anew’’
                      1. NX095Ntransitive reduction
                        1. NX09UY ‘‘rendering’ ‘anew’’
                          1. NX09VJ‘transitive reduction’
            3. NX1ZRX  ‘per def’  ‘same or similar’ ‘sub’
              1. NX2PHU <0  {graded Yes/No measure of a property’s presence}
              2. NX1ZSK 0
                1. NX1ZT7 ‘Wikipedia’
                  1. NX2LII https://en.wikipedia.org/w/index.php?title=Transitivity&oldid=688335497#Logic_and_mathematics especially on ‘relation’
                  2. NX1ZTN NX1RGA transitive
                2. ‘notable pros thru cons:’
            4. NX1ZNX ‘‘name’ ‘anew’’ ‘relation transitivity’
              1. NX1ZP8  ‘‘rendering’ ‘anew’’ ‘‘relation transitivity’
            5. ‘for remainder, sections overall
            6. NX1PXP ‘-’ ‘‘transitive relation’
              1. NX1QKS ‘‘definition’ ‘anew’’
                1. NX1V7W transitive (relation type)
              2. NX1PZF ‘notable pros thru cons:’
                1. NX1PZ7 seemingly the most formally familiar of its main superclass
              3. NX28D7  ‘per def’
                1. NX28DK for any 2 elements e(1) & e(n),
                  1. NX28FO e(1)Re(n) implies between the two elements there exists a path (of existing intermediate elements), specifically a transitive connection e(1)Re(2) & .. & e(n-1)Re(n),
                    1. NX28LJ going only in the direction given: starting at a and ending at b
                    2. NX28LS which can be as long (as many jumps) as the max of {{the total number of elements minus 1}, 0}
                2. NX1Q1P ‘same or similar’ ‘sub’
                  1. NX1Q28 <0
                    1. NX0K6S ‘1’ ‘binary endorelation’ notably transitive (relation type)
                  2. NX1QML 0
                    1. NX1QN7 ‘Wikipedia’ NX1RGA -> https://en.wikipedia.org/wiki/Transitive_relation
                  3. NX1QPY >0 common
                    1. NX1QVQ reflexivity
                      1. NX1QVG 1:  ‘1’ ‘‘preorder’
                    2. NX1QRQ symmetry
                      1. NX1QYE 1:  ‘1’ partial equivalence
                      2. NX1R23 0: ‘1’ ‘‘partial order’
              4. NX1PV1 ‘‘name’ ‘anew’’
                1. NX1PVF ‘transitive relation’
                  1. NX1PWS ‘‘rendering’ ‘anew’’ ‘‘transitive relation’
              5. ‘for remainder, sections overall
              6. NYGKUH ‘-’  ‘‘transitive closure’
                1. NYGKV0 ‘‘name’ ‘anew’’ ‘transitive closure’ ‘‘rendering’ ‘anew’’ ‘‘transitive closure’
                2. NYGLOF ‘per def’ ‘same or similar’ ‘sub’
                  1. NYGLFY -1 ‘1’ ‘‘transitive relation’
                  2. NYGLN8 0
                    1. NYGLN1 ‘Wikipedia’ https://en.wikipedia.org/wiki/Transitive_closure
                    2. ‘maker’
                3. ‘for remainder, sections overall
              7. NYFPSS transitive (relation type) and {reflexive (relation type) or/and antisymmetric (relation type)}
                1. ‘for remainder, sections overall
                2. NX0K04 ‘-’ ‘‘preorder’
                  1. NX1PES ‘‘definition’ ‘anew’’
                    1. NX1PFS transitive
                    2. NX1SRP reflexive (relation type)
                  2. NX5896 ‘per def’
                    1. NX0KII ‘notable pros thru cons:’
                      1. NX0KG9 seemingly the most common of its superclass
                    2. NX0K4X ‘same or similar’ ‘sub’
                      1. NX0K5D <0
                        1. see def
                      2. NX0K73 0
                        1. NX0K8W ‘Wikipedia’ https://en.wikipedia.org/wiki/Preorder
                  3. NX0K9P ‘‘name’ ‘anew’’
                    1. NX0KADpreorder
                      1. NX0KBW ‘‘rendering’ ‘anew’’
                        1. NX0KC5‘preorder’
                  4. ‘for remainder, sections overall
                  5. NYGM5F ‘-’   ‘‘equivalence relation’
                    1. NYGM88 ‘‘name’ ‘anew’’ ‘equivalence relation’ ‘‘rendering’ ‘anew’’ ‘‘equivalence relation’
                    2. NYGMCN ‘per def’ ‘same or similar’ ‘sub’
                      1. NYGM6X -1 ‘1’ ‘‘preorder’
                      2. NYGM6C‘Wikipedia’ https://en.wikipedia.org/wiki/Equivalence_relation#Definition
                    3. ‘for remainder, sections overall
                    4. NYGMF6 ‘-’   ‘‘congruence relation’
                      1. NYGMMH ‘‘name’ ‘anew’’ ‘congruence relation’ ‘‘rendering’ ‘anew’’ ‘‘congruence relation’
                      2. NYGMP8 ‘per def’ ‘same or similar’ ‘sub’
                        1. NYGMKG -1 ‘1’  ‘‘equivalence relation’
                        2. NYGMJR‘Wikipedia’ https://en.wikipedia.org/wiki/Congruence_relation
                        3. NYHG8R 1 common ‘1’ with the property that
                      3. ‘for remainder, sections overall
                      4. NX5H3R ‘-’ ‘‘congruence closure’
                        1. NX5H46 ‘‘definition’ ‘anew’’
                          1. NYHFCA ‘‘binary endorelation’ P closure’of ‘congruence relation’
                        2. NX5H65 ‘per def’ ‘same or similar’ ‘sub’
                          1. NYGLU3 -1 ‘1’ ‘‘transitive closure’
                          2. NYGLX1 0
                            1. NX5H4H https://www.google.com/search?q=congruence+closure
                            2. NYHFHB ‘Wikipedia’
                              1. NYHFHQ in ‘Wikipedia’s P closure’.
                              2. NYHFO3 found no other.
                            3. ‘maker’
                          1. NX5H6I ‘notable pros thru cons:’
                            1. NX5H6Q seemingly essential for reliably finding normal/canonical form
                          2. NX5HEO ‘same or similar’ ‘sub’
                            1. NX5HEZ <0 {closure}
                        3. NX5H8R ‘‘name’ ‘anew’’ ‘congruence closure’
                          1. NX5HGT ‘‘rendering’ ‘anew’’ ‘‘congruence closure’
                        4. NX5H9E ‘‘‘Pretty Link’ entry’ ‘anew’’ 1st
                3. NX1O6W ‘-’ ‘‘partial order’
                  1. NX1P3P ‘‘definition’ ‘anew’’
                    1. NX1R7K‘transitive relation’
                    2. NX1P47 antisymmetric (relation type)
                  2. NX1OAS ‘per def’ ‘same or similar’ ‘sub’
                    1. NX1OB8 <0
                      1. NX1PLX see def
                    2. NX1OOC 0
                      1. NX1O7D ‘notable pros thru cons:’
                        1. NX1O7T seemingly the most formally familiar of its main superclass
                      2. NX1OP0 ‘Wikipedia’ https://en.wikipedia.org/w/index.php?title=Partially_ordered_set&oldid=687708579#Strict_and_non-strict_partial_orders
                    3. NX1OQZ >0 common
                      1. NX1OZ6 strict/reflexive or not
                        1. NX0UU7 consequences including consequential theorems
                          1. NX0UGI for every partial order, the only difference between non-strict vs. strict is reflexive vs. irreflexive
                            1. NX0UIH per the combo:
                              1. NX0UNN ‘A (non-strict[ (or reflexive, or weak)*] ) partial order[2] is a binary relation “≤” over a set P which is reflexive, antisymmetric, and transitive’ says here
                              2. NX0UJ4 ‘ a strict (or irreflexive) partial order “<” is a binary relation that is irreflexive, transitive and asymmetric’ says here
                              3. NX0UTX ‘A relation is asymmetric if and only if it is both antisymmetric and irreflexive.[2]’ says here & #NX1S2V
                        2. NX1OSM ‘1’  ‘‘reflexive partial order’
                  3. NX1O8D ‘‘name’ ‘anew’’
                    1. NX1O8T ‘partial order’
                      1. NX1OJ9 ‘‘rendering’ ‘anew’’ ‘‘partial order’
                4. NX0S1F ‘-’ ‘‘reflexive partial order’
                  1. NX1SWK ‘‘definition’ ‘anew’’
                    1. NX1T91‘transitive relation’
                    2. NX1T9V antisymmetric (relation type)
                    3. NX1TAF reflexive (relation type)
                  2. NX0U3H ‘notable pros thru cons:’
                    1. NX0T1E seemingly the most common of its superclass
                    2. NX0BP4 commonplace tools to represent & reason-with them are still weak
                  3. NX0SH5 ‘per def’ ‘same or similar’ ‘sub’
                    1. NX0T24 <0
                    2. NX0T3U 0
                      1. NX1OMW‘partial order’’ AND reflexive (relation type)
                      2. NX0T2S‘preorder’’ AND antisymmetric (relation type)
                      3. NX0T4F ‘Wikipedia’ https://en.wikipedia.org/wiki/Partially_ordered_set#Formal_definition
                    3. NWYSR5 >0 common (including suggested in here)
                      1. NWYSVFis-a’ including social parenting & subset
                      2. NWYT4N has-a
                      3. NWYSZTinstance-ofprobably especially when there are relation chains as in prototype-based programming
                  4. NX0S4P ‘‘name’ ‘anew’’
                    1. NX0S53reflexive partial order
                      1. NX0S7J ‘‘rendering’ ‘anew’’ ‘‘reflexive partial order’
                    2. NX0U18non-strict partial order
                      1. NX0U4O usage: per #NX0UGI, prefer instead variant ‘reflexive’/‘irreflexive’ as that fully specifies the difference (instead of having to know strict for this context)
                  5. ‘for remainder, sections overall
                  6. NX1GI7 ‘-’  ‘‘total order’
                    1. NX1GVA ‘notable pros thru cons:’
                      1. NX1GVM seemingly the most formally familiar of its main superclass
                      2. NX1GVX commonplace tools to reason-with them are very strong
                    2. NX1GXW ‘same or similar’ ‘sub’
                      1. NX1GYX <0
                        1. NX1GZD ‘1’ ‘‘reflexive partial order’
                      2. NX1H3U 0
                        1. NYFPEU ‘1’  { total (relation type)  and ‘partial order’ }
                        2. NX1H48 ‘Wikipedia’ https://en.wikipedia.org/wiki/Total_order
                      3. NX1H59 >0 common (including suggested much more confusingly from here)
                        1. NX1H90 inequality { ≤, ≥} applied to real numbers
                          1. NX1HJP but notably applicable not to complex numbers as that here has only a  ‘reflexive partial order’}
                    3. NX1GPI ‘‘name’ ‘anew’’
                      1. NX1GQBtotal order
                        1. NX1GRC ‘‘rendering’ ‘anew’’ ‘‘total order’
        8. s
        9. NYHGMI ‘-’  ‘‘congruence property type’
          1. NYHHPQ ‘‘definition’ ‘anew’’
            1. NYHI46 property(s) which (seemingly equivalently):
              1. NYHHQ2 when combined with ‘equivalence relation’ assertion, create a ‘congruence relation’
              2. NYHI2L turn a given ‘equivalence relation’ into a ‘congruence relation’
          2. NYHKDW ‘‘motivation or source or change’ ‘in reverse start order’’
            1. NYHKE4 firstly to do #NYHJ80
            2. NYHKG4 #NYHHGG applies
          3. NYHIJM ‘‘name’ ‘anew’
            1. NYHIN9 ‘congruence property type’
              1. NYHIP1 ‘‘rendering’ ‘anew’’ ‘‘congruence property type’
            2. NYHGNV ‘congruence property’
          4. NYHIAE ‘per def’ ‘same or similar’ ‘sub’
            1. -1 ‘1’
            2. NYHI78 0
              1. my finds
                1.  
          5. ‘for remainder, sections overall
          6. NYHJA3 ‘-’
            1. NYHJ6T ‘‘definition’ ‘anew’’
              1. NYHKXA a binary endorelation R where,   given S1 & S2 which are each a array or equivalent,  {S1 R S2} if
                1. NYHIUW for every i, {S1[i] R S2[i]}
                  1. NYHLQD Note when condition
                    1. NYHMDA of both
                      1. NYHMDM {R is not reflexive}
                        1. NYHMFU which seems possible
                      2. NYHMEV {i has only 1 value}
                        1. NYHLR7 which is extremely rare (as the structure would contain little content except say for say nested quote-protection)
                    2. NYHLRF #NYHIUW does not seem to do much useful, a problem with  #NYHIUW possibly; how to fix? Possibilities:
                      1. NYHR2E define non-reflexive in terms of reflexive R as {(x R y) and NOT (y R x)}
                        1. NYHR6B does not have  #NYHQI0 so good.
                      2. NYHQJR replacement #NYHPUB has #NYHQI0 so don’t.
                2. NYHPUB {for every i, {S1[i] R S2[i]} or {S1[i] = S2[i]}} and {for some i, {S1[i] R S2[i]}}
                  1. NYHMMY where ‘or {S1[i] = S2[i]}’
                    1. NYHQCZ is to help solve  #NYHMDM
                      1. NYHMOI as for  ‘a sum S1 is less-than a sum S2 if respective augments pair-wise are less than OR sane as’
                    2. NYHQI0 problem is the ‘=’ operator here is readily stricter than a congruence intended by R
              2. NYHJB8 ‘array or equivalent’ includes:
                1. NYHJD4 very commonly an application A of a function to its arguments, where say A[i] is the respective argument except that A[0] is the function.
            2. NYHHF7 ‘‘motivation or source or change’ ‘in reverse start order’’
              1. NYHHGG since I couldn’t find a formal term that defines this, my invention.
              2. NYHHFH ~10 min ago, seeing https://www.google.com/search?q=congruence+closure find 1 (http://www.cs.berkeley.edu/~necula/autded/lecture12-congclos.pdf) slide 2 (‘Theory of Equality’) list the 3 properties of equivalence relation plus 1 additional labeled ‘congruence’
              3. NYHHNP In bachelors thesis (on memoized evaluation) else masters thesis, I probably defined something similar.
            3. ‘‘name’ ‘anew’
              1. NYHIN9 ‘substitutive ’
                1. NYHKQC ‘substitutive’ from #NYHJMU
                2. ‘‘rendering’ ‘anew’’ ‘‘congruence property type’
              2.  
            4.  ‘per def’
              1. NYHJJS ‘same or similar’ ‘sub’
                1. NYHJ80 <0 ‘1’  ‘‘congruence property type’
                2. NYHI78 0
                  1. NYHI91 my finds
                    1. NYHI7L ‘Wikipedia’  find not.
                    2. NYHI80 Google Searching: find not
                3. NYHJO7 >0 common
                  1. NYHJMU When R is a full ‘congruence relation’, {much of https://en.wikipedia.org/wiki/Substitution#Science_and_mathematics} for an equivalent.
  6. annex
  7. ‘motivation’
  8. ‘success of this’
  9. NWZ077 ‘post history additional’‘‘post history additional’ ‘in reverse start order’:’
    1. NYHZUI ‘{post.status.snapshot{;date ’20151127Fri1557pst‘;after ID ’minutes 0‘;revision ’11‘;version4.0‘;words ’5661‘;as ’before finished with split just got Chrome ‘Aw, Snap!’ so on reload got ‘There is an autosave of this post that is more recent than the version below. View the autosave giving updates {move out #NOKXS2 thru #NX7H28 + diffs #NX090F thru  #NX1OJ9 (diff sync failed) + move out #NX1HOJ thru #NX5H9E with diffs & ending at #NX5JL3 + history #NYENE9 thru #NYEMSB} + ‘Post restored to revision from November 27, 2015 @ 23:40:24 [Autosave]’ + ‘The backup of this post in your browser is different from the version below. Restore the backup.’ which included {~15 characters more after #NYHZ2Q} & looked current on good look‘;do ’continue editing starting with #NXS2YK with
      694 replacements‘}}’
    2. NYENE9 split of this post
      1. NYENF8 into subposts
        1. NYENND graphs overall –this article
          1. NYI0JE ending at #NYHZUI, for organization, added  #NYFKJD+#NYFOVR +#NYFOMB + #NYHSK0 + #NYGL37 + #NYGN07 + heading #NYFKHL + #NX1S4P expansion + #NX1S6T expansion + #NYGKUH + #NYFPSS grouping + #NYHGMI + #NYHJA3+  (not finished moving out #NX5JL3 and following)
        2. NYEZ4O compare & review
          • NYENFS ‘motivation & review’
          • NYENG2 ‘displacement/offset & categorizing’
        3. NYENHX ‘Pretty Link’ stuff moves to name & ref  –done into /5160#NYEO3T
        4.  
    3. NYEMSB ‘{post.status.snapshot{;date ’20151125Wed2022pst‘;after ID ’minutes 0‘;revision ’10‘;version3.1‘;words ’8852‘;as ’just got Chrome ‘Aw, Snap!’ so on refresh got ‘There is an autosave of this post that is more recent than the version below. View the autosave giving updates {#NYDNSD thru #NYDWWS + history #NYDRAJ: very few updates for another crash} + ‘Post restored to revision from November 25, 2015 @ 21:35:27 [Autosave]’ + ‘The backup of this post in your browser is different from the version below. Restore the backup.’ + ‘Post restored successfully. Undo.’ which gets the latest few characters ‘–also in spacetime so not’‘;do ’continue editing starting with #NXS2YK with
      1107 replacements; eeks as we got only 800 words out of the last edit before another crash‘}}’
    4. NYDRAJ ‘{post.status.snapshot{;date ’20151119Thu0945pst‘;after ID ’minutes 0‘;revision ’9‘;version3.0‘;words ’8062‘;as ’just got Chrome ‘Aw, Snap!’ so on reload got ‘There is an autosave of this post that is more recent than the version below. View the autosave giving updates {#NX5K6W moved + #NYCZD5 thru #NYCF3J + #NYD0IU thru #NYCVBG + #NYCTBF thru #NYCARG + history #NYCEZ9} + ‘Post restored to revision from November 25, 2015 @ 16:36:11 [Autosave]’ which looked very current on good look‘;do ’continue editing starting with #NXS2YK with
      1056 replacements‘}}’
    5. NYCEZ9 ‘{post.status.snapshot{;date ’20151124Tue1539pst‘;after ID ’minutes 0‘;revision ’8‘;version2.0‘;words ’6770‘;as ’as editing crashed from either Chrome or OS bug, on reload got: ‘There is an autosave of this post that is more recent than the version below. View the autosave’  with {updates title + #NV8LHT + #NXKHDI thru #NX2XMJ + #NOW3JL thru #NOW3RB (a move) + #NXKCP5 thru #NXKCSN +  history #NXKBWQ thru #NXKBVP} + ‘Post restored to revision from November 9, 2015 @ 21:44:44 [Autosave]’ ‘;do ’per NY0WO6 with _ replacements then continue editing‘}}’
    6. NXKBWQ updates: move #NOM5R5 + #NXKC3N +  thru #NXKCSN + #NXKHDI + NX91CQ
    7. NXKBVP ‘{post.status.snapshot{;date ’20151109Mon1138pst‘;after ID ’minutes 0‘;revision ’7‘;version1.0‘;words ’6597‘;as ’Due to OS forced restart NXGEHV, didn’t properly save so on reload got ‘There is an autosave of this post that is more recent than the version below. View the autosave’ giving updates {#NX7HMB + #NX7HAP thru #NX7H28 + #NOM6YI thru #NVWNYD + #NWWOPP thru #NWWP51 + #NX75OM thru #NX75QA + #NX5JUV thru #NX5LMA} getting ‘Post restored to revision from November 3, 2015 @ 07:03:47 [Autosave]’ which has recency {unknown on quick look as no recent memory but probably ok}‘;do ’continue editing‘}}’
    8. NX75JF updates: many + {move ‘‘in comparison to’’ from /5129 to here /5138}
    9. NX6CID ‘{post.status.snapshot: date ’20151101Sun2225pst‘;after ID’ minutes 0‘;revision ’6‘;version0.6‘;words ’6102‘;as ’got ‘Aw, Snap!’ so reload getting There is an autosave of this post that is more recent than the version below. View the autosave’ has notable {{#NX5E7A thru #NX5GQS}+{#NX5E82 thru #NX5M7Z}} so do getting ‘Post restored to revision from November 2, 2015 @ 06:17:42 [Autosave]’ and no more but looks current including recent #NX6C4P ‘;do ’continue editing‘}’.
    10. NX5BUS ‘{post.status.snapshot: date ’20151101Sun1813pst‘;after ID’ minutes 0‘;revision ’5‘;version0.5‘;words ’5208‘;as ’got ‘Aw, Snap!’ so reload getting ‘There is an autosave of this post that is more recent than the version below. View the autosave’ has significant diffs including {#NX2XMJ thru #NWZ0W6}+{#NOKXS2 thru #NX4MTW}+{#NWW5RR thru #NWWE2R}+{#NX4GW3 thru #NWYEKT}+{#NWXYW2 thru ~#NX4EZK}+{#NWY6L8 thru ~#NX05EW}+{#NWXRAS thru #NX2OLK}+{#NX2PZ7 thru #NX0BBK}+{#NX28D7 thru #NX0K6S}+{#NX1ZHK thru #NX22LL}, select getting ‘Post restored to revision from November 1, 2015 @ 16:21:43 [Autosave]’ and ‘The backup of this post in your browser is different from the version below. Restore the backup.’  doing restores to last point adding #NX59H3‘;do ’continue editing‘}’.
    11. NX3JE4 split out #NX3I60
    12. NX22SY continue latest entries,
    13. NX22RH ‘{post.status.snapshot: date ’20151030Fri1604pst‘;after ID’ minutes 0‘;revision ’4‘;version0.4‘;words ’4183‘;as ’got ‘Aw, Snap!’ so reload then ‘There is an autosave of this post that is more recent than the version below. View the autosave’ primarily showing {add #NX090F thru #NX1ZP8} do restore getting ‘Post restored to revision from October 30, 2015 @ 22:06:14 [Autosave]’ and ‘The backup of this post in your browser is different from the version below. Restore the backup.’  which gives a few changes bringing to latest ending in ~‘aRb or aRb’‘;do ’continue editing‘}’.
    14. NX22LL continue latest entries, mostly noted next
    15. NX02PZ ‘{post.status.snapshot: date ’20151029Thu1408pst‘;after ID’ minutes 0‘;revision ’1‘;version0.1‘;words ’2423‘;as ’significant todo but good to get content moved to here republished‘;do ’Publish 1 then continue editing‘}’.
    16. NX0257 {spellcheck} + {update IDs to latest format: 312 replacements}
    17. NX01TC TODO: finish completing latest entries + proofread + verify links then {spellcheck} + {update IDs to latest format: __ replacements}
    18. NWZMLP for the content moved to here, do NWZNOM: { http://1.jothere.com/wp-admin/admin.php?page=pretty-link&search=5129&size=100 ends up with 12 entries; http://1.jothere.com/wp-admin/admin.php?page=pretty-link&search=5138&size=100 goes from 0 to 8 }
    19. NWYUPJ ‘{post.status.snapshot: date ’20151028Wed2217pst‘;after ID’ minutes 0‘;revision ’1‘;version0.1‘;words ’2548~‘;as ’to do /5129#NWYU94‘;do ’{at time of ID of this entry, so now}, do /5058#NW3WBQ where to get a reasonable template AND source text, from http://1.jothere.com/wp-admin/edit.php?post_type=post pick the post with the highest post #, well, since near enough, pick the source post,  so post with last addition which is the last history entry /5129#NWYU94, creating this post http://1.JotHere.com/5138#NWYUYU then cut {all its content not to be reused here. so including every KCGUID declaration} to, after this, be completed”‘}’.