[J3] [SC22WG5.6514] RE: [ukfortran] Fwd: [SC 22 Convenors] JTC 1 plenary wrap-up - Electronic attachments to standard

[Gary Klimowicz]

It's about it being in plain text, not in PDF form. As an Annex, they're difficult to manipulate textually.

As plain text, I can image tools we could write for automatically generating parser definitions (especially for formal definition tools like SDF or Maude). Identifying changes between version would be much easier.

I also heard from some of the Flang developers that it would have been helpful to be able to map the constraint numbers and to highlight textual differences in the constraints between versions of the standard.



> On Nov 21, 2023, at 09:54, Long, Bill F <william.long at hpe.com> wrote:
> 
> Such lists would seem more natural in an Annex as part of the standard. 
> 
> 
> From: J3 <j3-bounces at mailman.j3-fortran.org> on behalf of Gary Klimowicz via J3 <j3 at mailman.j3-fortran.org>
> Sent: Tuesday, November 21, 2023 11:32 AM
> To: General J3 interest list <j3 at mailman.j3-fortran.org>
> Cc: Gary Klimowicz <gak at dancingbear.dev>; WG5 List <sc22wg5 at open-std.org>; Malcolm Cohen <malcolm at nag-j.co.jp>
> Subject: Re: [J3] [SC22WG5.6512] RE: [ukfortran] Fwd: [SC 22 Convenors] JTC 1 plenary wrap-up - Electronic attachments to standard
>  
> I can imagine it would also be helpful to attach as separate text files a list of the rules and a list of the constraints.
> 
>> On Nov 20, 2023, at 22:47, Malcolm Cohen via J3 <j3 at mailman.j3-fortran.org> wrote:
>> 
>> It would have been useful many years ago, for the source code of the ISO_VARYING_STRING module.
>>  
>> Van suggests:
>> > Could we publish the "standard" as an abstract on paper, and the "real" standard as an electronic attachment?
>>  
>> No. The normative text has to be part of the standard.
>>  
>> Cheers,
>> -- 
>> ..............Malcolm Cohen, NAG Oxford/Tokyo.
>>  
>> From: Steve Lionel <steve at stevelionel.com <mailto:steve at stevelionel.com>> 
>> Sent: Tuesday, November 21, 2023 6:03 AM
>> To: WG5 List <sc22wg5 at open-std.org <mailto:sc22wg5 at open-std.org>>
>> Subject: [ukfortran] [SC22WG5.6510] Fwd: [SC 22 Convenors] JTC 1 plenary wrap-up - Electronic attachments to standard
>>  
>> Interesting concept - I wonder if there's anything we can do with it.
>> -------- Forwarded Message -------- 
>> Subject: 
>> Re: [SC 22 Convenors] JTC 1 plenary wrap-up
>> Date: 
>> Mon, 20 Nov 2023 12:45:33 -0800
>> From: 
>> David Keaton <dmk at dmk.com> <mailto:dmk at dmk.com>
>> To: 
>> 
>> 
>> Dear SC 22 Convenors,
>> 
>> There is one item I forgot to mention from last week's JTC 1 plenary meeting. ISO and IEC have approved the concept of "electronic attachments" to standards. These have several interesting properties.
>> 
>> * Electronic attachments are distributed together with the standard, so anyone who buys the standard has the attachments.
>> 
>> * An electronic attachment can contain any kind of data, such as a machine-readable grammar for a programming language, a sample computer program, pictures, databases, or even text. Text attachments might include such things as a list of identifiers, a cross-reference list, or a change history of the standard. ISO and IEC do not need to know how to process the attachments; they are only for use by the customers of the standard.
>> 
>> * Customers are charged by the page of the standard. Electronic attachments are not counted; they are included for free. Consequently, some items that might otherwise have resulted in large annexes could instead be submitted as electronic attachments, giving customers access to the same data for less money.
>> 
>> Electronic attachments create some pretty exciting possibilities, and I hope you will keep them in mind during standards development.
>> 
>> David

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20231121/7344455c/attachment-0001.htm>