[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Proposal for upcoming meeting


Dear Achutha,

Thanks for your comments. I've embedded some answers below:

On Monday, October 20, 2003, at 11:19 PM, Achutha Jois wrote:

Dear Yaron

As i am fan of temporal expressions, i would like to work in the TE_TF.
Also if there is a shortage of staff in the Basic Language Task force (BL_TF) then i would work there as well,

This is great. I hope to have the enrollment started after next weeks
conference call.

And i had few doubts, please try to clarify them

1. ?It is regarding the extensions to the temporal languages, Can we suggest changes and additions to the basic structure, and how they are built? 

The main task is to capture the definition of the language. I think
this should be done first. Of course the TF can recommend extensions
and even modifications, but those should be presented as such and
accepted by the WG prior to their incorporation into the draft LRM.

2. regarding addition of PSL flavour, Can we also take a look at vera and Sugar for this??

The PAR is deliberately vague here, stating "other languages of interest".
This means that the WG can decide which languages to embed. Again, this
is not about creating a composite temporal language similar to the Accellera
effort, but rather defining the way other languages work in the e context.

The move to embed another temporal language should be presented as an
enhancement request to the WG. I feel such extensions should come
after the original language is reviewed and captured in the draft LRM.

3. What about sequences ???, which task force will address this?.

I would think this goes with the generation TF.

4. Can you provide us some templates and Guidelines for doing this work. 

This is a good point. I will propose some guidelines for TF operation.
In general each TF should review the relevant portions of the LRM, file
issues about inaccuracies, suggested modifications and extensions and
work with our editor to fix such issues in subsequent releases of
the draft LRM. I don't see the TF members doing any edits directly,
because of the huge issue this will create while attempting to
merge such edits into a coherent document.

Best regards,

-- yaron


regards
Achutha Jois



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.


Yaron Kashai wrote:


Hi there,

Here is my summary of the sporadic discussions we had so far. I would like
to present it to the WG at the next meeting (next Monday). Please send
out any comments ASAP - it would be great if we could present this
as our consensus.

Once presented, I will start looking for volunteers to lead each task
force. I assume this group will remain as the WPTF, but it would be
best if someone other than myself will lead this - any takers?

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.

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.

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.


<image.tiff>


*********************************************************************** *

SASKEN BUSINESS DISCLAIMER



This message may contain confidential, proprietary or legally Privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, Disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.

***********************************************************************