[NeXus-tech] [NeXus-committee] NeXus paper V7

[yayahjb]

Suggested corrections by Frances C. Bernstein and Herbert J. Bernstein:

p. 1, l. 8, change "Labortaory" to "Laboratory"
p. 1, l. 9, change "College" to "College,"
p. 1, l. 15, change "ANSTO" to "ANSTO,"
p. 1, l. 26, change "domain specific" to "domain-specific"
p. 1, l. 33, change "neutron,data" to "neutron, data"

p. 1, col. 1, l. 6, change "choose" to "have chosen"
p. 1, col. 1, l. -2, change "become impractical" to "have become 
impractical"
p. 1, col. 2, l. 4-5, change "self describing" to "self-describing"
p. 1, col. 2, l. 5, change "platform independent" to "platform-independent"

p. 2, col. 1, l. 19, change, "to NeXus" to "in NeXus"
p. 2, col. 1, l. 22, change "application" to "applications"
p. 2, col. 1, l. 26, change "Sect V" to "Sect. V"
p. 2, col. 1, l. 32, change "application definition, or" to "an 
application definition, or a"

p. 3, col. 1, l. 8, change "to store the results" to "storing the results"
p. 3, col. 1, l. 11, change "stored at" to "stored at the"
p. 3, col. 1, l. 20, change "that in practice" to "that, in practice"

p. 3, col. 2, l. 5, change "equivalent or better" to "equivalent to or 
better"
p. 3, col. 2, l. 13, change "volmes" to "volumes"

p. 4, col. 2, l. 4, change, "scientists from NeXus and the IUCr" to 
"scientists representing both
the NeXus International Advisory Committee and the IUCr Committee on the 
Maintenance
of the CIF standard"

p. 5, col. 1, l. 2-6, change "In the past, NeXus supported data files in 
HDF-4, HDF5, and
XML file formats.  To support writing software to read and write the 
file formats, the
NeXus application/programmer interface (NeXus-API) was provided.  This 
API is
maintained at a bug fix level.  On request of the community, we now 
concentrate
our efforts only on HDF5 files and tools.  The recommended way to write 
NeXus
files is now through the use of HDF-5 tools."
  to

"Historically, NeXus supported reading and writing data files in HDF4, 
HDF5 and
XML formats by use of the NeXus Application Programming Interface
(NeXus-API or NAPI).  NAPI is still available, but frozen except for bug 
fixes.
After consultation with the community the currently recommended use of
NeXus is solely in terms of the HDF5 file format, using standard HDF5 tools.
That is expected to remain the basis for NeXus software development and
file creation in the future."

p. 5, col. 1, l. 12, change "10" to "ten"
p. 5, col. 2, l. -1, change "july" to "July"

On 8/15/14 3:35 AM, Mark Könnecke wrote:
> Pete,
>
> we have crossed each other. I just have edited the additions made by Joachim and others a little. Most
> of my changes just improve wording a little.
>
> But I removed the debatable from our decision on NXmonitors. I find the use of the word debatable
> in a publication debatable.
>
> I also removed the section on field ranks. If we adopt the interfaces proposal on the next NIAC,
> we will be far more specific about ranks even in base classes. So, I opt for rather saying nothing
> rather then something which may already be wrong by the time of publication.
>
> Regards,
>
>     Mark
>
>    
>
>
>
>
>
> Am 15.08.2014 um 06:51 schrieb Pete R. Jemian<prjemian at gmail.com>:
>
>    
>> Just pushed changes to the draft to:
>> * convert the tables to PNG figures
>> * add design principles into the Design Principles section
>>   (We had words in that section but nothing that described the design principles as stated in the User Guide)
>>
>> Look at the attached PDF
>>
>> Pete
>> <nexus14aip.pdf>_______________________________________________
>> NeXus-committee mailing list
>> NeXus-committee at nexusformat.org
>> http://lists.nexusformat.org/mailman/listinfo/nexus-committee
>>      
>    
>
>
> _______________________________________________
> NeXus-tech mailing list
> NeXus-tech at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus-tech
>