Meeting 14 Minutes

Teleconference, July 11th, 2005
A quorum of 7 out of 9 voting members present.
Attendance is noted on the web site roster.

1. Call to order

Meeting was called to order at 09:01 PST/16:01 GMT.

2. Approval of minutes from meeting 13

Joe Daniels moves to approve the minutes as posted.
Lori Kate seconds.
No objections/abstainers. The motion to approve the minutes was carried.

3. Review status of technical contribution

Yaron : We have all the technical contribution material in. I would like to thank the various contributors for taking the timing to heart and greatly improving the LRM. Work ongoing around the first 4 chapters that will include the necessary preliminaries.

Some material is substantially new and may need a close review:
7 - constraints
8,9,10 - temporals
11 - time consuming actions (including state machines) WIP
13 - macros

The library chapters have been thoroughly reviewed and re-arranged. They seem to be quite stable now.

Some chapters already have issues filed relating to revision 0.3, most notably Ports.

Please note that moving forward we will discharge all issues relating to revisions 0.1 and 0.2.

We have a very short time to review and introduce changes to revision 0.4. That is planned to be the final revision - it will be available
early August. We'll have 2 weeks to review it. Joe will prepare a version without change bars and issue numbers, and with consecutive
numbering. That version will be called 0.5. Revision 0.5 will be identical contents wise to revision 0.4. The WG will be asked to
approve that revision on September 1st.

4. Editors updates

Joe: There are a few draft 2 issues and some 3 that need to be looked at. There is an issue with divergent cross references, because parts have moved around or removed. Need to point out holes that have to be fixed, either adding technical material where a reference is pointing or removing the reference if the material need not be there.

There is going to be a complete re-numbering of the pages, including tables and figures, in order to comply with IEEE style. This may make reviews more difficult, so that change will happen after the technical content is settled.

We need the WG members to look at the first few chapters, especially the list of terms and acronyms, but also at the list of references etc. Some of this material needs to be posted soon so the WG can review and comment.

Need someone to review the usage of unix names in the complete LRM, uses of Verilog and VHDL stuff.

The load order document was formulated as an annex - with references from the appropriate chapters.

Matan: two chapters tightly connected to the load order discussion: importing e files and preprocessor directives. Importing will need to be revised to eliminate stuff that's not accurate.

Joe: let's keep the framework and review the import section and the preprocessor directives chapter to remove inaccurate comments.

Matan: ch. 4 needs references to the load order as well (dealing with extension).

Pitchu: Can we have a single PDF file for the whole LRM? That would make the review of the flow more efficient

Joe: will have one ready by Wednesday.

Joe: In order to simplify the tracing of issues we have decided to maintain numbering for this version but will have to
change numbering for upcoming revision.

Matan: issues reported on earlier drafts, all have page/line numbers. How do we maintain references.

Yaron: maintain numbering in 0.4, only change once we are happy with the technical contents. For version 0.5, hopefully there won't be any open issues to refer to.

5. Preparing for ballot

5.1 Ballot preparation task force

Yaron: I've asked Victor Berman to lead our ballot preparation task force. Victor has a long experience with the IEEE and we are fortunate to have his support here.

Since TF leads are elected officers, per our bylaws, I'd like to have a vote confirming Victor's nomination. Can I invite a motion
to nominate Victor?

Matan moves to nominate Victor to lead ballot preparation.
Lori Kate seconds.
No abstains, no objections - the motion carries.

5.2 WG members participation in ballot

Yaron: It is key that the WG members have a fair representation in the ballot group. After all, we are the most knowledgeable people about the standard, and obviously have a vested interest. This will entail joining the IEEE SA organization and indicating your interest in
joining the DA ballot pool.

Victor: will send out a note to WG members with instructions on how to join the ballot pool.

6. Other Business

6.1 Listing of WG members on the standard

Yaron: We will need to decide whom to list as WG members on the standard. My inclination is to list all people that have been active at one time during the work on the standard. This will not include people that didn't participate in any of the meetings, or the technical discussion.

Matan: what's at stake?

Yaron: This will associate WG members with the standard. There doesn't seem to be any formal obligation here.

Yaron: I will send a personal e-mail to the people that will be included, to give them an option to opt-out of the standard. The list will be posted on the web site to allow for corrections.

6.2 Glossary of terms
WG members will be asked to review and contribute to the following pre-face matter:
- Glossary of terms
- List of refs
- Bibliography

Matan: What about issues relating to previous LRM revisions - do they need to be closed?
Yaron: There are currently over a hundred issues that have been fixed and need to be closed. To save effort, we can consider all issues relating to old revisions of the LRM as abandoned. If the issue persist in revision 0.3 kindly file a NEW issues.
Matan: How about comments about pre-defined methods / routines issues and other issues not worked on by my task force?
Yaron: Anyone can file issues on any topic. May be helpful to discuss with the author of the section before that though.
Pitchu: what happens to the index? Does it need to be reviewed?
Joe: We should not invest too much in the index. This will be one of my tasks.

No other business to dispense of.

7. Patent policy

The chair has issued a call for essential patents, in compliance with current IEEE/SA PatCom guidelines. The WG members are advised to review the call for essential patents and the patent related slide presentation posted on the web site .

8. Next meeting

Please remember to send e-mail to rollcall@ieee1647.org so that your attendance on this call is recorded.

• Please DON'T send these e-mails to the reflector
• Use the e-mail address you registered with

Next meeting (meeting 15) is set to Monday, August 1st at 9:00 AM pacific (same time as today's meeting).
A follow on meeting (meeting 16) is tentatively set for Monday August 27 at 9 AM pacific.

9. Adjourn

IEEE/SA home
IEEE Standards Association

DASC Home
Design Automation Standards Committee

VLSG Home
Verification Language Study Group

The 1647 PAR
Project Authorization Form

(Updated Wed Oct 11 16:19:01 PDT 2006)