RE: [sv-ac] call to vote on Mantis 1681

I put the text in the added section in blue and uploaded the updated
document.

Thanks,
Dmitry

-----Original Message-----
From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On
Behalf Of John Havlicek
Sent: Thursday, July 26, 2007 2:37 PM
To: Bresticker, Shalom
Cc: sv-ac@server.eda-stds.org
Subject: Re: [sv-ac] call to vote on Mantis 1681

Hi Shalom:

Are the rules that are the basis of these comments
written down so that we can refer to them?

I know of many places in the LRM with inconsistencies
in the use of fonts, and I would like to be able to 
judge independently whether or not they are correct.

Regarding the setting of new text in blue, this makes
sense to me when we have red strikethrough, blue, and
black text mixed in describing a change.  But if we
are describing a new section, how do we represent other
LRM conventions, like red terminals in syntax productions,
underneath a completely blue font?  I am not sure there
is a consistent set of rules on how to represent these 
things.

Best regards,

J.H.

> X-Authentication-Warning: server.eda-stds.org: majordom set sender to
owner-sv-ac@eda.org using -f
> X-ExtLoop1: 1
> X-IronPort-AV: E=Sophos;i="4.16,583,1175497200"; 
>    d="scan'208";a="254985807"
> X-MIMEOLE: Produced By Microsoft Exchange V6.5
> Content-class: urn:content-classes:message
> Date: Thu, 26 Jul 2007 11:14:51 +0300
> X-MS-Has-Attach: 
> X-MS-TNEF-Correlator: 
> Thread-Topic: [sv-ac] call to vote on Mantis 1681
> Thread-Index: AcfOJC6xSjKG3iwLR6a/4onP9mw6yAACOX4AABTa8zAANtL7kA==
> From: "Bresticker, Shalom" <shalom.bresticker@intel.com>
> X-OriginalArrivalTime: 26 Jul 2007 08:14:51.0519 (UTC)
FILETIME=[0A4EC0F0:01C7CF5D]
> X-eda.org-MailScanner: Found to be clean, Found to be clean
> X-Spam-Status: No, No
> X-MIME-Autoconverted: from quoted-printable to 8bit by
server.eda-stds.org id l6Q8FJf8006626
> Sender: owner-sv-ac@eda.org
> X-eda.org-MailScanner-Information: Please contact the ISP for more
information
> X-eda.org-MailScanner-From: owner-sv-ac@server.eda.org
> 
> Hi,
> 
> There seems to be some inconsistent formatting in the proposal.
> 
> For example, on page 3, if 14.13 is new, it should all be in blue.
> 
> At the bottom of page 3, "endclocking" should be bold.
> 
> At the top of page 4, "sys" should be in Courier font.
> 
> In M.2, "#define vpiGlobalClocking" should be in blue.
> 
> Some of the references to the "global clocking" statement are in bold
> Courier font, and some are in regular Times font.
> 
> Thanks,
> Shalom
> 
> 
> > -----Original Message-----
> > From: owner-sv-ac@server.eda.org 
> > [mailto:owner-sv-ac@server.eda.org] On Behalf Of Korchemny, Dmitry
> > Sent: Wednesday, July 25, 2007 8:57 AM
> > To: Bassam Tabbara; john.havlicek@freescale.com; 
> > sv-ac@server.eda-stds.org
> > Subject: RE: [sv-ac] call to vote on Mantis 1681
> > 
> > Hi Bassam,
> > 
> > I fixed this typo and uploaded the updated version into Mantis.
> > 
> > Thanks,
> > Dmitry
> > 
> > -----Original Message-----
> > From: owner-sv-ac@server.eda.org 
> > [mailto:owner-sv-ac@server.eda.org] On Behalf Of Bassam Tabbara
> > Sent: Tuesday, July 24, 2007 11:00 PM
> > To: john.havlicek@freescale.com; sv-ac@server.eda-stds.org
> > Subject: RE: [sv-ac] call to vote on Mantis 1681
> > 
> > I vote yes. *VERY MINOR* friendly amendment:
> > 
> > version_specifier ::=
> > 1800-2008
> > 1800-2005                       <<<<<<<<<< Add "|"
> > | 1364-2005
> > | 1364-2001
> > | 1364-2001-noconfig
> > | 1364-1995
> > 
> > 
> > Thx.
> > -Bassam.
> > 
> > -----Original Message-----
> > From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On 
> > Behalf Of John
> > Havlicek
> > Sent: Tuesday, July 24, 2007 11:55 AM
> > To: sv-ac@eda-stds.org
> > Subject: [sv-ac] call to vote on Mantis 1681
> > 
> > All:
> > 
> > This is the call to vote on the proposal for Mantis 1681.
> > 
> > Please vote if you are eligible.  See the details below.
> > 
> > J.H.
> > 
> > --------------------------------------------------------------
> > ----------
> > 
> > Ballot on Mantis 1681
> > 
> > - Called on 2007-07-24, final ballots due by 23:59 PDT on
2007-07-31.
> > 
> >  v[x-xxxxxxxxxxxxxxxxxxxxxxxx-xx] Doron Bustan (Freescale)
> >  v[xxxxxxxxxxxxxxxxxxxxxxxxxxx-x] Eduard Cerny (Synopsys)	
> >  n[--x-xxx---------x-x-xxx-x---x] Surrendra Dudani (Synopsys)
> > v[xxxxx-xx-xxxxx-xxx-xxx-------] Yaniv Fais (Freescale)
> > t[xxxxxxxxxxxxxxxxxxxxxxxxxxxxx] John Havlicek (Freescale - Chair)
> > v[xxxxxxxxxxxrxxxxxxxxxxxxx-xxx] Dmitry Korchemny (Intel - Co-Chair)
> > n[x--xx--xxxxx----------xx-xxxx] Manisha Kulshrestha (Mentor
Graphics)
> > n[----------xxxxx-------x-xx-x-] Jiang Long (Mentor Graphics)
> > n[--x--xxx.....................] Joseph Lu (Altera)
> > n[-------x--x-xx--xx-xxxxxxx-x-] Hillel Miller (Freescale)
> > v[xxxxxxxxxx-xxxxxxxx-xxxxxxxxx] Lisa Piper (Cadence)
> > v[x-x-xxxxx-x..................] Erik Seligman (Intel)
> > n[---xxxx-----xxxx-xx----------] Tej Singh (Mentor Graphics)
> > v[xxxxx-xxxxxxxxxxxxxxxxxxxxxxx] Bassam Tabbara (Synopsys)
> > v[xxx-xxxxxxxxxx...............] Tom Thatcher (Sun Microsystems)
> >    |----------------------------- attendance on 2007-07-24
> >  |------------------------------- voting eligibility for this ballot
> > |-------------------------------- email ballots received
> > 
> > 
> > 	Legend:
> > 		x = attended
> > 		- = missed
> > 		r = represented
> > 		. = not yet a member
> > 		v = valid voter (2 out of last 3 or 3/4 overall)
> > 		n = not valid voter
> >                 t = chair eligible to vote only to make or break a
tie
> > 
> > --
> > 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.
> > 
> > -- 
> > 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.
> 
> 

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