Agenda:
1. TRC errors
2. 1450.4 and channel mapping
3. Change Signals to SignalCharacteristics
4. Tutorial

• Detailed error descriptions of potential TRC errors are currently defined in each section and Annex G summarizes. It was decided that error numbering should *not* be in the standard. It was then further decided that exact wording of error messages should *not* be in the document. A section should be included on expectation of tools that perform TRC checks and how they are expected to report errors. Errors should be identified by the hierarchical block/statement name. e.g., TRC.PatternCharacteristics.MaxVectors.
• P1450.4 is looking into some aspects that may overlap with P1450.3. In particular tester channel mapping using NameMaps, and MultiplePort/MultipleSite definitions. More discussion with other team is required.
• Decided to change Signals to SignalCharacteristics to be consistent with other block names of this standard.
• A brief discussion (again) on Dan's tutorial. Group thought that it was of appropriate size and detail, although a full review has not been done. Group agreed to include it in the standard and continue the review process.

• FM-1 - tutorial review
• JT-5 - LoopCharacteristics - review changes and approve
• Remainder of resolution issues