Re: [6tisch] removing the 'e'

Tom Phinney <tom.phinney@cox.net> Mon, 30 March 2015 21:56 UTC

Return-Path: <tom.phinney@cox.net>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 102371A066B for <6tisch@ietfa.amsl.com>; Mon, 30 Mar 2015 14:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.466
X-Spam-Level: **
X-Spam-Status: No, score=2.466 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_50=0.8, FSL_HELO_BARE_IP_2=1.675, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7_-Iy4-LNA2T for <6tisch@ietfa.amsl.com>; Mon, 30 Mar 2015 14:56:41 -0700 (PDT)
Received: from fed1rmfepo101.cox.net (fed1rmfepo101.cox.net [68.230.241.143]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA4F1A0439 for <6tisch@ietf.org>; Mon, 30 Mar 2015 14:56:41 -0700 (PDT)
Received: from fed1rmimpo305 ([68.230.241.173]) by fed1rmfepo101.cox.net (InterMail vM.8.01.05.15 201-2260-151-145-20131218) with ESMTP id <20150330215640.JBCH32482.fed1rmfepo101.cox.net@fed1rmimpo305> for <6tisch@ietf.org>; Mon, 30 Mar 2015 17:56:40 -0400
Received: from 192.168.1.110 ([68.110.82.164]) by fed1rmimpo305 with cox id 9xwf1q00P3YjG0401xwgxJ; Mon, 30 Mar 2015 17:56:40 -0400
X-CT-Class: Clean
X-CT-Score: 0.00
X-CT-RefID: str=0001.0A020205.5519C698.01C7,ss=1,re=0.000,fgs=0
X-CT-Spam: 0
X-Authority-Analysis: v=2.0 cv=d5crP2fE c=1 sm=1 a=/lROMdMM8hnpqyhFWVF1XA==:17 a=CA33sFktnKwA:10 a=kviXuzpPAAAA:8 a=FuZHt-YyMucgtjQ_hO0A:9 a=QEXdDO2ut3YA:10 a=_W_S_7VecoQA:10 a=NyKyqcUa3GVnZkUc:21 a=geVs9FwiuVejqbAw:21 a=DC5giP99AAAA:8 a=-HgQR5d-s7rmobDvz1EA:9 a=Xl81_ENzj19cqPOQKZ0A:9 a=/lROMdMM8hnpqyhFWVF1XA==:117
X-CM-Score: 0.00
Authentication-Results: cox.net; none
Message-ID: <5519C697.4040405@cox.net>
Date: Mon, 30 Mar 2015 14:56:39 -0700
From: Tom Phinney <tom.phinney@cox.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: 6tisch@ietf.org
References: <9rQ51q00P0xxhYs01rQ6wU>
In-Reply-To: <9rQ51q00P0xxhYs01rQ6wU>
Content-Type: multipart/mixed; boundary="------------050603020602080209060503"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/AmRFlSeykR3SqeJ3YA-z_vsRGok>
Subject: Re: [6tisch] removing the 'e'
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Tom Phinney <tom.phinney@cox.net>
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Mar 2015 21:56:44 -0000

Dear all:

I was contributing a comment on this subject via the chat channel when the Thursday meeting closed. Diego, who was managing the chat channel, captured it and we subsequently have had the attached exchange.

In ISO and IEC standards the practice is to list the generic document within the list of Normative References unless there are explicit references to specific subclauses of the referenced document, in which case a specific edition needs to be called out because subclause numbering often change from one edition to the next.

Thus, if a 6tisch document references subclause m.n.p within the new 2015 edition of IEEE802.15.4, the reference would be to IEEE802.15.4:2015, m.n.p. Otherwise the reference WITHIN the standard is simply to IEEE802.15.4, without qualification as to the specific edition. While such an unqualified reference presumes that material on the referenced topic will not disappear from future editions of IEEE802.15.4, such an assumption is almost always valid and leads to much less confusion by those trying to use the standard over its lifetime.

The specific wording to cover both dated and undated references that the latest version of the ISO/IEC editing directives itself uses is:
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.

The related text from the ISO/IEC editing directives with regard to use of Normative References is:
6.2.2 Normative references

This conditional element shall give a list of the referenced documents cited (see 6.6.7.5) in
the document in such a way as to make them indispensable for the application of the
document. For dated references, each shall be given with its year of publication, or, in the
case of enquiry or final drafts, with a dash together with a footnote “To be published.”, and full
title. The year of publication or dash shall not be given for undated references. When an
undated reference is to all parts of a document, the publication number shall be followed by
the indication “(all parts)” and the general title of the series of parts (i.e. the introductory and
main elements, see Annex E).

In principle, the referenced documents shall be documents published by ISO and/or IEC.
Documents published by other bodies may be referred to in a normative manner provided that
a) the referenced document is recognized by the ISO and/or IEC committee concerned as
having wide acceptance and authoritative status as well as being publicly available,
b) the ISO and/or IEC committee concerned has obtained the agreement of the authors or
publishers (where known) of the referenced document to its inclusion and to its being
made available as required — the authors or publishers will be expected to make
available such documents on request,
c) the authors or publishers (where known) have also agreed to inform the ISO and/or IEC
committee concerned of their intention to revise the referenced document and of the
points the revision will concern, and
d) the ISO and/or IEC committee concerned undertakes to review the situation in the light of
any changes in the referenced document.

