[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
Editorial review of 7/1/04 version of our draft...
Hello All,
I just received a review of our draft from the perspective
of the Program Manager of the IEEE Standards group.
I include her review verbatim together with my comments.
They are largely of a syntactic nature with one major
exception.
Mike: We must make sure that all our ducks are in a row
with respect to IBM's DPD patent & our permission to use
it. She describes what is required below.
We can edit them into the draft any time. And, given our
current issues, I'd say this should be largely a matter of
the convenience of the editor.
See you all on the 21st.
Until then,
Dan
> Subject: Re: editorial review of P754
> To: r754@xxxxxxxxxxxxxx
> Cc: a.ickowicz@xxxxxxxx, knoppix@xxxxxxxxx, r754@xxxxxxxxxxxxxx
> From: n.humenick@xxxxxxxx
> Date: Sun, 11 Jul 2004 19:59:09 -0400
>
>
> Hi Dan:
>
>
> --
> Noelle D. Humenick
> Coordinating Program Manager
> IEEE Standards
> n.humenick@xxxxxxxx
> PH: +1 732 562 3818; FX: +1 732 562 1571
> http://standards.ieee.org/
>
> The Institute of Electrical and Electronics Engineers, Inc.
> 445 Hoes Lane, PO Box 1331, Piscataway, NJ 08855-1331 USA
>
> ***************************************
>
>
>
> r754@xxxxxxxxxxxx
> om To: n.humenick@xxxxxxxx
> Sent by: cc: r754@xxxxxxxxxxxxxx, a.ickowicz@xxxxxxxx
> knoppix@xxxxxxxxx Subject: Re: editorial review of P754
>
>
> 07/11/2004 03:11
> PM
>
>
>
>
>
>
> > Subject: editorial review of P754
> > To: r754@xxxxxxxxxxxxxx
> > Cc: a.ickowicz@xxxxxxxx
> > From: n.humenick@xxxxxxxx
> > Date: Sun, 11 Jul 2004 12:07:23 -0400
> >
> > Dear Dan:
> >
> > I have reviewed draft July 1, 2004 of P754, and I have the following
> > comments. Please note that this review has been organized into two
> > sections:
> >
> > 1. Items/issues that shall be resolved before the ballot begins
> > 2. Items/issues that shall be resolved before submission to RevCom
> >
> >
> > Items/issues that shall be resolved before the ballot begins
> >
> > The title of the document shall be in the following format
> > Draft Standard for Floating... (remove "American National Standard"
> and
> > "IEEE" from the title)
> > Also, the title shall match that on the PAR. Your current title does
> > not.
>
> OK.
>
> >
> > The correct standard designation shall appear in the upper right
> corner
> > of every page, including the body of the standard. For your draft the
> > correct designation is P754/Dx (indicating the draft number) current
> > date.
>
> OK.
>
> >
> > The scope shall match the latest PAR. The scope in this document is
> > different. Narrowing the technical focus of the standard is acceptable
> > in the scope, but if it is a change or an expansion, the PAR shall be
> > updated.
>
> The scope & purpose was one of the last things we wanted
> to write. But when it is written, I'm sure we can make
> sure both the document & the standard match.
>
> Okay, just bear in mind that your PAR will need to match the title, scope,
> and purpose of the document before the ballot starts.
>
> >
> > The Annexes shall be labeled using capital letters. Thus, the first
> > annex is Annex A, followed by the word informative or normative. The
> > rest of the annex is numbered using the capital letter A, followed by
> > the clause number (e.g., A.1, A.1.1, A.1.2).
>
> OK. Must they necessarily be, A followed by B & so on?
> The current letters have a meaning for us (for example,
> L is for Language) but, I suppose, it is not important
> for the final draft.
>
> I understand, but it should be A, B, etc.
>
> >
> > If you decide to incorporate any other standards by reference, create
> > Clause 3, References. Use one of the following introductory sentences
> as
> > appropriate. If you would like the user to use the most recent edition
> > of the published standards listed in the reference clause, use the
> > following sentence. References will be updated during the final
> > publication process if this introductory sentence appears.
> > This standard shall be used in conjunction with the following
> > publications. When a referenced standard is superseded by an
> > approved revision, the revision shall apply.
>
> OK. This has not yet been necessary but I can see the
> possibility of reference the C99 standard in (current)
> Annex L.
>
> >
> > When you are ready to ballot this draft, please remove all change
> bars,
> > underlined text, or multi-colored text.
>
> This was always our intention. Also, all purple text
> will be deleted from the final draft as it contains
> editorial comments to ourselves.
>
> >
> > Items/issues that shall be resolved before submission to RevCom
>
> The general description below sounds like a paper being
> submitted to a peer-reviewed publication. Is that the
> case?
>
> RevCom is the review committee of the Standards Board.
>
> >
> > Abstract and keywords shall be supplied.
> > Introduction shall be supplied.
> > Permission is required for excerpted text, tables, and figures, if
> there
> > are any.
>
> In order: OK. OK. None that I am aware of.
>
> > If this standard uses a trademark owned by an entity other than IEEE
> or
> > requires the use of patented technology, please see IEEE Standards
> Style
> > Manual for text required when trademarks or patents exist.
>
> There is a formal agreement between this committee
> & IBM over the use of the term DPD (Densely Packed
> Decimal) & the associated patent.
>
> You'll need to ensure that a letter of assurance is on file with the patent
> committee of the standards board. Also, you'll want to incorporate the
> following boilerplate to the front matter of your document. See the
> following excerpt from our policies.
>
> Patents
> [The following notice shall appear when the IEEE receives assurance from
> a known patent holder or patent applicant prior to the time of
> publication that a license will be made available to all applicants
> either without compensation or under reasonable rates, terms, and
> conditions that are demonstrably free of any unfair discrimination.]
>
>
> Attention is called to the possibility that implementation of this
> standard may require use of subject matter covered by patent rights. By
> publication of this standard, no position is taken with respect to the
> existence or validity of any patent rights in connection therewith. The
> IEEE shall not be responsible for identifying patents or patent
> applications for which a license may be required to implement an IEEE
> standard or for conducting inquiries into the legal validity or scope of
> those patents that are brought to its attention. A patent holder or
> patent applicant has filed a statement of assurance that it will grant
> licenses under these rights without compensation or under reasonable
> rates and nondiscriminatory, reasonable terms and conditions to
> applicants desiring to obtain such licenses. The IEEE makes no
> representation as to the reasonableness of rates, terms, and conditions
> of the license agreements offered by patent holders or patent
> applicants. Further information may be obtained from the IEEE Standards
> Department.
>
>
> [If the IEEE has not received letters of assurance prior to the time of
> publication, the following notice shall appear:]
>
>
> Attention is called to the possibility that implementation of this
> standard may require use of subject matter covered by patent rights. By
> publication of this standard, no position is taken with respect to the
> existence or validity of any patent rights in connection therewith. The
> IEEE shall not be responsible for identifying patents or patent
> applications for which a license may be required to implement an IEEE
> standard or for conducting inquiries into the legal validity or scope of
> those patents that are brought to its attention.
>
> > Metric values shall be used. Inch-pound values may be used and
> shall
> > follow the metric values in parenthesis if they are represented.
> (see
> > SI 10TM-2002)
>
> All quantities are either pure numbers (without any
> metric dimensionality) or NaNs.
>
> > Separate electronic files of figures shall be supplied in one of
> the
> > following formats: .tiff, .eps, or .jpeg.
>
> OK.
>
>
>
>
> Noelle,
>
> May I have your permission to pass your review on to the
> full committee together with my comments?
>
> Sure, no problem.
>
> That would be the easiest way to get them into the text.
>
> Thanks for spending your time on this.
>
> You're welcome.
>
> Regards,
> Noelle
>