<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div>Partly to get myself up to speed on the interface issue, I transcribed one of the documents that Mark sent out by email last year onto the NeXus wiki, adding it to an existing discussion page (<a href="http://wiki.nexusformat.org/Objects_or_Interfaces">http://wiki.nexusformat.org/Objects_or_Interfaces</a>).
I also added a comment to the discussion tab. I look forward to the discussion in December.</div>
<div><br>
</div>
<div>Ray</div>
<br>
<div>
<div>On Aug 20, 2014, at 8:44 AM, Mark Könnecke <<a href="mailto:mark.koennecke@psi.ch">mark.koennecke@psi.ch</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
Hi,<br>
<br>
<br>
Am 20.08.2014 um 09:40 schrieb j.wuttke <<a href="mailto:j.wuttke@fz-juelich.de">j.wuttke@fz-juelich.de</a>>:<br>
<br>
<blockquote type="cite">Mark:<br>
<br>
After you fixed "some wordings" in v9 of our manuscript,<br>
an entire paragraph of my invention has become invisible:<br>
<br>
</blockquote>
<br>
On purpose. I sent a message about this but it may have been lost.<span class="Apple-converted-space"> </span><br>
The point is that if we adopt NeXus Interfaces at the next NIAC, then<span class="Apple-converted-space"> </span><br>
we will be far more specific about rank even in base classes. NeXus<span class="Apple-converted-space"> </span><br>
Interfaces have met with little resistance up to now. Which either means<span class="Apple-converted-space"> </span><br>
no one read my proposal or people agree…..<br>
<br>
My point is that I would rather write nothing about rank then something which<span class="Apple-converted-space"> </span><br>
is already wrong at the time of publication.<br>
<br>
May be this is a point to discuss at the next Telco….<br>
<br>
Regards,<br>
<br>
Mark<br>
<br>
<blockquote type="cite">NeXus does not specify the *rank* of a data field.<br>
For many, but not all fields it is possible to infer from<br>
the field name or from an explicit annotation whether<br>
the field is a scalar or what its array dimensionality is.<br>
The character data type NXchar is almost always to be<br>
understood as string type.<br>
<br>
This needs discussion, the more so since my related posting<br>
<a href="http://lists.nexusformat.org/pipermail/nexus-committee/2014/000534.html">http://lists.nexusformat.org/pipermail/nexus-committee/2014/000534.html</a><br>
has not yet been answered, private messages notwithstanding.<br>
<br>
I will not insist on having the above paragraph or a<br>
corrected version thereof in the paper. But I need to<br>
know where we stand. Is my paragraph technically correct?<br>
<br>
Best - Joachim<br>
_______________________________________________<br>
NeXus-committee mailing list<br>
NeXus-committee@nexusformat.org<br>
http://lists.nexusformat.org/mailman/listinfo/nexus-committee<br>
</blockquote>
<br>
<br>
_______________________________________________<br>
NeXus-committee mailing list<br>
<a href="mailto:NeXus-committee@nexusformat.org">NeXus-committee@nexusformat.org</a><br>
<a href="http://lists.nexusformat.org/mailman/listinfo/nexus-committee">http://lists.nexusformat.org/mailman/listinfo/nexus-committee</a></div>
</blockquote>
</div>
<br>
<div>-- <br>
Ray Osborn, Senior Scientist<br>
Materials Science Division<br>
Argonne National Laboratory<br>
Argonne, IL 60439, USA<br>
Phone: +1 (630) 252-9011<br>
Email: <a href="mailto:ROsborn@anl.gov">ROsborn@anl.gov</a><br>
<br>
</div>
<br>
</body>
</html>