(j3.2006) please update 08-252 to contain the name of the submitter of the F08 public comment
Bill Long
longb
Wed Jul 9 18:08:01 EDT 2008
Dan Nagle wrote:
> Hi,
>
> My view is that the submitter should be included
> in the summary, but that the email address should not.
>
OK. Dan and Steve have convinced me this is the right course of action.
Cheers,
Bill
> Unfortunately, 08-193 is no help here.
>
> A good many of these public comments were discussed
> in various public forums, and the submitter
> may expect, and certainly deserves, a response.
> The responses will likely also be discussed publicly.
> It is hard for me to understand the applicability
> of state privacy law to a public comment submitted
> to a committee acting in an international capacity.
> IANAL and there are many things I do not understand. :-)
>
> These comments are, after all, already publicly available
> as J3 documents. So they are available anyway,
> including their "reply-to:" fields. The J3 reply
> document will also be publicly available as a J3 document,
> that will include discussion of the comment as well as
> the comment itself.
>
> J3 is a public process by law.
>
> On Jul 9, 2008, at 4:40 PM, Lionel, Steve wrote:
>
>
>> I would recommend against including email addresses, as they WILL get
>> "scraped" by spammers. The list of names with emails should be kept
>> private by the committee. I do agree that the names of the submitters
>> should be made available.
>>
>> If these comments were sent by email, I don't see how laws regulating
>> web sites are relevant.
>>
>> Steve
>>
>>
>>> -----Original Message-----
>>> From: j3-bounces at j3-fortran.org [mailto:j3-bounces at j3-fortran.org] On
>>> Behalf Of Bill Long
>>> Sent: Wednesday, July 09, 2008 4:25 PM
>>> To: fortran standards email list for J3
>>> Subject: Re: (j3.2006) please update 08-252 to contain the name of
>>> the
>>> submitter of the F08 public comment
>>>
>>> An email address where a response could be sent might also be useful.
>>> These are, after all, PUBLIC comments, so there should not be secrets
>>> about who is making a PUBLIC comment.
>>>
>>> Cheers,
>>> Bill
>>>
>>>
>>> Whitlock, Stan wrote:
>>>
>>>> Michael,
>>>>
>>>>
>>>>
>>>> Please revise paper 08-252 to include the name of the submitter for
>>>> each F08 public comment we received.
>>>>
>>>>
>>>>
>>>> Thanks /Stan
>>>>
>>>>
>>>>
>>>> 08-252
>>>>
>>>> To: J3
>>>>
>>>> From: Michael Ingrassia
>>>>
>>>> Subject: summary of public comments
>>>>
>>>> Date: 2008 July 08
>>>>
>>>>
>>>>
>>>> Tracking Date
>>>>
>>>> number Paper number received Topic
>>>>
>>>> J32001 08-209r1.txt 06-08 NEWUNIT= specifier and NEWUNIT
>>>>
>>> value
>>>
>>>> J32002 08-210r1.txt 06-10 Conversions between different
>>>> character kinds
>>>>
>>>> J32003 08-211r1.txt 06-16 BESSEL_YN and BESSEL_JN
>>>>
>> intrinsic
>>
>>>> functions
>>>>
>>>> J32004 08-218.txt 07-02 F2008 too early
>>>>
>>>> J32005 08-219.txt 07-03 Coarrays should be optional
>>>>
>>>> J32006 08-220.txt 07-03 Restore the restrictions on
>>>> internal procedures
>>>>
>>>> J32007 08-221.txt 07-03 the official interpretations
>>>> should be examined
>>>>
>>>> J32008 08-222.txt 07-03 generic resolution
>>>>
>>>> J32009 08-223.txt 07-03 File position and the left tab
>>>>
>>> limit
>>>
>>>> J32010 08-224.txt 07-03 constraint C542
>>>>
>>>> J32011 08-225.txt 07-03 define entity
>>>>
>>>> J32012 08-226.txt 07-03 attributes
>>>>
>>>> J32013 08-227.txt 07-03 additional intrinsic functions
>>>>
>>>> J32014 08-228.txt 07-03 definition of vector subscript
>>>>
>>>> J32015 08-229.txt 07-03 assumed constraints for names
>>>>
>>>> J32016 08-230.txt 07-03 advice regarding additional
>>>> intrinsics ignores
>>>>
>>>> J32017 08-231.txt 07-03 typographical error in CMPLX
>>>>
>>>> J32018 08-232.txt 07-03 imprecise description of
>>>>
>>> constraints
>>>
>>>> J32019 08-233.txt 07-03 undue claims concerning
>>>>
>>> compatibility
>>>
>>>> J32020 08-234.txt 07-03 constraint C538
>>>>
>>>> J32021 08-235.txt 07-03 Allow compatible specific
>>>>
>>> interfaces
>>>
>>>> J32022 08-236.txt 07-03 allow multiple generic
>>>>
>>> interfaces
>>>
>>>> that
>>>>
>>>> J32023 08-237.txt 07-03 zeros and sign control
>>>>
>>>> J32024 08-238.txt 07-03 pick a model of generic
>>>>
>>> intrinsics
>>>
>>>> J32025 08-239.txt 07-03 types declared to be PRIVATE
>>>>
>>>> J32026 08-240.txt 07-03 implicit typing should not be
>>>> allowed in derived
>>>>
>>>> J32027 08-241.txt 07-03 definition is poorly defined
>>>>
>>>> J32028 08-242.txt 07-03 the EXTERNAL attribute
>>>>
>>>> J32029 08-243.txt 07-03 Fix error in type equivalence
>>>>
>>>> J32030 08-244.txt 07-03 derived-type equivalence
>>>>
>>>> J32031 08-245.txt 07-03 equivalence of circular types
>>>>
>>>> J32032 08-246.txt 07-06 New intrinsic procedures
>>>>
>>>> J32033 08-247.txt 07-06 LEADZ and TRAILZ
>>>>
>>>> J32034 08-248.txt 07-06 CRITICAL and BLOCK
>>>>
>>>> J32035 08-249.txt 07-06 IMPURE ELEMENTALs
>>>>
>>>> J32036 08-250.txt 07-06 Submodules
>>>>
>>>> J32037 08-251.txt 07-06 The g0 edit descriptor
>>>>
>>>>
>>>>
>> ---------------------------------------------------------------------
>>
>>> ---
>>>
>>>> _______________________________________________
>>>> J3 mailing list
>>>> J3 at j3-fortran.org
>>>> http://j3-fortran.org/mailman/listinfo/j3
>>>>
>>>>
>>> --
>>> Bill Long longb at cray.com
>>> Fortran Technical Support & voice: 651-605-9024
>>> Bioinformatics Software Development fax: 651-605-9142
>>> Cray Inc., 1340 Mendota Heights Rd., Mendota Heights, MN, 55120
>>>
>>>
>>>
>>> _______________________________________________
>>> J3 mailing list
>>> J3 at j3-fortran.org
>>> http://j3-fortran.org/mailman/listinfo/j3
>>>
>> _______________________________________________
>> J3 mailing list
>> J3 at j3-fortran.org
>> http://j3-fortran.org/mailman/listinfo/j3
>>
>
>
--
Bill Long longb at cray.com
Fortran Technical Support & voice: 651-605-9024
Bioinformatics Software Development fax: 651-605-9142
Cray Inc., 1340 Mendota Heights Rd., Mendota Heights, MN, 55120
More information about the J3
mailing list