Date: 2016-06-01

Time: 16.00:00 UTC (9:00 PDT)

Duration: 1 hour

Agenda

• Reminder of IEEE patent policy
  See: http://standards.ieee.org/board/pat/pat-slideset.ppt
• Minutes approval
• Email ballot results
• Mantis items in progress
• Opens

Attendance Record

Legend:

x = attended

- = missed

r = represented

. = not yet a member

v = valid voter (2 out of last 3 or 3/4 overall)

n = not a valid voter

t = chair eligible to vote only to make or break a tie

Attendance re-initialized on 2016-03-09:

v[.x-xxxx] Mehbub Ali (Intel)

n[.xx--x-] Ang Boon Chong (Intel)

n[x-x-xx-] Shalom Bresticker (Accellera)

n[.x-----] Dennis Brophy (Mentor Graphics)

v[xxxxxxx] Eduard Cerny (Synopsys)

n[xx-xx-x] Ben Cohen (Accellera)

t[x-xxxxx] Dmitry Korchemny (Synopsys - Chair)

n[xxx-x-x] Manisha Kulshrestha (Mentor Graphics)

v[xxxxxxx] Anupam Prabhakar (Mentor Graphics)

v[xxxxxxx] Erik Seligman (Intel – Co-chair)

v[x-x-xxx] Samik Sengupta (Synopsys)

|- attendance on 2016-06-01

|--- voting eligibility on 2016-06-01

Minutes

IEEE patent policy reminder

Minutes approval

Erik: Move to approve the minutes from 18-May-2016.

Samik: Second.

Motion passed: 5y/0n/0a (only valid votes count; one non-valid voter abstained).

Email ballot results

Issue 3117 passed: 4y/0n/1a.

Issues 5056 and 5372 passed: 5y/0n/0a.

Mantis items in progress

3924: Need to clarify behavior when sequence event used as property clocking

Erik: Do we have a definition of a sequence event in assertions?

Anupam: Yes, it is written in 9.4.2.4.

Dmitry: The sequence event occurs in the Observed region

Erik: Need an example in the LRM

Ed: There is an example at the end of 16.13.6

Erik: Maybe to add a standalone example or just drop it altogether. Will elaborate a proposal.

4557: Typos in clause 16

Ben: Do we need more parentheses?

Manisha: It is always clearer to use parentheses.

Dmitry: There is a typo in the proposal.

Ed: Need also to define `true.

Dmitry: It would be convenient to have true and false defined in a standard package. Should be considered by the next PAR.

Ben: Will implement the fix and notify Shalom.

Opens

Erik: Dmitry to review the assigned items and resend.