Meeting 12 Minutes

Teleconference, May 9th, 2005
A quorum of 12 out of 13 voting members present.
Attendance is noted on the web site roster.

1. Call to order

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

2. Approval of minutes from meeting 11

Darren Galpin moves to approve the minutes as posted.
Vitaly seconds.
No objections/abstainers. The motion to approve the minutes was carried.

3. Task force updates

Yaron : The thing to keep in mind here is that we're approaching the deadline for technical input to be provided, we want to have everything in by the beginning of June. I'll go through the list of outstanding technical contributions

An introduction chapter and technical summary
We need to insert the load-order visibility document in the appropriate places
There's still an open issue about the parsing infrastructure that Matans been working on
The macro expansion chapter requires review
There's a document about method extension principles that is being prepared
We have decided about the Verilog and VHDL declarations that has to be reflected in the document
The constraints chapter is being worked on and I have in my in-box a partial draft that is being reviewed by a few members now and hopefully will have that done shortly
Updates to the temporal chapters - some work has been done on that
Finally there's a review of the library chapters. Two of them chapters 19 and 26 are through the initial review

Also I have chapter 2 ready for posting - it has been through the editing process already. It contains fixes to a majority of the issues in the bug tracking database - it's a major revision to that chapter.

All these chapters that are being posted now - these are the things that we will use for the revision unless people find issues with them and file these issues. So I really encourage everyone to take a close look at these as soon as they're posted as we want to move on with these.

Matan : Reporting on AOP work progress - unfortunately I haven't been able to advance much. The biggest issue is that of the macro methods - this chapter in the LRM is very unsatisfactory . The macro functions is pretty similar to what we normally call reduction rules in the grammar it is much more expressive than ordinary grammatical rules. Any sequence can be reduced once the rule applies but if you can have the sequence inside a regular expression - you can have any number of these non terminals followed by a terminal. All of these regular expression operators can be used to express the reduction rules that each macro uses. These are explained very sketchily or very briefly in the LRM and elaborating here would go towards explaining the syntactic composition of the language.

The other document is the semantics for method extensions - especially with respect to instances when subtypes. These rules are not captured well enough. I hope to put some more substance into this but not close every possible issue.

I had an interesting discussion with Christian about the load order document - I got a few inputs that I may want to incorporate in the document.

Pitchu : We had a discussion on the ports chapter and we had some issues with the vhdl declarations which we put into the bug tracking system. We will have another meeting in 2 weeks time.

David : Update regarding the temporal TF. Basically we're so late with the work that I've taken up the work upon myself. So to report the status, Chapter 8 is in pretty good shape - there's just some clarification needed with ticks and constructs. Then there's chapter 9 with core temporal expressions - there's quite a lot of work for 1) terminology 2) the framework for explaining semantics should be put in place with abstract syntax, a discussion of normal sampled form and semantics. Most of the material we basically have and this is what was distributed to the working group many months ago, so I see the main work that is still remaining for chapter 9 is to relate the framework to the concrete syntax. I'm still working on that. Chapter 10 is not very substantial.

Yaron: Vit, working on the constraints chapter should have his first revision shortly. Time is short - we're getting to the point that by the next meeting we'll need all of the technical work to have been done and only editing then to go on.

4. Editors updates

Joe : We're continuing to put chapters and drafts through the necessary revisions. We're going through the chapters and moving forward from chapters 7 to 13. We've just finished the basic ones and will now start on coverage constraints. Then after review this may become more refined once people have taken a closer look at that. Any feedback that you have on how we're doing this process feel free to pass that on to Yaron and myself and please continue with the issue tracking database for any technical issues that you identify. We're in the process now that we have all the technical issues identified and in the next 21 to 35 days I'm going to continue to turn around the clauses into IEEE format and getting them in front of people. Yaron - at what point do we assume that we're not going to review this any more and we can close it?

Yaron: The chapters that we post - the 3rd revision that are being posted - the working assumption is that these are the final form. There are some open questions which have not been addressed, its those minor changes that we hope to insert in there. People should review them as soon as they're posted and if there's anything wrong please let us know right away - that will help us to wrap it up and move onto the ballot.

Joe : Each TF, in theory knows what their issues were and whether they are open or whether they've been passed to me. Can people please review the issue database, confirm that we've dealt with the issue correctly and move their issue number into the closed column.

Yaron: We have 268 issues and 2/3 rd of them are still open in some status. I could close them all myself but the intent is for the people to review the issues they filed - review the changes and close them . When all the version 3 chapters are out, we'll take no further notice of the issues that were filed for revisions 1 and 2 - we'll only look at the revision 3 issues to move forward. So if there's an issue which hasn't been addressed or not appropriately it has to be elevated and logged against revision 3.

Joe: So far I've worked worked on clauses 2,3 4,5,6,16. Next in line is 12,14,15,17,18 and then if the library and temporal chapters come in I'll go through that

Yaron : We have chapters 19 and 26 of the library chapters ready for review as well.

Matan : when an issue that is imported is handled by Joe its status would be updated to indicate that it would be verified?

Yaron : Right now issues that are ready for Joe to take a look at are changed to "update by editor" status, then when Joe has edited them he will change the status to "TF verify fix" in theory you should then be able to check the change and if it is correct then change the status to "verified and closed" status. Once they are closed then they are filtered out in the database - although they're still in there they're not immediately visible.

5. Other Business

We need to push to accelerating the work to move to ballot earlier than expected - in general this is a happy thing that I'd like to see things get in focus and move faster.

6. 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 .

7. 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 is set to Monday, May 9th at 9:00 AM pacific (same time as today's meeting).

8. 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:18:53 PDT 2006)