Re: I believe that it is time to create a draft one 1364-2005

From: Michael McNamara (mac@verisity.com)
Date: Wed Apr 09 2003 - 12:05:12 PDT

  • Next message: Stefen Boyd: "Re: I believe that it is time to create a draft one 1364-2005"

    Precedence: bulk

    Let us use Passover as a compelling event, and have you complete
    certainly the IEEE required header and footer items for a Draft, and
    then take whatever other items you happen to have complete by then;
    and then produce a PDF, send it to Stefen, and we can chew on it.
    Clearly this will not be the last draft, so again, get it produced and
    out to us with whatever quality can be done, so that we can all start
    acting a proofreaders for you :-)

    I'd also like to get a copy of the framemaker source at the point you
    make the PDF, so that I can serve as the holder of a backup copy,
    should unlikely events transpire.

    Michael McNamara

    Shalom.Bresticker@motorola.com writes:
    > Also, I forgot to note that not all of the changes from 2001a to 2001b are
    > already passed by vsg and marked with change bars. I should mark them as well
    > already for Draft 1.
    >
    > Shalom
    >
    >
    > On Wed, 9 Apr 2003 Shalom.Bresticker@motorola.com wrote:
    >
    > > I would like to do the following additional work for Draft 1:
    > >
    > >
    > > (A) Implement change of table and figure numbering from consecutive to by
    > > section. This is by itself almost trivial. The additional work comes from the
    > > fact that some of the references to tables and figures in the text were
    > > implemented as regular text instead of as FrameMaker cross-references. These
    > > will not be updated automatically when I change the numbering style.
    > >
    > > I already have gone through the entire text of the LRM and circled all the cases
    > > I found of such non-linked references. I am sure I found almost all of them.
    > > I just have to fix them one by one. I have already done so through page 250. I
    > > just have to finish the work. It is not hard, but takes a little time.
    > >
    > > After that, changing the numbering style and updating the cross-references is
    > > easy. By the way, I have implemented the cross-references as underlined bold
    > > blue. In PDF, they will be hyperlinks as well.
    > >
    > >
    > > (B) I need to meet IEEE requirements for standard drafts by changing the page
    > > headers and footers accordingly, and the introductory page as well.
    > >
    > >
    > > The draft contains a number of editorial corrections which are also not listed
    > > as vsgpassed issues. These are of the sort that are obvious and trivial and
    > > required. Some of these, like spelling and grammar errors, or bad fonts or line
    > > breaks, may not be listed as issues at all. Others are listed as issues, but not
    > > yet vsgpassed, but I did them anyway for one reason or another.
    > >
    > >
    > > I added an additional annex I in which I log the changes I made each day, in
    > > varying degrees of detail. Where the change is associated with an issue number,
    > > I listed the issue number. There are a few changes I made of the type that the
    > > issue has not yet been passed where I did not yet list the issue number. These
    > > are of the trivial type, though.
    > >
    > > For each entry, I also noted whether I added change bars. I used the criterion I
    > > previously proposed, of "significant" changes, one which changes the original
    > > meaning (even if it was obviously incorrect). If anyone finds a case where I did
    > > not add a change bar, but should have, tell me.
    > >
    > > I added change bars, but not boxes in the margins with the issue #s.
    > > That could be done if needed, in the future.
    > >
    > > Should I start color-coding change bars in future drafts?
    > >
    > >
    > > I have another 3 days of work, I think, before Passover vacation. I will make
    > > every effort to produce Draft 1 by then and send it to Stefen Boyd. I will not
    > > have access to FrameMaker (or web access)
    > > probably from next Tuesday or Wednesday until Thursday
    > > the following week, except Monday April 21, when I intend to come to work for
    > > the ETF conference call. I will be following my email most of the time though.
    > >
    > >
    > > In general, I work on implementing vsgpassed issues on an ongoing basis, so that
    > > Draft 2 will have the additional changes I will do during the month and a half
    > > inbetween, including new Table of Contents and Index. I think for the drafts, we
    > > should add List of Tables, List of Figures, and List of Syntax Boxes as well,
    > > even though IEEE will not allow them in the final version.
    > >
    > > Shalom
    > >
    > >
    > > On Tue, 8 Apr 2003, Michael McNamara wrote:
    > >
    > > > Talking with Stefen, we'd like you to produce a PDF of Draft One of
    > > > 1364-2005 with all of the lrmdraft issues in place (from looking at
    > > > <http://www.boyd.com/1364_btf/report/vsgpassed.html> it appears there
    > > > are more 70 in this state)
    > > >
    > > > Stefen will put this up at boyd.com; and then we can review this, with
    > > > a goal of submitting corrections so that we can produce a Draft Two in
    > > > time for the Design Automation Conference (if necessary). Draft two
    > > > might also include additional lrmdraft issues you complete after
    > > > creation of Draft One.
    > > >
    > > > What are your thoughts?
    > > >
    > > > When do you think we could have a Draft one?
    > > >
    > > >
    > >
    > >
    >
    > --
    > Shalom Bresticker Shalom.Bresticker@motorola.com
    > Design & Reuse Methodology Tel: +972 9 9522268
    > Motorola Semiconductor Israel, Ltd. Fax: +972 9 9522890
    > POB 2208, Herzlia 46120, ISRAEL Cell: +972 50 441478

    This archive was generated by hypermail 2.1.4 : Wed Apr 09 2003 - 12:11:58 PDT and
    sponsored by Boyd Technology, Inc.