<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
An unfortunate coincidence, particularly since we have no trademark.
It's a bit<br>
late in the game to switch names, as both collaborations are older than
ten years<br>
and have some name recognition. Does the UnUsuaL capitalization help us
stand out?<br>
<br>
In any case, when I use Google to search for "nexus data format" I<br>
do get both nexuses (nexii ?) but each format has a different context.<br>
Ours is associated with neutron,x-ray, and muon data, and the other<br>
is associated with systematic biology. I think it's reasonable to assume<br>
that the end-user searching will be subject to some confusion, but <br>
should still select the correct format according to its context.<br>
<br>
Perhaps littering our links with neutron/x-ray/muon will help out<br>
the search engines to better steer our users to the right place...<br>
<br>
Nick<br>
<br>
Rudi Cilibrasi, Ph.D. wrote:
<blockquote
cite="midbd3cb4550705270853o1c2ccab7pc66b8c94cf501365@mail.gmail.com"
type="cite">Agreed, it seems an excellent release. However, I would
also
<br>
ask if the name itself for the library is "set in stone"?
Unfortunately,
<br>
there is another scientific data format called the "Nexus" file format
<br>
and it is used in bioinformatics. You can read about it here:
<br>
<br>
<a class="moz-txt-link-freetext" href="http://awcmee.massey.ac.nz/spectronet/nexus.html">http://awcmee.massey.ac.nz/spectronet/nexus.html</a>
<br>
<br>
The confusing part is that the other Nexus file format has an
<br>
extendable block format. It can very well be misunderstood to contain
<br>
an X-Ray or other radiation type data block. It already contains many
<br>
other data block types and so this will probably continue to be a
source
<br>
of confusion for all newcomers to either file format potentially, since
<br>
most people type nexus into the search box anyway both results come
<br>
up intermingled and thus suggesing that the two libraries are the same
<br>
format when in fact they are totally unrelated.
<br>
<br>
The bioinformatics Nexus format has been around about 10 years now I
think.
<br>
I just
<br>
checked the NeXus mailing lists and noticed that that use of the term
has
<br>
also
<br>
been around for about 10 years, so I'm not sure which use came first
So
<br>
probably eventually
<br>
one of the two file formats will need to change names I think;
otherwise
<br>
there will be no end of confusion due to the similarity between
<br>
Nexus
<br>
and
<br>
NeXus
<br>
and the confusing similarity of scientific file format domains.
<br>
<br>
I look forward to any ideas for resolution of this problem. Best
regards,
<br>
<br>
Rudi
<br>
<br>
On 5/26/07, Ray Osborn <a class="moz-txt-link-rfc2396E" href="mailto:ROsborn@anl.gov"><ROsborn@anl.gov></a> wrote:
<br>
<blockquote type="cite"><br>
On 2007/05/25 8:27, "Nick Maliszewskyj" <a class="moz-txt-link-rfc2396E" href="mailto:nickm@nist.gov"><nickm@nist.gov></a> wrote:
<br>
<br>
> The NeXus technical committee is pleased to announce the official
<br>
> release of version 4.0 of the NeXus API. The NeXus API provides a
<br>
> unified interface for writing hierarchical data files in HDF4,
HDF5,
<br>
> and XML formats. Version 4.0 resolves a number of bugs reported in
the
<br>
> 3.0 release by providing updated makefiles, support for the
gfortran
<br>
> compiler, and an improved test suite.
<br>
<br>
Congratulations for all the work done in getting this release out - I
<br>
think
<br>
it's been a very well conducted process. Could I put in a plea though
<br>
that
<br>
someone updates the documentation on the API wiki page to include the
new
<br>
routines?
<br>
<br>
Obviously not until after the Memorial Day (or Whitsun or Pfingsten...)
<br>
holiday.
<br>
<br>
Have a great weekend,
<br>
Ray
<br>
--
<br>
Dr Ray Osborn Tel: +1 (630) 252-9011
<br>
Materials Science Division Fax: +1 (630) 252-7777
<br>
Argonne National Laboratory E-mail: <a class="moz-txt-link-abbreviated" href="mailto:ROsborn@anl.gov">ROsborn@anl.gov</a>
<br>
Argonne, IL 60439-4845
<br>
<br>
<br>
<br>
_______________________________________________
<br>
NeXus-developers mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:NeXus-developers@nexusformat.org">NeXus-developers@nexusformat.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.nexusformat.org/mailman/listinfo/nexus-developers">http://lists.nexusformat.org/mailman/listinfo/nexus-developers</a>
<br>
<br>
</blockquote>
<br>
<br>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
NeXus-developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NeXus-developers@nexusformat.org">NeXus-developers@nexusformat.org</a>
<a class="moz-txt-link-freetext" href="http://lists.nexusformat.org/mailman/listinfo/nexus-developers">http://lists.nexusformat.org/mailman/listinfo/nexus-developers</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
o Dr. Nicholas C. Maliszewskyj
o Center for Neutron Research
o National Institute of Standards & Technology
o 100 Bureau Drive, Stop 8562
o Gaithersburg MD 20899-8562
o <a class="moz-txt-link-abbreviated" href="mailto:nickm@nist.gov">nickm@nist.gov</a> Phone: (301)975-3171 Fax: (301)921-9847
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
</pre>
</body>
</html>