Approval to submit D22 as the next ballot draft:

All present were in favor, Greg held Peter's proxy for approval as well. The following is the cover letter that will be submitted with the invitation to balloters:

You are requested to, once again, review the document for IEEE Std - 1450.1.  Since the last ballot recirculation which completed in Jan 2005 the working group has addressed a very small number of issues (summarized below). The new document (draft D22) has change bars that accurately indicate which
lines have been modified since the last ballot re-circulation. Please confine your comments to these changes.

The following is a summary of the changes made in D22:

1. Change bars indicate all lines that have changed since D21. More detail is available in the D22-ballot-resolution document.

2. NO changes have been made to any syntax definitions, only to the explanation of the semantics.

3. All code examples have been run through a STIL parser (provided by Source-III) and corrections have been made to make them compliant with the syntax definitions.

4. Sub-clause 5.2 (Expression delimiters) has been slightly ammended. Whereas, in D21, it stated that some statements required delimiters, it now states that delimiters are required for complex data streams where
expressions are embedded with other data. A new set of examples has been added illustrating complex data streams.

5. Sub-clause 5.5 (Expression processing) has been completely re-written per suggestions from Don Organ. The new write-up more accurately explains the processing rules. This is the same intent as in D21, but was not explained well enough in the prior draft.

6. Sub-clause 5.8 (Logic expression) has been clarified by the addition of a new paragraph stating that this is a logic expression of the design, not of the waveforms in STIL.

7. Clause 9 (Variables) has a new rule added that states that variables that are defined in the global block may not be overridden in a named block. This is to allow STIL parsers to be able to rely on the definitions that are in this global block not to change.

8. Table 13 in clause 15 (PatternData) has been updated to clarify the operation of the backslash operators.

9. Annex F has been replaced with a new example. This change was done to avoid confusion with 1450.6 (CTL) which has a similar example with a different implementation that is more appropriate for embedded cores. The new annex F does not use shared scan chains, and is a better example of an application using the AllowInterleave statement.

New item from Jose:
Jose identified a confusion between the .1 definition of logic_expressions supporting expressions, and the .6 reference which
appears to define them to be signals only - however an example in .6 shows an expression. Current understanding of the .6 requirements are that these constructs should be expressions and if .6 references them as signals and uses them as expressions, they need to review their spec.

Rohit's response:

"The statement you are looking at is datatype - just like clocks and scan ins scan enable needs to be in the data type. We have already removed the associated relation statement when dot 1 put in the statement in the scan str."

Next direction:

Tony proposed that the next meeting of this group focus on p1450.3 as there will be no p1450.1 work until after reballot results are returned. The members present agreed to this.

Meeting ended at 10:25