From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org Fri May 28 04:58:55 2021 Return-Path: X-Original-To: sc22wg5-dom9 Delivered-To: sc22wg5-dom9@www.open-std.org Received: by www.open-std.org (Postfix, from userid 521) id 34109358C55; Fri, 28 May 2021 04:58:55 +0200 (CEST) Delivered-To: sc22wg5@open-std.org Received: from nag-j.co.jp (bvdeuz19.secure.ne.jp [180.222.80.19]) by www.open-std.org (Postfix) with SMTP id 0EC133587A5 for ; Fri, 28 May 2021 04:58:52 +0200 (CEST) Received: (qmail 5850 invoked from network); 28 May 2021 11:58:49 +0900 Received: from unknown (HELO Maru10) (218.42.159.105) by 0 with SMTP; 28 May 2021 11:58:49 +0900 From: "Malcolm Cohen" To: "'WG5 List'" References: <390726e2-06d1-5141-63f9-18115901ba43@dmk.com> <20210528002245.0ACE5358AF5@www.open-std.org> In-Reply-To: <20210528002245.0ACE5358AF5@www.open-std.org> Subject: RE: [ukfortran] (SC22WG5.6340) Fwd: 2021 Directives part 2 change regarding TRs Date: Fri, 28 May 2021 11:58:49 +0900 Message-ID: <00e201d7536d$6279f760$276de620$@nag-j.co.jp> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00E3_01D753B8.D2634D10" X-Mailer: Microsoft Outlook 16.0 Content-Language: ja Thread-Index: AQINnZBPZk8iwF6kfmFDkOpaqH4CzgGPjZ50qn8iwuA= Sender: owner-sc22wg5@open-std.org Precedence: bulk This is a multipart message in MIME format. ------=_NextPart_000_00E3_01D753B8.D2634D10 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Steve, =20 This does not affect us, because what used to be called TRs (back when = we did them) became Technical Specifications. Indeed, the last one we = published started out intending to be a TR but we published it as a TS. =20 Cheers, --=20 ..............Malcolm Cohen, NAG Oxford/Tokyo. =20 From: Steve Lionel =20 Sent: Friday, May 28, 2021 9:23 AM To: WG5 List Subject: [ukfortran] (SC22WG5.6340) Fwd: 2021 Directives part 2 change = regarding TRs =20 Not that we're doing any TRs at the moment, but in case we do... -------- Forwarded Message --------=20 Subject:=20 2021 Directives part 2 change regarding TRs Date:=20 Thu, 27 May 2021 17:07:19 -0700 From:=20 David Keaton To:=20 =09 CC:=20 Bill Ash Dear SC 22 Convenors, There is a change in the 2021 Directives part 2 that affects some SC 22 = TRs. TRs are now forbidden to contain recommendations. The "Note 3 to = entry" below is new as of this month. --- 3.1.8 Technical Report TR document (3.1.1) published by ISO or IEC containing collected data of a = different kind from that normally published as an International Standard = (3.1.4) or Technical Specification (3.1.5) Note 1 to entry: Such data may include, for example, data obtained from = a survey carried out among the national bodies, data on work in other = international organizations or data on the state of the art (3.4) in = relation to standards of national bodies on a particular subject. Note 2 to entry: Prior to mid-1999, Technical Reports were designated as = Technical Reports of type 3. Note 3 to entry: The content of a Technical Report is not permitted to = include requirements (3.3.3), recommendations (3.3.4) or permissions = (3.3.5). --- It was always understood that TRs could not contain normative text, but = this goes further. TRs that contain guidance, as some SC 22 TRs do, will = need to become International Standards if they are revised. New editions = will be scrutinized according to the prohibition against = recommendations. I hope this will save you from finding out at the last minute that extra = work will be required when revising some TRs. David ------=_NextPart_000_00E3_01D753B8.D2634D10 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi Steve,

This does = not affect us, because what used to be called TRs (back when we did = them) became Technical Specifications. Indeed, the last one we published = started out intending to be a TR but we published it as a = TS.

Cheers,

--

..............Malcolm Cohen, NAG = Oxford/Tokyo.

From: Steve Lionel = <steve@stevelionel.com>
Sent: Friday, May 28, 2021 9:23 = AM
To: WG5 List = <sc22wg5@open-std.org>
Subject: [ukfortran] = (SC22WG5.6340) Fwd: 2021 Directives part 2 change regarding = TRs

Not that = we're doing any TRs at the moment, but in case we = do...

-------- Forwarded = Message --------

Subject:	2021 Directives = part 2 change regarding TRs
Date: =	Thu, 27 May 2021 17:07:19 = -0700
From:	David Keaton <dmk@dmk.com>
To: =
CC:	Bill Ash <bash@itic.org>

Dear SC 22 = Convenors,

There is a change in the 2021 Directives part 2 that = affects some SC 22 TRs. TRs are now forbidden to contain = recommendations. The "Note 3 to entry" below is new as of this = month.

---

3.1.8

Technical = Report

TR

document (3.1.1) published by ISO or IEC = containing collected data of a different kind from that normally = published as an International Standard (3.1.4) or Technical = Specification (3.1.5)

Note 1 to entry: Such data may include, for = example, data obtained from a survey carried out among the national = bodies, data on work in other international organizations or data on the = state of the art (3.4) in relation to standards of national bodies on a = particular subject.

Note 2 to entry: Prior to mid-1999, Technical = Reports were designated as Technical Reports of type 3.

Note 3 to = entry: The content of a Technical Report is not permitted to include = requirements (3.3.3), recommendations (3.3.4) or permissions = (3.3.5).

---

It was always understood that TRs could not = contain normative text, but this goes further. TRs that contain = guidance, as some SC 22 TRs do, will need to become International = Standards if they are revised. New editions will be scrutinized = according to the prohibition against recommendations.

I hope this = will save you from finding out at the last minute that extra work will = be required when revising some = TRs.

David

------=_NextPart_000_00E3_01D753B8.D2634D10--