Newsgroups Main » Newsgroups Directory » Computers - Non-OS » Specifications
Larch ( comp.specification.larch )
From gaf@cam.ov.com Wed Mar 15 14:45:50 1995
Path: uunet!bounce-back
From: gaf@cam.ov.com (Gary A Feldman)
Newsgroups: news.announce.newgroups,news.groups,comp.specification,comp.specification.z
Subject: RFD: comp.specification.larch, comp.specification.misc
Followup-To: news.groups
Date: 14 Mar 1995 12:09:26 -0500
Organization: OpenVision Technologies, Inc.
Lines: 115
Sender: tale@uunet.uu.net
Approved: tale@uunet.uu.net
Message-ID: <3k4ik6$mmt@rodan.UU.NET>
NNTP-Posting-Host: rodan.uu.net
Xref: gs2.UU.NET news.announce.newgroups:6439 news.groups:139292 comp.specification:3019 comp.specification.z:1890
Request for Discussion (RFD)
Part 1:
Proposed Newsgroup: comp.specification.larch
Status: unmoderated
Distribution: worldwide
Summary: Discussion relating to the Larch family of formal
formal specification languages
Proponents: Gary Feldman <gaf@cam.ov.com>
Part 2:
Proposed Renaming: comp.specification -> comp.specification.misc
Status: unchanged (unmoderated, worldwide)
Summary: General discussion of formal specification methods
This is a two part RFD.
Par 1 is a formal Request for Discussion on the creation of an
unmoderated newsgroup for discussion of issues related to the
Larch family of formal specification languages, and related
methodologies. The purpose of the group is to relieve sporadic
congestion on the Larch interest mailing list, as well as making
up-to-date information about Larch more readily available to the
Computer Science research community. It is parallel to the
comp.specification.z newsgroup (which serves a similar role for
the Z formal specification language).
Part 2 is a request to rename the existing comp.specification
newsgroup to be comp.specification.misc. This is consistent with current
conventions, primarily to distinguish hierarchies (comp.specification.*)
>from specific newsgroups.
The votes for these two parts will be handled separately.
This RFD has been posted in accordance with the Guidelines for
Newsgroup Creation. Its language is based on previously submitted
RFDs (and in some cases, just plain copied). The RFD is being
cross-posted to the following relevant news groups:
news.announce.newgroups, news.groups,
comp.specification, comp.specification.z
Followups to this RFD are to be posted only to news.groups, where
the actual discussion is to take place.
PROPOSED CHARTER
The comp.specification.larch newsgroup will be open to discusison on all
aspects of Larch. This includes, but isn't necessarily limited to,
technical discussions, discussions of practical application, stylistic
issues, discussions of the mathematics underlying Larch, discussion
of any and all Larch Interface Languages, announcements of publications,
trait libraries, and software, discussions of particular Larch tools
(including bug reports that may be of interest to the general Larch
community, but not as a substitute for reporting uninteresting bugs to the
maintainer), etc.
The charter for the renamed comp.specification.misc will be unchanged from
the existing charter for comp.specification, i.e. general discussion of
formal specification methods, including discussion of specific methodologies
that do not have their own newsgroup.
RATIONALE
As indicated above, the proposed Larch newsgroup is consistent with
the existing hierarchy. The traffic rate on the Larch mail list
varies, but recently has produced spikes that make it difficult for
participants to handle the various discussions. Furthermore, as a
mailing list it has appeared to be much more intimidating to new users
than a newsgroup would be, thus inhibiting their participation.
Discussions on the Larch mailing list are most frequently technical in
nature, specific to Larch, and uninteresting to the other comp.specification
readers. While one might consider that traffic on the existing
comp.specification newsgroup is light enough to handle additional
Larch traffic, we fully expect that traffic patterns will match the
existing traffic patterns. Specifically, current traffic on
comp.specification.z usually exceeds that on comp.specification; we
would likewise expect traffic on comp.specification.larch to exceed
that of the general newgroup. Hence, to put this on the general
newsgroup would be unfair to other participants in the general
newsgroup, as well as being unfair to other specification
methodologies (and their proponents) that might be lost among the
Larch discussion.
The rationale for renaming comp.specification to be comp.specification.misc
is to conform to the currently recommended naming strategy. This should have
been done when comp.specification.z was created, but was overlooked. This
benefits both site newsgroup administrators and participants, by making
the distinctions between the newsgroups clearer. Please try to catch up on
existing discussions concerning this strategy in news.groups, before
adding to the discussion.
PROCEDURE
Please post any response to this message to NEWS.GROUPS. If you use
the followup feature on your newsreader this should happen automatically.
It is important to understand that all discussions about the merits of
this proposal should occur on news.groups.
FUTURE CALL FOR VOTES
The votes for comp.specification.larch and comp.specification.misc will
be handled separately; they can both pass, both fail, or one could pass
and the other could fail.
After a discussion period of 21-30 days, unless the discussion indicates
a need to resubmit a new RFD, there will be a Call For Votes (CFV) posted
to the same groups as this RFD. The voting period will be at least 21 days.
If the new group passes by receiving 100 more YES votes than NO votes and
(at least) twice as many YES votes as NO votes, it will be created. Likewise
for the renaming.
From warren@syra.net Mon May 1 18:20:34 1995
Path: uunet!bounce-back
From: warren@syra.net (Warren Lavallee)
Newsgroups: news.announce.newgroups,news.groups,comp.specification,comp.specification.z
Subject: CFV: comp.specification.{larch,misc}
Followup-To: poster
Date: 1 May 1995 16:12:44 -0400
Organization: Usenet Volunteer Votetakers
Lines: 109
Sender: tale@uunet.uu.net
Approved: tale@uunet.uu.net
Expires: 23 May 1995 00:00:00 GMT
Message-ID: <comp.specification-groups-CFV1@uunet.uu.net>
References: <3k4ik6$mmt@rodan.UU.NET>
Reply-To: voting@syra.net
NNTP-Posting-Host: rodan.uu.net
Xref: gs2.UU.NET news.announce.newgroups:6720 news.groups:147048 comp.specification:3156 comp.specification.z:2009
FIRST CALL FOR VOTES (of 2)
unmoderated group comp.specification.larch
unmoderated group comp.specification.misc (replaces comp.specification)
Newsgroups line:
comp.specification.larch Larch family of formal specification languages.
comp.specification.misc Formal specification methods in general.
Votes must be received by 23:59:59 UTC, 22 May 1995.
This vote is being conducted by a neutral third party. For voting
questions only contact Warren Lavallee <warren@Syra.NET>. For
questions about the proposed group contact Gary Feldman <gaf@cam.ov.com>.
DISTRIBUTION
This CFV has been cross-posted to:
comp.specification
comp.specification.z
and EMailed to:
larch-interest@src.dec.com
CHARTER
The comp.specification.larch newsgroup will be open to discusison on all
aspects of Larch. This includes, but isn't necessarily limited to,
technical discussions, discussions of practical application, stylistic
issues, discussions of the mathematics underlying Larch, discussion
of any and all Larch Interface Languages, announcements of publications,
trait libraries, and software, discussions of particular Larch tools
(including bug reports that may be of interest to the general Larch
community, but not as a substitute for reporting uninteresting bugs to
the maintainer), etc.
The charter for the renamed comp.specification.misc will be unchanged
>from the existing charter for comp.specification, i.e. general
discussion of formal specification methods, including discussion of
specific methodologies that do not have their own newsgroup.
RATIONALE
The Larch mailing list is getting unwieldy. Discussions on the list
list are most frequently technical, specific to Larch, and
uninteresting to the other comp.specification readers. We fully
expect that traffic patterns for the larch group will match those of
the existing z (zed) newsgroup. Specifically, current traffic on
comp.specification.z usually exceeds that on comp.specification; we
would likewise expect traffic on comp.specification.larch to exceed
that of the general newgroup. Hence, using the general newsgroup
would be unfair to other participants there, as well as being unfair
to other specification methodologies (and their proponents) that might
be lost among the Larch discussion.
The rationale for renaming comp.specification to be
comp.specification.misc is to conform to the currently recommended
naming strategy. This should have been done when comp.specification.z
was created, but was overlooked.
HOW TO VOTE
Erase everything above the top "-=-=-=-" line and erase everything
below the bottom "-=-=-=-" line. Do not erase anything between these
lines and do not change the group name. Basically, remove everything
except the ballot - we have to save them all on disk.
Give your name on the line that asks for it. Place a YES or NO in the
brackets next to the group name to vote for or against it. Don't
worry about spacing of the columns or any quote characters (">") that
your reply inserts.
Send MAIL to: voting@Syra.NET
Just Replying should work if you are not reading this on a mailing list.
-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
comp.specification-groups Ballot <CS-0001> (Don't remove this marker)
Give your real name here:
If you do not give a real name your vote may be rejected.
[Your Vote] Group
-----------------------------------------------------------------------
[ ] comp.specification.larch
[ ] comp.specification.misc (replaces comp.specification)
-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
Neither ABSTAIN nor CANCEL messages are counted as votes; they serve
only to cancel any previous vote. Abstentions are noted in the final
vote list, whereas CANCEL removes your vote from that list entirely.
(This is the only difference between the two.)
Anything else may be rejected by the automatic vote counting program. The
votetaker will respond to your received ballots with a personal acknowledge-
ment by mail - if you do not receive one within several days, try again.
It's your responsibility to make sure your vote is registered correctly.
If you later change your mind you may vote again; only your last valid
vote will count.
Standard Guidelines for voting apply: no more than one vote per person,
no more than one vote per account. If you attempt multiple votes or
other vote fraud, all your votes may be canceled and your name published.
The complete vote list will be posted with the vote result, including
how each person voted. Note that Usenet votes are not done by secret
ballot.
There will then be a five-day period during which the published vote
list may be corrected and any irregularities addressed. The
requirements for group creation are 100 more YES votes than NO votes,
and 2/3 of all counted votes being YES.
From warren@syra.net Sat May 13 00:05:37 1995
Path: uunet!bounce-back
From: warren@syra.net (Warren Lavallee)
Newsgroups: news.announce.newgroups,news.groups,comp.specification,comp.specification.z
Subject: 2nd CFV: comp.specification.{larch,misc}
Supersedes: <comp.specification-groups-CFV1@uunet.uu.net>
Followup-To: poster
Date: 12 May 1995 15:56:08 -0400
Organization: Usenet Volunteer Votetakers
Lines: 109
Sender: tale@uunet.uu.net
Approved: tale@uunet.uu.net
Expires: 23 May 1995 00:00:00 GMT
Message-ID: <comp.specification-groups-CFV2@uunet.uu.net>
References: <3k4ik6$mmt@rodan.UU.NET> <comp.specification-groups-CFV1@uunet.uu.net>
Reply-To: voting@syra.net
NNTP-Posting-Host: rodan.uu.net
Xref: gs2.UU.NET news.announce.newgroups:6814 news.groups:149088 comp.specification:3183 comp.specification.z:2029
LAST CALL FOR VOTES (of 2)
unmoderated group comp.specification.larch
unmoderated group comp.specification.misc (replaces comp.specification)
Newsgroups line:
comp.specification.larch Larch family of formal specification languages.
comp.specification.misc Formal specification methods in general.
Votes must be received by 23:59:59 UTC, 22 May 1995.
This vote is being conducted by a neutral third party. For voting
questions only contact Warren Lavallee <warren@Syra.NET>. For
questions about the proposed group contact Gary Feldman <gaf@cam.ov.com>.
DISTRIBUTION
This CFV has been cross-posted to:
comp.specification
comp.specification.z
and EMailed to:
larch-interest@src.dec.com
CHARTER
The comp.specification.larch newsgroup will be open to discusison on all
aspects of Larch. This includes, but isn't necessarily limited to,
technical discussions, discussions of practical application, stylistic
issues, discussions of the mathematics underlying Larch, discussion
of any and all Larch Interface Languages, announcements of publications,
trait libraries, and software, discussions of particular Larch tools
(including bug reports that may be of interest to the general Larch
community, but not as a substitute for reporting uninteresting bugs to
the maintainer), etc.
The charter for the renamed comp.specification.misc will be unchanged
>from the existing charter for comp.specification, i.e. general
discussion of formal specification methods, including discussion of
specific methodologies that do not have their own newsgroup.
RATIONALE
The Larch mailing list is getting unwieldy. Discussions on the list
list are most frequently technical, specific to Larch, and
uninteresting to the other comp.specification readers. We fully
expect that traffic patterns for the larch group will match those of
the existing z (zed) newsgroup. Specifically, current traffic on
comp.specification.z usually exceeds that on comp.specification; we
would likewise expect traffic on comp.specification.larch to exceed
that of the general newgroup. Hence, using the general newsgroup
would be unfair to other participants there, as well as being unfair
to other specification methodologies (and their proponents) that might
be lost among the Larch discussion.
The rationale for renaming comp.specification to be
comp.specification.misc is to conform to the currently recommended
naming strategy. This should have been done when comp.specification.z
was created, but was overlooked.
HOW TO VOTE
Erase everything above the top "-=-=-=-" line and erase everything
below the bottom "-=-=-=-" line. Do not erase anything between these
lines and do not change the group name. Basically, remove everything
except the ballot - we have to save them all on disk.
Give your name on the line that asks for it. Place a YES or NO in the
brackets next to the group name to vote for or against it. Don't
worry about spacing of the columns or any quote characters (">") that
your reply inserts.
Send MAIL to: voting@Syra.NET
Just Replying should work if you are not reading this on a mailing list.
-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
comp.specification-groups Ballot <CS-0002> (Don't remove this marker)
Give your real name here:
If you do not give a real name your vote may be rejected.
[Your Vote] Group
-----------------------------------------------------------------------
[ ] comp.specification.larch
[ ] comp.specification.misc (replaces comp.specification)
-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
Neither ABSTAIN nor CANCEL messages are counted as votes; they serve
only to cancel any previous vote. Abstentions are noted in the final
vote list, whereas CANCEL removes your vote from that list entirely.
(This is the only difference between the two.)
Anything else may be rejected by the automatic vote counting program. The
votetaker will respond to your received ballots with a personal acknowledge-
ment by mail - if you do not receive one within several days, try again.
It's your responsibility to make sure your vote is registered correctly.
If you later change your mind you may vote again; only your last valid
vote will count.
Standard Guidelines for voting apply: no more than one vote per person,
no more than one vote per account. If you attempt multiple votes or
other vote fraud, all your votes may be canceled and your name published.
The complete vote list will be posted with the vote result, including
how each person voted. Note that Usenet votes are not done by secret
ballot.
There will then be a five-day period during which the published vote
list may be corrected and any irregularities addressed. The
requirements for group creation are 100 more YES votes than NO votes,
and 2/3 of all counted votes being YES.
From warren@syra.net Thu May 25 18:43:48 1995
Path: uunet!bounce-back
From: warren@syra.net (Warren Lavallee)
Newsgroups: news.announce.newgroups,news.groups,comp.specification,comp.specification.z
Subject: RESULT: comp.specification.{larch,misc} all groups pass
Supersedes: <comp.specification-groups-CFV2@uunet.uu.net>
Followup-To: news.groups
Date: 23 May 1995 16:11:37 -0400
Organization: Usenet Volunteer Votetakers
Lines: 242
Sender: tale@uunet.uu.net
Approved: tale@uunet.uu.net
Message-ID: <comp.specification-groups-RESULT@uunet.uu.net>
NNTP-Posting-Host: rodan.uu.net
Xref: gs2.UU.NET news.announce.newgroups:6898 news.groups:150962 comp.specification:3214 comp.specification.z:2057
RESULT
unmoderated group comp.specification.larch passes 165:14
unmoderated group comp.specification.misc passes 149:38
Yes No : 2/3? >100? : Pass? : Group
---- ---- : ---- ----- : ----- : -------------------------------------------
165 14 : Yes Yes : Yes : comp.specification.larch
149 38 : Yes Yes : Yes : comp.specification.misc (replaces comp.specification)
comp.specification.larch passed on Fri May 12 04:58:12 1995
comp.specification.misc (replaces comp.specification) passed on Thu May 18 15:17:14 1995
Newsgroups line:
comp.specification.larch Larch family of formal specification languages.
comp.specification.misc Formal specification methods in general.
This vote was being conducted by a neutral third party. For voting
questions only contact Warren Lavallee <warren@Syra.NET>. For questions
about the proposed group contact Gary Feldman <gaf@cam.ov.com>.
CHARTER
The comp.specification.larch newsgroup will be open to discusison on all
aspects of Larch. This includes, but isn't necessarily limited to,
technical discussions, discussions of practical application, stylistic
issues, discussions of the mathematics underlying Larch, discussion
of any and all Larch Interface Languages, announcements of publications,
trait libraries, and software, discussions of particular Larch tools
(including bug reports that may be of interest to the general Larch
community, but not as a substitute for reporting uninteresting bugs to
the maintainer), etc.
The charter for the renamed comp.specification.misc will be unchanged
>from the existing charter for comp.specification, i.e. general
discussion of formal specification methods, including discussion of
specific methodologies that do not have their own newsgroup.
[This collection of addresses is (C)1995 by Consultix Computer Services.
Permission is strictly NOT given to use this list or any part thereof to
make a mailing list, or for mass-mailings. Any other use is fine.]
comp.specification-groups Final Vote Ack
comp.specification.misc (replaces comp.specification) ----+
comp.specification.larch ---+|
||
A.M.Gravell@ecs.soton.ac.uk Andy Gravell YY
ab@mimuw.edu.pl Adam Balaban YY
aceler@bnr.ca Alicja Celer YY
aleks@spoda.gentoo.com Brian Witt YY
alex@ece.uc.edu Perry Alexander YY
almstrum@cs.utexas.edu Vicki L. Almstrum YY
amichel@gyptis.univ-mrs.fr Michel ALLEMAND YY
Amy_Moormann_Zaremski@VARICOSE.VENARI.CS.CMU.EDU Amy Moormann Zaremski YY
andrews@rmcece.rmc.ca J. David Andrews YN
archer@frmug.fr.net Vincent Archer NN
Arne.Kristian.Groven@hrp.no Arne-Kristian Groven YY
arromdee@blaze.cs.jhu.edu Ken Arromdee -N
artreyes@rennes.ICS.UCI.EDU Arthur A. Reyes YY
ata@cs.adelaide.edu.au Atanas Nikolaev Parashkevov YY
avenhaus@informatik.uni-kl.de Juergen Avenhaus YY
bb@informatik.uni-kiel.d400.de Bettina Buth YY
bell@aussie.enet.dec.com Peter Bell YY
bjv@herbison.com B.J. Herbison -Y
bkb@Informatik.Uni-Bremen.DE Bernd Krieg-Brueckner -Y
black@cse.ogi.edu Andrew P. Black YY
bmm@inf.rl.ac.uk Brian Matthews YY
Boutheina.Chetali@loria.fr CHETALI Boutheina YY
Brian.Randell@newcastle.ac.uk Brian Randell YY
brianb@wv.MENTORG.COM Brian Bailey YY
brookes@cs.uq.oz.au Wayne Brookes YY
broult@calvin.info.unicaen.fr Christophe Broult YY
bsh@id.dtu.dk Bo Stig Hansen YN
buck@Siswat.Hou.TX.US A. Lester Buck YY
by177@cleveland.Freenet.Edu D. L. Mosher -N
calvert@cc.gatech.edu Ken Calvert YY
carle@telematik.informatik.uni-karlsruhe.de Georg Carle YY
casey@sybase.com Casey Koulman YY
cattel@di.epfl.ch Thierry CATTEL YY
cflatter@aoc.nrao.edu Chris Flatters YY
chalin@cs.concordia.ca Patrice Chalin YY
chengb@cps.msu.edu Betty H.C. Cheng YY
cheon@heeya.seri.re.kr Yoonsik Cheon YN
chizzoni@ghost.dsi.unimi.it Alfredo Chizzoni YY
cianca@cs.unibo.it Paolo Ciancarini YY
Claus.Hintermeier@loria.fr Claus Hintermeier YY
clstampe@mailbox.syr.edu Chris Stamper Y-
crouchkp@flidh101.delcoelect.com K. Crouch --
cwg@iist.unu.edu Chris George YY
dalamb@qucis.queensu.ca David Alex Lamb YY
davidg@oracorp.com David Guaspari YY
dc@panix.com If you do not give a real name your vote may be NN
dhara@cs.iastate.edu Krishna K. Dhara YY
dick@blaze.csci.csusb.edu Richard John Botting YN
dwilliam@thor.ece.uc.edu Douglas Lloyd Williams YY
edavid@lami.univ-evry.fr Erwan David YY
eggert@twinsun.com Paul Eggert YY
engel@cs.tu-berlin.de Christian Engel YY
Eoin@copse.demon.co.uk Eoin Woods YN
esterlin@ncat.edu Albert C. Esterline YY
evs@larch.lcs.mit.edu David Evans YY
ewl@panix.com Emery Lapinski NY
Frederic.Voisin@lri.fr Frederic Voisin YY
FRITZ@Gems.VCU.EDU J.E. Fritz YN
fuy1@gl.umbc.edu Francis Uy -Y
gaf@cam.ov.com Gary Feldman YY
gannon@cs.UMD.EDU John Gannon YY
Gareth.Rees@cl.cam.ac.uk Gareth Rees Y-
garland@fire.lcs.mit.edu Stephen J. Garland YY
godfrey2@coventry.ac.uk Bill Godfrey YN
goldschl@itd.nrl.navy.mil David Goldschlag YY
griffioe@cwi.nl W.O.D. Griffioen YY
gtl1@mcs.le.ac.uk Gilbert Laycock YY
guttag@larch.lcs.mit.edu John Guttag YY
guttman@linus.mitre.org Joshua D. Guttman YY
h-ishika@jaist.ac.jp Hiroshi Ishikawa YY
hall@cs.byu.edu Kelly Hall YY
hancock@movies.enet.dec.com Peter Hancock YY
harter@suneta.zko.dec.com Paul K. Harter, Jr. YY
hehner@cs.toronto.edu E.C.R. Hehner YY
heydon@pa.dec.com Allan Heydon YY
horning@pa.dec.com Jim Horning YY
hossein@csalpha.unomaha.edu Hossein Saiedian YY
hschadha@eos.ncsu.edu Harpreet S. Chadha YY
Hubert.Garavel@imag.fr Hubert Garavel -N
jacob@latcs1.lat.oz.au Jacob L. Cybulski YY
jampel@cs.city.ac.uk Michael Jampel YY
jcohen@DRI.cornell.edu Jeffrey David Cohen YN
jimj@eecs.umich.edu Jim Jewett -Y
jlc@veda.co.uk John.Colley YY
jluc@gyptis.univ-mrs.fr Jean-Luc PAILLET YY
jm@hp-vcd.vcd.hp.com John Matthews YY
jon@violin1.radonc.washington.edu Jonathan Jacky YY
jonboy@io.org Trevor Tymchuk YN
jpenix@ece.uc.edu John Penix YY
jrm@globalvillag.com John R. MacWilliamson NN
jsp@csd.cri.dk Jan Storbank Pedersen YY
jst@id.dtu.dk Jorgen Staunstrup, DTU, Denmark YY
katz@csa.cs.Technion.AC.IL Shmuel Katz YY
kdj@rambus.com Kevin D. Jones YY
kerrinp@byron.apana.org.au Kerrin Pine YY
khb@informatik.uni-kiel.d400.de Karl-Heinz Buth YY
kimketo@utu.fi Kimmo Ketolainen +358 40 500 2957 YY
Krzysztof_Stencel@UQAH.UQuebec.CA Krzysztof Stencel YY
ks@cs.tut.fi Kari Systä -N
kuroda@cs.cmu.edu Kiyotaka Kuroda YY
leavens@cs.iastate.edu Gary T. Leavens YY
leonard@ricks.enet.dec.com Tim Leonard YY
limcy@singnet.com.sg Lim Chee Yong YY
london@cs.pdx.edu Ralph L. London YY
maa@graceland.ih.att.com Mark A. Ardis YY
madey@mimuw.edu.pl Jan Madey YY
makofka@ix.netcom.com doug makofka YY
marc@algorithmics.com Marc Moorcroft NN
marcinek@mimuw.edu.pl Marcin Kubica YY
martins@tcomhp20.epfl.ch Martins Juan YY
Mary_Shaw@cs.cmu.edu Mary Shaw YY
mbarnett@cs.uidaho.edu Michael Barnett YY
medwards@lick.ucolick.org Michael K. Edwards YY
mengel@mimuw.edu.pl Marcin Engel YY
mfx@cs.tu-berlin.de Markus Freericks YY
Michael.Hinchey@cl.cam.ac.uk Mike Hinchey YN
Michael.Norrish@cl.cam.ac.uk Michael Norrish YY
Michal_Iglewski@UQAH.UQuebec.CA Michal Iglewski YY
Michel.Bidoit@ens.fr Michel BIDOIT YY
Michel.Lemoine@cert.fr Michel LEMOINE YY
mmt@RedBrick.COM M Mike Taksar --
moreaux@di.epfl.ch Michel Moreaux YY
moss@bastille.cchem.berkeley.edu David NY
mtv@godiva.lcs.mit.edu Mark Vandevoorde YY
NCC00310@niftyserve.or.jp Shinichi OMURA YY
nick@inferno.fc.hp.com Nick Ingegneri NN
nickc@dcs.st-and.ac.uk Nick Cropper YY
orc@pell.com david parsons YN
Othmene.Ait-Mohamed@loria.fr Otmane AIT-MOHAMED YY
otto@vaxb.acs.unt.edu M. `up to spec' Otto --
P.Boury@frcl.bull.fr pierre boury Y-
paige@cs.toronto.edu Richard Paige YY
patl@lcs.mit.edu Patrick J. LoPresti NN
Paul_Grabow@BAYLOR.EDU Paul Grabow YY
pbaraona@uceng.uc.edu Phillip Baraona YY
pdecker@lds.loral.com Philip Decker YY
pfeifer@ares.informatik.uni-ulm.de Holger Pfeifer YN
pfs@mimuw.edu.pl Piotr Filip Sawicki YN
philip@cs.mu.OZ.AU Philip Dart YY
Pierre.Lescanne@loria.fr Pierre Lescanne YY
pkrysiuk@mimuw.edu.pl Piotr Krysiuk YY
pmb@csd.cri.dk Peter Michael Bruun YY
po@login.dknet.dk Peter A. Olsen YY
poetzsch@informatik.tu-muenchen.de Arnd Poetzsch-Heffter YY
protops@cs.concordia.ca PROTOPSALTOU ANTONIOS YY
pshuang@MIT.EDU Ping Huang YY
ptbast@owl.WPI.EDU Pete Bastien YN
pyoung@srd.bt.co.uk Pete Young YY
pys@info.fundp.ac.be Pierre-Yves Schobbens YY
radrayer@panix.com Rebecca Drayer NN
ramesh@cs.concordia.ca RAMESH ACHUTHAN YY
Ranan.Fraer@sophia.inria.fr Ranan Fraer YY
rdavis@sunset.scu.edu Ruth E. Davis YY
rew@CrystalData.COM Ryan Waldron NN
richford@osf.org Richard L. Ford YY
rick@aai.com Rick Lerner YY
rick@bcm.tmc.edu Richard Miller YY
robsmith@u.washington.edu Robert P. Smith -N
rustan@pa.dec.com K.R.M. Leino YY
sal@dcs.st-and.ac.uk Stephen Linton YY
sartin@pencom.com Rob Sartin YY
schmitz@informatik.uni-tuebingen.de Christoph Schmitz NN
schrod@iti.informatik.th-darmstadt.de Joachim Schrod YY
schweizer@tik.ethz.ch Daniel Schweizer YY
scott_ankrum@VNET.IBM.COM T. Scott Ankrum -N
sean@mpi-sb.mpg.de Sean Matthews Y-
sgubbi@cs.unibo.it Sgubbi Patrizia YY
shb@dcs.st-and.ac.uk Simon Brock YY
sigurd@ii.uib.no Sigurd Meldal NN
simon@security.ucc.ie Simon Foley YY
sivapras@cs.iastate.edu Gowri Sankar Sivaprasad YY
sjsmith@cs.UMD.EDU Stephen Joseph Smith --
smk@dcs.ed.ac.uk Stefan Kahrs YN
somebody@cadlab.de Christel Oczko, co@cadlab.de YY
sp@csd.cri.dk Soren Prehn YY
stainles@bga.com Dwight Brown NN
steve@gridlock.demon.co.uk Steve Tracey YY
stoodt@cis.umassd.edu Michael A. Stoodt -N
sturm@coe.wvu.edu David W. Sturm YY
T.B.Dinesh@cwi.nl T. B. Dinesh YN
tgm@netcom.com Thomas G. McWilliams YY
thp@csd.cri.dk Thomas Puls YY
ue@cci.dk Urban Engberg YY
um@dcs.st-and.ac.uk Ursula Martin YY
warford@pepperdine.edu Stan Warford YY
widenius@cc.helsinki.fi Risto Widenius NN
wile@ISI.EDU David Wile YN
wilma@deis65.cineca.it Wilma Penzo YY
wing@cs.cmu.edu Jeannette M. Wing YY
wood@sctc.com William T. Wood YY
wth0019@decster.uta.edu Billy Harris -N
yang@dstc.edu.au Zhonghua YANG YY
yelick@cs.Berkeley.EDU Kathy Yelick YY
ymtan@iti.gov.sg Yang Meng Tan YN
young@cs.purdue.edu Michal Young YY
USENET FACT: Flaming
Flaming is the hostile interaction between multiple Usenet users.
NewsDemon® is a trademark of K&L Technologies, Inc.
2001 - 2012 © Copyright NewsDemon.com