Phone Conference P1450

1. New Annex-O using Jose's tablular format (attached pdf)

2. Use of parens and tics in expressions (see below). Need an update from the expr-sub-group on getting NO-voter-buy-in.

3. Removal of annex-F. I need help creating a realistic alternate example if we are to remove current one.

4. Syntax for CellGroups (attached pdf)

5. Progress and Status

6. Dot0 reflector and user-group phone call on Friday

Tony's additional rules for use of parens and tics -

1. There are tokens like: 2ns, SIGX, and VAR.

2. There are expressions that are made up of tokens: SIGX+SIGY, VAR+2ns. Tics around these expressions are always allowed, and in some cases are required: GRP = 'SIGX+SIGY'; 01 {
'VAR+2ns' L/H; }

3. There are equations that are made up of tokens and expressions
- equations may be either assignments using the assignment operators =, :=
- else they are boolean using the boolean operators ==, !=, :==, :!=, <>, >=, >=

4.Equations can never be enclosed in tics, only the expressions on either side of the operators
- the following are legal:
        GRP = 'A+B'
        T := 'VAR/2'
        'SIG1+SIG2' = HH
- while to following are NOT legal:
        'GRP = A+B'
        'T := VAR/2'
        'GRP = HH'

5. Parens are allowed inside an expression:
        A/(B+C)
        'A/(B+C)'

6. Parens are required around a boolean equation:
        (\WSIG == H)
        (@@ < 2ns)

Meeting discussion

IEEE meeting clearances

Nothing under discussion or presentation for this meeting was identified

as being proprietary or restricted.

CellGroups
More discussions during the week resulting in a new proposal, placing
CellGroups within ScanStructures. During the discussion of this new
proposal, the group advocated removing the attribute on
'cellgroup'-type chains entirely, and relying on just the scanchain to be
used as grouping. Additional modifications to syntax constructs used
elsewhere but added here is to allow the Base statement without a
wfc-list, as a chain declaration of Base Hex is useful but
coordinating WFCs to internal elements doesn't make sense. Also the
group needs to confirm that multi-bit constructs don't make sense in
this context as well.

clause 18.3, table 8
Proposal to add lowercase h,l,t here accepted.
Events are sticky in this context, and persist across cycle
boundaries. Therefore need to add the x-event to terminate the events
above.
There was some discussion about the '!' event, which was defined prior
to creating an 'S' event which appears to serve the same
function. Therefore the group agreed to remove the '!' event and
replace it with the 'S' event.

Annex O
This new Annex was generated by Tony for consideration by the Working
Group. Decision to use it was tabled for opportunity to review by the
members.

expressions
Tony presented his additions to using parens and tics. There were no
issues identified by the group for this elaboration. This information will

expression sub-group.

Greg identified his action item to document why we need ':='.

Annex F
Some discussion about the request to modify the example here, this is
left as an open issue at the moment.

Status
Tony identified the current completion percentage at 58%, with 125
tbd's remaining.

2nd User Group Meeting
Tony identified there will be a second phone conference 'STIL users
group' on Fri.

Annex N
no significant progress

Meeting ended at 11:05.

AIs

Greg - Statement of Intent on expression syntax and get NO-voters buy in
Tony - work with Rohit to resolve the timing expression issue described above
Bruce - rework Annex-N to clarify the use of labels and X statements
Tony - incorporate Jose's table into Annex-O
Peter - DM-5 "What is the nature of STATE_ELEMENT?"