RE: Working groups for the upcoming standard

Hi,

Maybe the last one should also be separated into two? The first two issues there are related to generation constructs/semantics, and the third is related to TLM, which are two unrelated topics.

Thanks,
Yuri.



-----Original Message-----
From: owner-ieee1647@eda.org [mailto:owner-ieee1647@eda.org] On Behalf Of darren.galpin@infineon.com
Sent: Friday, 01 November, 2013 17:43
To: ieee1647@eda.org
Subject: Working groups for the upcoming standard

Hi,

Here are the open mantis issues we have so far:

0004746<http://www.eda-stds.org/mantis/view.php?id=4746>        Revise the chapter on Template types
0004745<http://www.eda-stds.org/mantis/view.php?id=4745>        Reflection API enhancements
0004490<http://www.eda-stds.org/mantis/view.php?id=4490>        ability to stop/restart evaluation of temporal checks (expects)
0004377<http://www.eda-stds.org/mantis/view.php?id=4377>        new message configuration infrastructure
0004336<http://www.eda-stds.org/mantis/view.php?id=4336>        read_only() missing from LRM
0004318<http://www.eda-stds.org/mantis/view.php?id=4318>        Chapter 10 - Clarify variable clustering and ordering semantics for constraints
0004312<http://www.eda-stds.org/mantis/view.php?id=4312>        Chapter 25 - Generalize messaging constructs to eneble structured messages
0004311<http://www.eda-stds.org/mantis/view.php?id=4311>        Section 13.1 - Generalized on-event
0004125<http://www.eda-stds.org/mantis/view.php?id=4125>        additional TLM2 interface constructs should be added to standard
0004124<http://www.eda-stds.org/mantis/view.php?id=4124>        new set type should be added to standard
0004112<http://www.eda-stds.org/mantis/view.php?id=4112>        consume defined as a keyword but not defined anywhere else in LRM
0003386<http://www.eda-stds.org/mantis/view.php?id=3386>        Consider adding wildcard equality operators


There are two working groups which seem to naturally fall out of this:

1)      Temporal Working Group
      This would cover 0004490, 0004311, 0004112.

2)      Messaging Working Group
      This would cover 0004377, 004312.

Perhaps a third would be:

        Types and Operators Working Group
        This would cover 0004846, 0004124, 0003886

And a fourth to mop up:

        General Working Group
        Covering 0004336, 0004318, 0004125


So, do people agree with this, does it seem reasonable?

We'd then of course need working group leaders and people to help out in each group..... Also, since the last meeting Hannes has organised the legal letter to cover the release of Cadence documentation for us to work on, and this has now been lodged with the IEEE. Many thanks Hannes!

Cheers,

Darren

--------------------------------------------------------------------
Darren Galpin                                         Tel: +44 117 9528741
Infineon Technologies                        Fax: +44 117 9528777
Infineon House                    Darren.Galpin@infineon.com<mailto:Darren.Galpin@infineon.com>
Great Western Court
Hunts Ground Road
Stoke Gifford
Bristol, BS34 8HP, England
--------------------------------------------------------------------




--
This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.