The list shall be introduced by the following wording:
“The following documents, in whole or in part, are normatively referenced in this
document and are indispensable for its application. For dated references, only the edition
cited applies. For undated references, the latest edition of the referenced document
(including any amendments) applies.”

The above wording is also applicable to a part of a multipart document.

The list shall not include the following:
• referenced documents which are not publicly available;
• referenced documents which are only cited in an informative manner;
• referenced documents which have merely served as bibliographic or background material
in the preparation of the document.

Such referenced documents may be listed in a bibliography (see 6.4.2).

An example from the same ISO/IEC Directives, Part 2 document demonstrates proper dated-citation usage, including usage of the date only as necessary to reduce ambiguity:
D.1.1 Scope of rules and examples provided in Annex D

Annex D provides a synthesis of the rules and examples given in ISO 10241-1:2011, and is
intended to cover those rules applicable to the forms of terms and definitions most commonly
present in ISO and IEC standards. For the complete set of rules and examples, refer to
ISO 10241-1.



It seems likely that actual references to the 2015 edition of IEEE802.15.4 will, in fact, need to cite specific subclauses. If that is the case, then this entire discussion of whether or not to cite the edition is moot, because such citations are essential to ensure that any specific sublclause references actually point to relevant text.

-Tom

--- Begin Message ---
Tom,
       I think what you say is completely relevant to
discuss on 6tisch so as to keep the references correct
and coherent among the documents.
      I encourage you to send these comments to the
ML, or, if you wish, I can do it for you (referencing you
as the author, of course).
     I hope to see you on the next 6tisch webex call, which
should be announced soon.
     Tell me what you think about this.
     Thank you.
     Regards,

                            Diego Dujovne


2015-03-26 13:59 GMT-03:00 Tom Phinney <tom.phinney@cox.net>et>:

>  I saw that the meeting was concluding just as I finished typing. My
> comment was about the general nature of references. I agree with Pat Kinney
> that references need to be to the current edition, which requires updates
> to specs that cite subclause numbers. That's why it's best not to cite such
> numbers. The standard text at the start of Clause 2, the Normative
> Reference clause, in IEC and ISO standards is
>
> The following referenced documents are indispensable for the application
> of this document. For dated references, only the edition cited applies. For
> undated references, the latest edition of the referenced document
> (including any amendments) applies.
>
> Thus most references can be to the current edition, whatever that is,
> meaning that the normative reference lists the document but not the edition
> or publication date. However, when it is necessary to cite within the
> specification specific subclause numbers of another document, which can
> change from one edition to another of that second document, then the
> edition listed in the normative references section must be dated.
>
>
> As to whether I can participate in the next 6tisch interim meeting, that,
> as always, depends on the date and time of the meeting. I participated on
> Monday and early this morning because it fit my schedule. However, I should
> have left for a class after the first hour. Instead I stayed on the
> connection until there was an unintended loss of connection, then
> reconnected to hear the end of the session.
> ===
>
> On 2015.03.26 09:41, Prof. Diego Dujovne wrote:
>
>    Tom,
>         Your last comment could not be included.
>  Would you be able to participate on the next 6tisch
>  interim meeting and reproduce that comment please?
>
> "Tom Phinney: An unqualified reference to a standard implies the edition
> listed in the normative references, which needs to specify either issue
> date (year) or edition. Any subclause references should be to that edition."
>
>  Thank you!
>  Regards,
>
>                         Diego Dujovne
>
> --
> DIEGO DUJOVNE
> Académico Escuela de Ingeniería en Informática y Telecomunicaciones
> Facultad de Ingeniería UDP
> www.ingenieria.udp.cl
> (56 2) 676 8125
>
>
>


-- 
DIEGO DUJOVNE
Académico Escuela de Ingeniería en Informática y Telecomunicaciones
Facultad de Ingeniería UDP
www.ingenieria.udp.cl
(56 2) 676 8125
--- End Message ---