ascribe will be charter beta client - here is [**ascribe**] with latest postings
BMF versions = _release.html and  [***]
  1. index - holds the main menu (which introduces the web app) - old index
    1. navhdr.txt - cites links to formlist
    2. footer.txt - cites 3 orgs sharing credit
    3. agencyhdr.txt - cites links to formlist and specs
  2. Specs on the system when done
    1. Schedule - 6th version on 11/23; added it to 11/21+2 draft 5
    2. Use Cases - lists how forms metadata will be used and by whom
    3. Rule Base - overview of form-field-data-rule interactions
    4. Rule Syntax - 11/21 plans/specs on a release of new commands
    5. The Stack - diagram of the code layers in the web application
    6. FormBase - 9/5 plans on JSP List supporting use cases B & C
    7. Ontology - overview of what Topic types we need to define first
    8. Expansions + agency - optional claims and a Product Plan
    9. Time Line - the top level organizer for each incident is time
    10. SIL Admin - interfaces for IT, QA and MDs at future customers
    11. Packets - naming for /scripts/forms/ that directs their storage
    12. Domain - directed design paper for wink, planning
    13. Machine - Mode paper for DM, planning
  3. Prototype  - built for bosmed using tiny tim - CAREFUL - SHARE CHANGES?
    1. Upper ontology using ctm.xtm - a placeholder (mostly ignored?)
      1. booting includes shared/ensureIndexSet.txt used in many JSPs
        1. ensureContext.txt - checks for Indexset or forwards
        2. ensureAccess.txt - calls above; checks focus or forwards
        3. bootformbase.txt - ensures 3.1.1-5, even today, using scripts
      2. review it here - uppermostwords.txt - run it here
      3. review it here - middle: bosmed.txt - run it here
      4. review it here - debug: form access.headache.txt - run it here
      5. review it here - debug: form painkiller.txt - run it here
    2. formlist.jsp - provides lists of links into formbase - a good baseline
      1. formlist.txt - ensures a loaded TM - lists forms type/ins
      2. this boots using 3.1.1.3 that requires focus
    3. formbase.jsp - displays a form instance given, or new if its type is
      1. formbase.txt - defaults on fields now come from loaded TM
      2. this boots using 3.1.1.2 that requires focus
    4. scriptfield.jsp - posts a form (re)defining field scripts like those under 3.1
      1. scriptfield.txt - defaults come from loaded TM - see jsp? below
      2. this boots using 3.1.1.2 that requires focus
    5. makefield.jsp - usually hidden: shows textbox for data posted by
      1. makefield.txt - uses no defaults, but does require TM using below
      2. this boots using 3.1.1.1 so that GUI can call it using t0 rules.
Until write works, we cannot only create incidents and formsets, not save them
x/x? - Lex - understand example logic enough to use it in packet loads
x/x? - Lex - fix the IndexSet/example logic to save an XTM file ASAP
x/x? - Lex - need to redo boot and split into two options - fast or folder

Until HAS1 works, we can dump makefield output only into files, not context
2/x? - Lex - HAS1 required before ok to post changes in role players
2/x? - Lex - test Modeler for t0= access.  Be nice to really know it works!
2/x? - Lex - add page-timing and JVM memory-manager debugs
2/x? - Lex - fix formlist.jsp (at least?) to show "Display names"
2/x? - Lex - fix formlist.jsp to time-rank form instances

Forms Editor must generalize makefield.jsp to add/use a basescript each form can apply
2/x? - Lex - redo makefield so each field APPLYs a base script to posted parms
2/x? - Lex - base script to APPLY can itself be a new parm, set on scriptfield.jsp
2/x? - Lex - scriptfield.jsp must make domain & property become fixed links

The application of scripts to args is simple to do, finishing RUN may not be
2/x? - Lex - recall/fix RUN - it needs a stack, so we can continue (and add args)
2/x? - Lex - RUN becomes APPLY - add/support optional $ARGS[n] macros

The migration of code into HL7 will take a refresher course on what it is doing
2/x? - Lex - adjust the scripts created & ALL CODE to use (e.g) HL7Action names
2/x? - Lex - at the same time, clean out scxript/forms and add HL7-like forms


Sa20 - Lex - add x to /cms/xbosmed/ in /exhibit/ & /agency/ - to hide posted files
Sa20 - Lex - cms /ascribe/ can them get these changes, roughly in order:
Fr20 - AFTER I find a new site host, I post /cms/ using /agency/'s simple version
Su15 - Lex - I learn site host must change, edit section above to help plan it

We04 -Lex - progress!: I discover putty works, and learn how to ftp via composer!
1/04 - Lex - rename the posted javasrc - just in cases BMF machine allows breakin
1/04 - Lex - copy this ascribe folder from BMF, but [*]=posted not aok yet - see red
1/04 - Lex - using Mozilla, post a new hdr/ftr = HL7 scribe, a Lexikos utility

Su01 -10B - write overlong, complaining email to SM - re-ask Lex $ and mtg
Sa31 -10B - declare charter code used in formrules; recompile locally to test
12/31 -10B - decide SM needs ONLY 5 interface classes of Modeler source
12/31 - Lex - finish analyzing the new code needed for <select/<input controls
12/31 - Lex - finish awful process of shifting LLC registraion => NO lexikos move
Fr30 - 10B - send my Dec hours, THEN expand BosMed log as formal record
12/30 - 10B - SM decides he will NOT pay me via Lexikos - I get VERY PISSED OFF
12/30 - Lex - analyze the new code needed for select => java for <select/<input
12/30 - Lex - above now for HL7scribe.com - offers ways to capture/export HL7 Actions