Attendees: Ric Dokken, Scott Franzen, Carey Garrenton, Greg Maston, Jim O'Reilly, Ernie Wahl

Line and clause numbers if any are with regard to STIL.4 syntax document D02 dated July 11, 2016.

================================================================================
OLD BUSINESS:

1. Clause "32. TestType Definition":
    REPLACE: For each standard-defined test-type, STIL.4 or STIL.5 shall describe its function and how it uses its parameters to perform that function.
    WITH: Each standard-defined test-type shall be accompanied by a description of its function and how it uses its parameters to perform that function.
          That description should enable replicating test results across various ATE with identical electrical properties.

2. Insert in clause "21.1 Literal Values" after 2nd paragraph (rewritten from May 9, 2016 doc, Line 662):
    User-data AMPERES, CELSIUS, DECIBELS, DEGREES, FARADS, HENRIES, HERTZ, METERS, OHMS, SECONDS, VOLTS, and WATTS represent literal values with appropriate units, e.g., 100mA for AMPERES. PERCENT represents an integer or REAL followed by a percent sign, e.g., 5%. REAL represents a floating point number without units, e.g., 0.05.

3. Add "Node" to clause "3. Definitions":
    used to describe a node in a directed flow graph (flow-node) or an electrical node in a circuit

4. Syntax BNF inconsistently uses ::=, :=, and =, 7/5/2016 consensus: use ::= for BNF

5. Meta-type "next_stmt" is not defined in Syntax Document
================================================================================
CONSENSUS:

SigGroup.doc:
1. Line 9: Change "in the resolved expression" to "in the SigGroup".

Syntax doc:
2. "Table 13 "Parameter Directionality Semantics" and other specifications describe behavior, not implementation

3. Consider STIL.4 specification changes that make "In SigGroup GRP1 = 'grp1';" a legal line. Associated issues:
  a. "Table 13 ”Parameter Directionality Semantics": what is the rationale for "Out" being pass-by-value?
  b. "Table 6 ”Large Data Structure Parameter Types" and "Table 7 ”Integral and Small Structure Variable and Parameter Types":
     what is the rationale for keeping these two tables separate or consoldidating them?
  c. Outline effect of removing the constraint of passing Table 6 types as InOut
  d. Take into account need for pass-by-value and pass-by-reference illustration via parameter defs:
    In    Integer meas = spec.cat.var.Meas; // By value:     "spec.cat.var.Meas" won't change
    InOut Integer meas = spec.cat.var.Meas; // By reference: "spec.cat.var.Meas" may change via assignment to "meas"
================================================================================
ACTION ITEMS:

Ric: CONSENSUS item 1
Carey and Ernie: CONSENSUS item 3, make recommendations
================================================================================