Jan 082012
 

 

  1. LXISUB=subject=

    1. LXIMVS=lastMod_version_status=pst2012.02.02Th1022 0.86 constructing actively
    2. LXITTL=title=our posts’ common terms http://1.JotHere.com/LX93Y7
    3. LXAGVQ=“common terms” include fields, variables, and constants.
    4. LX93Z0=“our posts” are:
      1. LX943X=posts & comments of http://1.JotHere.com
      2. LX9444=event listings/posts of  Meetup.com & similar event post style LX9STY)
      3. LX945F=Ideally many other HTML documents.
  2. the Details=

    1. LXIHDU=ID of a Term’s (Definition vs particular setting)

      1. LXIIA1=Possible assignment includes, from most to least preferred:
        1. LXIIRO=To each new non-reused setting needed, assign a new else replacement ID which is
          1. LXILEX=a fresh ID but with the last 3 characters set to match the definition name (indeed same as used on the definition if that’s good nemonic)
            1. LXILH9=Notable Pro: ID is somewhat usable by itself.
            2. LXILFV=Tiny con: Some conflict risk, but that’s notably with the definition which is easy to check.
            3. LXILKU=Now started doing this, replacing LXIKQQ
          2. LXIIJ7=a fresh standard ID.
            1. LXIIV1=Pro: no conflict possiblity
            2. LXIKS1=Tiny pro: No ID computation.
            3. LXIIKR=Small con: the ID isn’t pretty.
            4. LXIITL=Small con: If a replacement, ID gets a falely new date.
            5. LXIKQQ=Now started doing this, replacing LXII8W. Outdated by LXILKU.
          3. LXIIM3=an increment of the definition ID, by some increment scheme
            1. LXIIW9=Small pro: Don’t need to remember the the mapping between definition and setting, but probably a good idea to have the mapping
            2. LXIK7C=Tiny con: the ID is not as pretty as original, but close.
            3. LXIKAQ=(ID of setting)=(ID of definition)+(setting #,an integer >= 1)
              1. LXIKKQ=Tiny con: conflict possiblity, but only in a series of rapidly generated terms.
        2. LXIIBJ=Make the setting of a term with ID “x” be say “x_setting_1” or “x.1” or other extension of “x”.
          1. LXIIE0=Notable con: Makes IDs which are derived IDs, so longer (bad for formatting, since IDs are of fixed width) & by some ID derivation system.
          2. LXIIHT=Con: Conflicts could happen if the extension ends up wrong or accidentally duplicated.
        3. LXIHIW=The ID for the setting (from say id=”LX3MVS“) is the same as the ID for the definition (from say <a href=”LX3MVS“>…</a>)
          1. LXIHZ0=In this example, I have say HTML code: “<li id=”LX3MVS“><a href=”#LX3MVS”>the</a> <a href=”LX3MVS“>lastMod_version_status</a>=pst…</li>”. .
          2. LXII8W=Currently in effect since say the creation of say title; replaced by LXIKQQ.
          3. LXIHTY=Small pro: HTML can handle this: can distinquish one from the other based on usage (one is a page anchor and the other is a page “file” name) but
          4. LXIHUD=Small con: on this page, specifically in “LX94BQ=term definitions (table)“, it would be handy that the term definition has its own ID as an anchor name, but that’s impossible since in this example and others that anchor ID is already in use by the setting.
          5. LXII1J=Con: it is ugly IMHO to give the setting of a term the same ID as the term code-name/definition, as
            1. LXII3Y=They are closely-related by still different concepts.
            2. LXII4F=Indeed while a term generally-else-ideally has 1 definition, it can can have many settings in some contexts.

LXIDIU=Scroll (horizontally=left or right) by selecting text range going left or right.

LX94BQ=term definitions (table)
LX94CJ= LXIKVO= LX94DX= LX95DS= LX96EX= LX94TB= LX94NN= LX94FQ=
LX94D7= linked name (assending) ref to the 1 local setting, assigned by LXIIA1 example values else (defintion) specified by nearest prerequesites & why uses: 1st & other examples importance further details
LX7OYM= _
  1. (see for title)
  1. LX9MOA=title
LX9MOP=not applicable.
  1. LX9MPG=I started use ~5yrs ago.
_
LXAACE= a change element
  1. (LXA89C=abstract; specifies any one of creation)
  1. LXA8CX=any instance of making)
  2. LXA8EH=any  instance of partial history, in order)
