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 September 21, 2015.

Have Enum syntax changes been added ?
* Remove PassActions and FailActions from TestBase

================================================================================
CONSENSUS:

*Line 5183: add word "in"

*Line 5185 - 5224: Accept as is but move lines 5198 - 5220 to examples section
(example in black, associated commmentary in red).

*Line 5226 - 5233: Delete

*Line 5242 - 5250: Delete single & double strike through, accept rest as is

*Line 5245: Change occurrences of "next_ stmt" to "next_stmt"

*Line 5245: Only action_stmt can "stop the test flow and set a bin"

*Line 5245: Or stop the test flow and set a bin

*Line 5261 - 5268: delete

Line 5291: Add PostActions example

*Page 137 footnotes: Accept as is
================================================================================
ACTION ITEM: Ernie to make changes as per CONSENSUS above.
================================================================================
REJECTED:
--------------------------------------------------------------------------------
Line 5163: use "PORTNAME" instead of "PORTLABEL:" because 

  - the colon terminator is extraneous in new port-name/label position

  - "LABEL" is used in STIL.0 to describe flow control target locations

  - some smart editors automatically indent colon-terminated labels differently
    and labels are generally go-to targets which is not the case in this
    context.

WHY: 
  - Dropping the colon is inconsistent with STIL.0 where the only lines
    permitted to start with an optional user-defined identifier require a colon
    terminator.

  - Using NAME and LABEL to differentiate between a tag and a flow control
    target was deemed unimportant.

  - Smart editor EMACS is programmable.
--------------------------------------------------------------------------------
Line 5247: let PORTNAME use stil4_alnumid syntax .e.g. 1GHz because speed
binning paths are common, and strike "by any other syntax block".

WHY: inconsistent with STIL.0 precedent.
--------------------------------------------------------------------------------
Line 5249: change "Setting the last port’s Boolean expression to True is a means
to guarantee a valid exit for the FlowNode" to shall be required.

WHY: Ric's customers explicitly rejected the requiring a literal value of True
on the last port statement. At least one port boolean_expr must return True.
--------------------------------------------------------------------------------
Line 5261: keep first two sentences ?

WHY: a standard should be specified in positive terms, i.e., what syntax means,
as opposed to what it doesn't mean.
================================================================================