Meeting 2 Minutes

1. Call to order

2. Motion to accept the minutes of meeting 1 as posted

The motion to accept the minutes as posted was set forth in the agenda.

Andy Piziali seconds the motion. There were no objections, no one abstained.

The motion to accept the minutes has passed unanimously.

3. Motion to accept bylaws

Matthew Morley seconds the motion. No objections, no abstentions.

The motion to accept the bylaws as passed unanimously.

4. Officer nominations

Michael McNamara moves to nominate Steve to Vice Chair. Mike Goble seconds the motion. There were no objections, no abstentions.

The motion to nominate Steve as Vice Chair has passed unanimously.

5. Review work plan proposed by work plan task force

5.1 Review recommendations

The WG should charter the following task forces to develop areas of the specification. All TF work will be viewed as recommendation to the WG, which will be the forum approving all such work.

Each task force will focus on reviewing the LRM parts relevant to it's scope. Inaccuracies, omissions and corrections will be logged into an issue tracking system established for this purpose. The TF will work with the WG editor to correct the issues in subsequent releases of the draft LRM. Each TF is empowered to propose language extensions and modifications, and log issues to that end. Language extensions and modifications must be approved by the WG prior to their inclusion in a draft LRM.

To clarify: this means that any corrections and clarifications can be inserted through the process between the TF and the Editor, such changes will be visible to the whole WG through periodical revisions of the LRM. Modifications and extensions will require the WG consent upfront, before they are included in the LRM.

Additional guidelines for the operation of the task forces will be developed later.

1. Work plan task force (WP_TF)

This task force should remain active with the following charter:

Review issues submitted by WG members, recommend further action and assign them to the appropriate task force.

The WP_TF may recommend that new task forces are created to deal with issues that can not be reasonably addressed within one of the existing task forces.

2. Basic language task force (BL_TF)

Specify the syntax and the semantics of fundamental language constructs including syntactic macros, types, identifiers, modules, units, structs, struct members and actions. Not including features covered by other task forces.

3. AOP task force (AOP_TF)

Specify object oriented and aspect oriented features of the language in particular (like and when) inheritance, extension, packages, as well as the import statement.

4. Constraints and generation (TG_TF)

Specify the syntax and semantics of constraints and related actions, including elaboration and sequences.

5. Coverage task force (COV_TF)

Specify the syntax and semantics of coverage features. Define the expected behavior of the coverage database and its API.

6. Temporal expressions (TE_TF)

Specify the temporal language and its anchoring in language expressions and actions.

This task force should later look at embedding of temporal languages, in particular the addition of a PSL flavor.

7. TCMs and concurrent semantics (TCM_TF)

Specify the concurrent behavior of e time consuming methods, including scheduling semantics. The work shall cover "wait", "sync" and "emit" actions, "all-of" and "first-of" concurrent actions and e-to-e ports. The work of this task force should set the context for the temporal expressions task force.

8. Foreign (HDL) access and interfaces (FI_TF)

Specify the interaction between e and other languages (Verilog, VHDL, System C). Specify the behavior of the language as a stand alone environment, a master and a slave. Define the semantics of external ports.

9. e libraries (LIB_TF)

Specify the API and semantics of all library functions defined for e.

10. e reflection API (RF_TF)

Specify the reflective functions of the language and an API for them.

11. e synthesis task force (SYN_TF)

Define the subset of the e language used for synthesis and the semantic restrictions related to synthesis.

This task force should be launched only after a synthesis subset has stabilized sufficiently.

This concludes the recommendation of the WP TF.

Ron Bow has accepted the invitation to become the lead Editor for this WG. Ron has been a technical writer with Verisity for over 6 years now, with great e related experience.

Additionally, a new issue tracking system has been added to the web site. It will soon become operational and everybody will be requested to familiarize themselves with the system. TF members and other WG members will be able to use this system to log issues, look at reports of current issues and generally track work through that tool.

5.2 Discussion

• The work plan task force should include all task force leads, to ensure proper distribution of work.
• There should be overlap between the temporal, concurrency and interfaces TFs to align their closely related work.

The motion to amend the recommendations, requiring that the WP_TF comprises all TF leads, passes.

Bryan Morris: why break up the language into an AOP TF and basic language TF?

Steve Pearlmutter: AOP adds complexity to the language, this partition will simplify the work for both teams and allow for some parallel progress.

5.3 Motion to accept

The motion to accept the WP_TF recommendations as amended passes unanimously.

6. Patent policy

7. Next meeting

The meeting adjourned at 9:35