LX9ABY= by
  1. DestinyArchitect
  1. LX9JTV=initial creation
  2. LXA8K9=a change element
  1. LX9JT4=date as doer seems 2nd most universal (can ask him/her for more)
  1. LX9LUP=same as initial creation
LSZCMP= Comparison with Alternatives, from most to least similar
  1. (LX966W=a list of alternatives to that defined by Details, from most to least similar, and for each, how Details compares as it’s pros-thru-cons)
  1. LX9JU3=JotHere post
  1. LX96GN=Details as generally needs to know what something is before one can sensibly compare it.
  1. LX9647=An ancestor doc of here
LXACRE= creation
  1. LXA814=partial history, in order
LX9DAT= date
  1. pst2011.12.30Fr2242=LX22NH
  1. LX9JUL=initial creation
  2. LXA8JM=a change element
  1. LX9JR8=nothing (within initial creation) as a date is perhaps the most univeral point-of-reference.
  2. LXA93Z=motive (unless immediate motive –current exception) as that occurs before date so should be listed before per say partial history, in order.
  1. LX9LUX=same as initial creation
LSZDEF= Definition
  1. definition
  1. LXI6DB=JotHere post
  1. a JotHere post in 2011
  2. this post
LX7DET= Details
  1. (LX95TJ=A list of assertions that specifies & ideally exactly defines, the value of the Subject in all contexts it could/did exist.)
  1. LX9JUA=JotHere post
  1. LX96IE=Subject as one needs the subject area before definitions make much sense.
  1. LX95R5=here =<(“lastMod_version_status= pst2012.01.03Tu0311 3.0 released“)
LX2DTA= discussion thread of all additional aspects
  1. thread for all 3 days
  2. thread
  1. LX9L1G=post
  1. LX9JLD=permanent full URL as this is important to some attendees not just organizers.
  1. LX9LVB=same as post
LX9EIC= entry initial creation
  1. (see use examples)
  1. LX99W1=post
  1. LX99WY=all general attendee items
  1. LX9A7O=replaced separate “post initial creation“.
LXAH8N= event post
  1. (LXAHBC=A post for an event)
LXABG6= featured history+updates, in order
  1. (see use examples)
  1. LXAHEU=event post
LXAFUR= full URL none yet
  1. LXA5JG=a change element if no certain permanent full URL
  1. LXAL35=See LXA4Y3
