Phone Conference P1450.3 Working Group
Thursday, Mar 30, 2005 - 10:00-11:30 Pacific Time
Tony Taylor (chair & scribe)
Nothing under discussion or presentation for this meeting was identified as being proprietary or restricted.
subclause 7.5 on scoping
John Cosley questioned whether the scoping rules were consistent with other STIL blocks. Specifically, should a named block replace an unnamed global block, or should the contents of both be merged (similar to the way that global and named SignalGroups operate)? The only reason that Tony presented for full replacement is to make the rules clearer and simpler for a TRC tool to implement. After some discussion it was the conclusion of the (6 people present) group to merge the two blocks and that it is an error if there are any conflicting rules.
Jose Santiago questioned whether a local block rule should take precedence over a global rule. The decision was to not allow precedence. If the rule is to be defined locally, the TRC should be created with this in mind and leave it out of the global block.
Tony will update subclause 7.5.
Now that the definition is all of the syntax blocks is complete, we decided to freeze D11 and start a new D12 with clear change bars.
Tony requested that others on the WG review the descriptions since the re-work has been extensive. (Afterthought by Tony - We should solicit proof readers from the stilusers group ... who could pre-review the document ... and then become part of the dot3 ballot group)
Annex B on fluid concepts
Tony reviewed the modified example (see attachment #1). Although this was the first time the others had had a chance to understand the proposal, it was generally agreed that it is an improvement and fixes problems in existing syntax which had some pretty obscure uses of spec equations.
It came out of the discussion, a preference to put the Assert statements into the Variables block. That way the rules can be inserted right after the IntegerConstant to which they apply.
It is recognized that this concept requires a new clause in dot3 to define the TRC enhancements to the dot1 Variables block.
Tony will add the syntax and definition into the draft for review at the next meeting.
John Cosley suggested creating some example TRC files in "PatternReport" form. This to serve to flush out more usage issues in lieu of actual tester "Constraints" form of files.
John Cosley pointed out that the index
produced in the pdf versions of the draft is not complete. Tony will
look into the cause.
Meeting adjourned 11:05 Pacific time
Date: Next meeting Thursday, Apr
Time: 10:00 to 11:30 Pacific time
AI-1: Tony - update D11 per the above and continue to prepare the doc for ballot.