Refined recommendation

[Yaron Kashai <yaron@verisity.com>]

Hello again,

Here is a refined version of the proposed recommendation, taking into
account Meirav's and Achutha's comments.

Please provide any additional comments urgently - I would like to
post this on the web site so that the WG members will be able to
read this before the call. (approving comments welcome as well :)

For your convenience, changes are marked with change bars.

Thanks a lot,

-- yaron



Proposed Task Forces


we recommend that the WG will 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.

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


 1. Work plan task force (WP_TF)

Review issues submitted by WG members, recommend further action and
assign them to the appropriate task force. (An issue tracking system
will be added to the WG web site - under construction).


The WPTF 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.

| Sequences should be covered by this task force as well.

 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 also look at extensions to the temporal language
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

 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

 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.