LXAIMO= immediate motive
  1. LXA8I9=a change element
  1. LXA8XV=by as
    (LXA91Q=Pro: causes one to accurately ask what that agent’s motive was)
    (LXA923=Pro: this info could be derived giving the prior info (if the agent recalled)
    (LXA92U=Con: see LXA93Z)
LX2IFO= info
  1. (content of say a post)
  1. LX9L47=post
  1. LX9J9P=lastMod_version_status (early as possible) since the reader really wants to the interesting content.
  1. LX9LVQ=same as post
LXAINL= initial
  1. (see use examples)
  2. (the span of time defining the creation)
  1. LXA6D3=making
LX9CRI= initial creation
  1. (see use examples)
  1. LX9K0L=post
  1. LX9JO7=discussion thread of all additional is of next more general interest but still some attendees could be interested in the initial parts of this.
  1. LX9LW0=same as post
  2. LXA78S=replaced by separated “making initial” for more flexiblity and to avoid LXA76T
  3. LXA8O0=effectively replaced by creation
  1. LXA76T=this may be a redundant combination because “creation” usually implies “initial”.
LXAJEP= JotHere-style event post
  1. A more exact name for event post
  1. LXAJM3=needed with the context wouldn’t be known w/o clicking.
  2. LXAJMJ=Gives credit to the creating organizatio
LX3MVS= lastMod_version_status LXIMVS=the lastMod_version_status
  1. pst20120103Tu1638 0.1 constructing actively
  1. LX95GH=Subject item 2
  2. LX95GQ=event listing
  3. LX9KG7=source
  1. LX9J4H=display title. (LX9J5W=It’s initially unintuitive & annoying to have this at the beginning as indeed it would be unnecessary when the document is complete, but when incomplete else changing (which is often more typical than not), this is key heads-up)
  2. LX9KH9=Within source, this is required IFF the URL is not to a snapshot with this info.
  1. LX95A9=here =<(“lastMod_version_status= pst2012.01.03Tu0311 3.0 released“)
  1. LX94ST=To keep track of edits in a doc which changes and (is being copied or edited by multiple persons).
  2. LX94T0=To tell how recently something was edited as an estimate of freshness.
LX2LSO= last one
  1. LX9EEU=replaced by previous at Lucy’s suggestion.
  1. LX9L5W=post
  1. LX9L53=was replaced by previous
LY1LNK: link
LXAMKG= making
  1. (see use examples)
  1. LXA62Z=post
  1. LXA7QB=replaced by partial history, in order
LSZMOT= Motivation
  1. LX97BO=Comparison with Alternatives, from most to least similar as one has to know at least existing alternatives before one can really see the motivation for creating something.
  1. LX97B3=An ancestor doc of here
LXABQF= motive
  1. (LXABUK=Warning: Lucy points out that asking one’s “motive” or even “motivation” has off-putting invasiveness feel; suggests something else, as “purpose”)
LX9NUR= numeric URL
  1. (LX9LB3=on Meetup, a URL of the form http://[www.]meetup.com/<Group/>/events/x where x is of the form [0-9]+)
  1. LX9L6K=was replaced by permanent full URL
LXAH2S= not applicable since NOT a copy
LX9MEC= operation (“Copy”, “Schedule a Meetup”, or “SUGGEST A MEETUP”)
  1. (Meetup event creation operation)
  1. LX9LJF=initial creation
  2. LXA8LI=creation
  1. LX9JX4=by as what is done seems next univerally recognized.
  2. LX9K9M=arguably (but not done here) source as one often picks that THEN selects the (copy) op.
  1. LX9LW9=same as initial creation
LY1OPA: other parameters
LY1OPO: our prior one
  1. same as previous
LX9PFU= permanent full URL
  1. www.meetup.com/OCAndroid/events/46041572
  2. (LX9L84=Note n Meetup, a URL of the form http://[www.]meetup.com/<Group/>/events/x where “x” is not-empty but NOT of the form [0-9]+ is a TEMPORARY URL. LX9LFR=To create & use-only the permanent URL, change a RSVP response in any way, including changing just the public comment.)
  1. LX9K1L=post
  1. LX9JIO=permanent short URL as while not nearly as important to the average reader it is so conceptually close might as well put together.
  1. LX9LWI=same as post
  2. LXA4VD=If possibly not permanent, use instead full URL.
  1. LXA4J0=in a post, for when the body/description has been copied outside of the post as to into a (better) HTML editor and its filesystem, this is then helpful/essential to know where that draft came from (esp for when it authoring was paused) and includes valuable search keywords including (the site name, (Group & type (as “event”) name, if Meetup.com), and the post #.
LX9PSU= permanent short URL
  1. http://meetu.ps/6lpws
  1. LX9K21=post
  1. LX9JGJ=previous since the reader generally first wants to know what it is before s/he decides she needs this to share it.
  1. LX9LWT=same as post
LX9POS= post
  1. (see use examples)
  1. LX9LKL=A Meetup event listing description
  2. LX9LL6=ideally a blog post body
  1. LX9LR1=none
  1. LX9KXB=here starting “lastMod_version_status= pst2011.01.03Tu2230 3.0..”
LX9PRV= previous none yet
  1. LX9K2D=post, LXAHE3=no, event post
  1. LX9JEK=(OUTDATED by next)info since:
    (LX9K3L=this is related to that and often quite important (what happened previously) but not quite as.)
    (LX9K3U=it should be deriable for that, so just specified here as an optional convenience.)
  2. LY1OAU:  lastMod_version_status as all other items, including info, apply to present/current so should be listed after previous .
  1. LX9LM9=initial proposed use was replaced by previous post at Lucy’s almost insistance.
LX9PRP= previous post
  1. (means previous where that is a post)
  2. pst2011.02.25Fr: [via OCAndroid: ]SCALE9 (9th Annual Southern CAlifornia Linux Expo) Day 1 of 3 not posted but posted Day2&3!
  1. LX9LO4=post
  1. LX9LRK=inherits from previous
  1. LX9LX2=same as post
LXAHIS= partial history, in order
  1. (see use examples)
  1. LXA7ML=post
  1. LXABL2=replaced by featured (history & updates), in order
LY1REF: refresh format
LXASUR= short URL
LX9SRC= source
  1. (see use examples)
  1. LX9JZJ=initial creation
  2. LXA8PV=a change element
  1. LX9K5M=operation (“Copy”, “Schedule a Meetup”, or “SUGGEST A MEETUP”) as the source generally isn’t applicable if not “copy” and or no copy being made (but debatable: see that).
  1. LX9LXE=same as initial creation
LXASPN= span
  1. LXA6RV=instances of this (generally of time) in making
LX3SUB= subject LXISUB=the subject
  1. (see use examples)
  1. LX9JUY=JotHere post
  1. LX96KW=displayed title is generally athetic but technically none (esp since this even defines title)
  1. LX95AP=here =<(“lastMod_version_status= pst2012.01.03Tu0311 3.0 released“)
  1. LX95IE=Specifies the subject including scope of the container (document)
    1. LX95JG=Ideally exactly (nothing more and (nothing less=completely))
    2. LX95LP=Ideally context-free
LX950Z= the
  1. the (what it links to varies on context)
  1. LX95H7=JotHere post section
  1. LX95AI=here =<(“lastMod_version_status= pst2012.01.03Tu0311 3.0 released“)
  1. LX9538=Provides a copy-then-edit link for the section beginning it appears in as its first element.
LT2NAM= title=title LXITTL=the title
  1. Creating & maintaining _ Meetup.com event listings http://1.JotHere.com/LX90E0
  1. LX99QH=Subject item 2
  2. LX9KKG=source
  1. LX9KLE=lastMod_version_status since
    (LX9KRO=within a post, much of this has already been given (via display post) so more urgent is this other data.)
    (LX9KPA=within source, since this is then generally derivable from the prior info.)
  1. LX9LXQ=here =<(“lastMod_version_status= pst2012.01.03Tu0311 3.0 released“)
  1. LX9KMD=Within source, this is not required IFF it can be derived.
LX9URL= URL
  1. none
  2. http://meetu.ps/6lpws
  1. LX9KD4=source
  1. LX9KDZ=None as always best when it’s available & permanent.
  1. LX9LY0=same as source
  1. LXA55H=If an element of source, generally-most concisely & precisely gives the exact source, especially if a permanent URL to a snapshot.
  2. LXA4Y3=If an element of a post‘s (initial creation or (other=later) a change element/time-span), allows the URL to change but still be found by its prior URL even if the prior URL isn’t forwarded: by then (text searchng for it, as Google or desktop search).
  1. the Comparison with Alternatives, from most to least similar=

    1. .
  2. the Motivation=

    1. LX96Q8=Why this article? Every term, especially these used by forms, should have a good definition if not more (use background, etc). And this provides a systematic way to do so.
  3. the Additional History, in order=

    1. LX93VM=I  (did not know of any JotHere article on this subject) so created this post http://2.loverules.info/654 by:
      1. copying:
        1. lastMod_version_status=pst2012.01.03Tu0311 3.0 released
        2. title=SCALE10x _ Meetup.com groups’ visit http://1.JotHere.com/LX26CM
      2. then set its ID to LX93Y7 which is a new ID
      3. then remove all that didn’t apply and correct the rest.
    2. LXI891=About 3 days ago, table “LX94BQ=term definitions” I tried to force to the left with <li style=”position: relative; left:-5em; right:+5em; width:+10em;”>..</li> but this didn’t work so broke it out of the outline to give it the width.
  4. the Additional Planned Changes, in order=

    1. LX7W4D=none (other than global improvements on all docs, as mentioned here)
    2. LXIEBD=format table “LX94BQ=term definitions” in a way that horizontal scrolling won’t be necessary; this will require advanced CSS.
      1. LXIFII=I just tried <style>th,td,col {display:inline-block;}</style> but sadly IE seems to ignore it and and in Chrome & Firefox, the col-tag settings are then lost.

  One Response to “our posts’ common terms http://1.JotHere.com/LX93Y7”