What are these 6-digit codes before every point & item?

^LL40IP: =What are these 6-digit codes before every point & item?:

1. ^LL40KY: IDs to date-stamp & uniquely-reference most anything -that gives some explanation
2. ^LL41TX:  my invention, with prototypes starting around 2004.
3. LXJX8Q=to be released ASAP for general public use (so anyone can make & include their own IDs)
4. LXJXBY=in alpha-test of the 1st release, including
   1. LXJXH1=(making IDs & outlining nearly-disappear into the background, as humans much prefer it displayed, while still enabling it to be found when-needed by humans & machine-search) is
      1. LXJY8A=still under regular development (see Could the presentation of this info be improved?)
      2. LXJY8U=very-difficult or impossible on nearly all Web 2.0 sites due their stripping of formatting by HTML & CSS & JavaScript.
   2. LXJXOH=This stage will & is taking up to 10 years, due to (my part-time effort on it from no funding) and the inherent difficulty LXJXTT.
5. ^LL41HJ: useful in numerous situations:
   1. ^LL41JR: as in general
      1. ^LL41ML: gives an ID to an item which is often fairly-globally unique.
      2. ^LL418E: =benefits of always & immediately doing: If placed on an item when it is created/entered whenever an ID might be necessary has notable benefits:
         1. ^LL41A5: it time-stamps when the item is created, including soon an ID-to-date converter web page will be offered so one can get, from the ID, the exact time down to the second.
         2. ^LL41BC: in the item one say a relative time (as “now” or “2 hours ago”) and still specify exactly –for  the time-stamp of the ID gives the exact time being referred to.
         3. ^LL4CJJ:it insures all references to the will have the ID embedded so then
            1. ^LL4CNH: the link can be found & fixed if ever broken.
            2. ^LL4CNU: all references to the item can found (usually automatically) by searching on the ID.
         4. ^LL4CRA: it creates a uniform & short ID/serial-# for all items.
      3. ^LL41D9: A future version will allow one to get, from the ID, the exact user who created it.
   2. ^LL41ML: as on text (as and ID on every paragraph, or document, or sentence, or heading, or table or column or row or table-cell)
      1. ^LL40ZW: any text  which has an ID attached offers several benefits:
         1. ^LL41S8: all the general benefits mentioned above, including time-stamping & time-referencing, plus
         2. ^LL4131: Instead of having to quote arbitrary spans of text (and then have those quotes go out-of-date if the text changes or one got the quote wrong), one can much more compactly refer to some text by just quoting its ID (and only-optionally quoting the text, which might change anyway), and find it just by searching (as Google-searching or desktop-searching for that ID) and find it even if it’s moved to a new website or even if the text has changed.
         3. ^LL42VG:And then by making it easier to reference text, it then
            1. ^LL42YT: it then makes it easier to avoid repeating but rather encourages reuse of writings
            2. ^LL431D: which then cuts cuts down on textual clutter and enables standards which are more consistent & developed faster.
         4. ^LL41XT: Helps track & credit authorship plus cut-down on plagiarism (as when the text is copied, the IDs are generally copied as well).  The better tracking (of where words came from & went to) then also enables better authorship tracking & crediting.
      2. ^LL41XT: Great for any documents which go thru revisions (as wikis, instructions, rules, & increasingly blog-posts) , as references to IDs will still be findable even if the text is moved or rewritten.
      3. ^LL45FY: Especially great for any sort of rules & laws & guidelines, including military doc, as every point & subpoint of a rule/law instantly gets ID/code so one can easily write “In (accordance- with|violation of (rule|point) x”.
      4. ^LL45L5: Great for manuals & instructions, as each point instantly gets an ID so one can say “See/follow/do step x”.
      5. ^LL421W: Good for messages, especially email, as then:
         1. ^LL424S: One wanting to refer to a portion of a message need not quote all the text there , just the ID (and optionally the text, but just a little bit).
         2. ^LL426S: since messaging is a snapshot of dialog and dialog is where a lot of (indeed possibly most) good ideas & sayings get invented, allows better tracking of where these good sayings & ideas came from (by just referring to the ID) and where they got used to (by the copying of an ID).   And again since many/most good things start from dialog, this could lead to significantly better crediting where credit is due (per IDs helping credit & track, explained above).  The paragraph’s ID allow one to refer to exactly where that “good saying” or “good idea” or “pearl of wisdom” came from and by whom.
   3. ^LL4C3M: On ID each file & folder and global-function and global-variable, using say the syntax “<name/>_<id/>” where the <name/> may change but <id/> remains constant. This allows these all (files, folders, variables, and functions) to be freely renamed & moved while still being able to restore broken links, sometimes automatically.
   4. ^LL4CGT: On each address book contact (as most electronic address books hide the internal ID) to track the contact
   5. ^LL4CXY: On each  http://eTag.JotHere.com (JotHere’s standard for a email address used for portably categorizing/tagging instead of emailing, often given to each address book contact)
   6. ^LL4BXL: On physical items (as a phone or device) as a kind of serial #, including it’s shorter than most serial #s, and being universal, works well with other uses.
   7. ^LL4CBJ: Note to make use of IDs, one does NOT need to put an ID on everything (which one may not want to because that takes time & they are unsightly) but note benefits of always & immediately doing.
6. ^LL47QH: I and a few other alpha-testers have been heavily using them on most everything in their present form since 2009.01.01 (over 2 years), and in a longer form in the years prior to that.
7. ^LL45S7: So everyone can author with these IDs, The web page & macros I’ve built to generate & insert IDs I plan to release shortly to the general public,
   1. ^LL45VM:–after refinement is complete, including
      1. ^LL45WH: the generator noting who created each ID
      2. ^LL45X2: a code system which is more scale-able (current system would only support a thousand people w/o ID conflicts).
      3. ^LL45YV: cross-platform, robust, ID-insert macros
      4. ^LL463I: Better ways to display & hide the IDs so they are not so unsightly.
8. ^LL40MC: To explain ones use of them in a document, prefix the document with say:
   

   ^LL3YGR: What are these 6-digit codes before every paragraph & point? They’re IDs to date-stamp & uniquely-reference most anything –see that link for more details.

9. LXJXTT=to build the tools (the software) to generally enable such augmented text is inherently very hard!
   1. LXJYCD=may appear easy (just insert IDs into text) but is much more complex
   2. LXJYD7=involves
      1. LXJYDR=balancing the needs for machine & human parsing & understanding, something only recently being done with microformats.
      2. LXJYDI=subtle, comprehensive, & integrated modifications of the whole text-processing process: in editing, display, storage, linking, & indexing
      3. LXJYKG=testing & supporting a variety of existing popular publishing platforms, notably Web 2.0 sites, so to be generally useful.
      4. LXJYEL=selling humans on a notably different way of writing & composing & authoring.
10. ^MJO3C1: Linking text which is labeled with an ID
    1. ^MJO3D8:  Does the text have an <a id=”..”> tag?
       1. ^MJO3EM:  Yes
          1. ^MJO3FB:  –the typical & ideal case.
          2. ^MJO3FG:  Use href form “<url/>#<id/>”
             1. ^MJO8YY:  Real example: http://1.JotHere.com/401#MJO8YY to link to this point.
       2. ^MJO3GH:  No
          1. ^MJO3HS:  –as were sites trip out the <a id=”..”> as with user-text on Meetup.com
          2. ^MJO3I2:  the MJRef solution
             1. ^MJO3LR:  Usage: http://1.JotHere.com/MJRef?q=”<id/>”(+<keyword/>)*
                1. ^{MJO88I:  MJO89Y:}  (+<keyword/>)*
                   1. ^MJO8CJ: needed when <id/> naturally occurs elsewhere for something which is not the intended target
                      1. ^MJO8CU:  which happens fairly routinely as IDs are fairly short (currently just 6 characters).
                   2. ^MJO8CX:  each should be a word that occurs within the target text:
                      1. ^MJO8GH: within say 50 characters of <id/>
                      2. ^MJO8HE:  always and literally, except a variance the search engine would correct for as possibly word ending as “attending” vs “attendance”.
                2. ^MJO6HU:  Originally: http://1.JotHere.com/MJRef?q=<id/>(+<keyword/>)*
                   1. ^MJO6JO:  but now found http://1.JotHere.com/MJHref?q=LTDSHF+Meetup  returning quote(Showing results for LTD SF Meetup<br/>Search instead for LTDSHF Meetup); but http://1.JotHere.com/MJHref?q=”LTDSHF”+Meetup works, as used in real example.
             2. ^MJO41Q:  Pros thru cons:
                1. ^MJO3V0:  HUGE PRO: will not break even if the text is moved onto another of a different website.
                2. ^MJO92O:  Very notable PRO: allows click tracking.
                3. ^MJO94F:  Very notable Pro: could be used to do ad display on every click
                4. ^MJO3WV:  Notable PRO: Supports multiple copies of the destination text: finds all instances provided only the text is found via public Google Search.
                5. ^MJO6TR:  Tiny con: should be tested in an Incognito Window to simulate what other will see as Google search guesses what you the author want so will be more accurate
                   1. ^MJO6W0:  Example case:  for LTDSHF+Meetup it will guess you mean “LTDSHF”+Meetup
                6. ^MJO406:  Usually tiny CON: Seems to require ~1 day for newly appearing text (be it copied or moved or created again) to get indexed so found.
                7. ^MJO69Q:  Small con: often requires including a keyword which won’t change.
                8. ^MJO3TK:  CON: Initially & currently works just for IDs on the public web.
                9. ^MJO62Z:   BIG CON: often the most recent version is not obvious & not returned first
                   1. ^MJO664: For text on repeating event listings, indeed they have multiple versions.
                10. ^MJO987:  Fairly Huge Con: user may find the indirection (1 or 2 additional page displays and time wait for that) very annoying
                    1. ^MJO98I: Most especially for any link to a target on the same page: now instead of taking ~1/4 sec to scroll the page it now could take maybe ~20 secs for 2 page loads, just to bring him/her back to the same page just in a different spot, and the user will likely be somewhat disoriented as not realizing (and not to easy to quickly tell) that indeed this is the same page.
                11. ^MJO62F:  HUGE CON: getting to the particular text/tagged-item is tricky as while the search engine usually lists the start of the matching text, the user still needs to know to & copy (into clipboard)  the ID then click on the link then page-search for it on that page, which many/most will not know to do.
             3. ^MJGPXPL: first implemented by this Pretty-link redirecting to https://www.google.com/search for 1st use at  use on http://meetup.com/OCAndroid/events/106978332
             4. ^MJO8KY:  Pretty-link “Parameter Forwarding Enabled” must be turned on.
             5. ^MJO8OU:  via https://www.google.com/search
                1. ^MJO8PL:  the “https” rather than http seems to be what the brower’s address bar web search seems to prefer & indeed add security for at little cost for this small amount of encryption.
                2. ^MJO8RQ:  the “www.” is optional but what the query redirects to so saves the time of doing this replacement.
             6. ^MJO8T4:  searching for the “:” in the target, as “<id/>:”
                1. ^MJO8UJ:  via Google Search
                   1. ^MJO8US: so far has seemed impossible from my tests.
11. Post history, in order
    1. ^MJO383:  prior history needs reconstruction
    2. ^MJO39P:  1st editing this with WP3.5+ which corrupts & keeps corrupt <a id=”..”>-tags until WP fixes this.
    3. ^MJO8XZ:  added this history section
    4. ^MJO9IB:  added Linking text which is labeled with an ID most notably the MJRef solution; pst2013.03.14Thu1537.