<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi,<br>
<br>
If you are not talking about application definitions, please
ignore this mail.<br>
<br>
In the case of application definitions, I would not expect them to
match with the API version. A program may support several versions
of an application definition but it may be able to write one of
version them. In addition, it may not use the NeXus API at all.<br>
<br>
Best regards,<br>
<br>
Armando<br>
<br>
On 23/01/2015 11:00, Wintersberger, Eugen wrote:<br>
</div>
<blockquote
cite="mid:35E004AD6290A7438FCA34BBF325F41606996B04@ADXV2.win.desy.de"
type="cite">
<pre wrap="">Hi folks
I just had a look in the manual. According to the reference manual the
NeXus_version attribute, attached to the root node of the file, should
be the API version used when writing the file (that's why I set it to
4.3 in my own code).
This is most probably not the best choice for this attribute. It should
rather refer to the current version of the Nexus definitions. I am not
sure yet if the API and definitions version was coupled until now.
Since we see many people using their own code to write Nexus files it is
most probably more important to know which definition they follow rather
than which API version they have used.
@Pete: how are definition versions encoded in the XML (sorry for my
limited knowledge of XML - am working on this)?
regards
Eugen
On Fri, 2015-01-23 at 09:56 +0100, Jan Kotanski wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Tobias,
Thanks for your email.
Usually, when someone creates an NXroot group he/she adds its
NeXus_version attribute. Should it be 3.1.0 or something else.
E.g. using Eugen's pni-libraries I get automatically
NeXus_version = 4.3.0
Is this version number is somewhere encoded in the “definitions” repository?
NeXus_version could be helpful for NeXus readers.
Bests,
Jan
On 01/23/2015 09:34 AM, Tobias Richter wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Jan,
I agree that the release situation requires some improvements. At least could do with a roadmap or so.
Just to confirm: We are talking about the “definitions” repository, were we hold the manual and XML schema that define the standard (as opposed to the “code” that holds the API). Right?
To my knowledge there hasn’t been another formal release of that since 3.1.0. And there hasn’t been one before. Maybe some day someone will explain to me why that was released as 3.1.0. I do not know.
Since then we’ve been on a rolling release, if you like. Until very recently all changes since the release, tried to be backward compatible. In December we’ve deprecated NXgeometry. So it was difficult to make the call on how many small changes or additions here or there warrant a new release. I tend to just consult the manual for the latest version and for me that works well. Opinions from the community was the expectations would be are welcome.
Does that help?
Tobias
</pre>
<blockquote type="cite">
<pre wrap="">On 23 Jan 2015, at 09:01, Jan Kotanski <a class="moz-txt-link-rfc2396E" href="mailto:jan.kotanski@desy.de"><jan.kotanski@desy.de></a> wrote:
Hi,
I've just been searching for the current NeXus version number in the
nexusformat repo and I could find only a tag denoted by v3.1.0.
But I suppose this is not the last version. Where can I find it and why
I cannot find it on <a class="moz-txt-link-abbreviated" href="http://www.nexusformat.org">www.nexusformat.org</a>? (It should be easily visible).
In my opinion it would be good to have in the repo tags/branches
corresponding to version numbers.
Bests,
Jan
_______________________________________________
NeXus mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NeXus@nexusformat.org">NeXus@nexusformat.org</a>
<a class="moz-txt-link-freetext" href="http://lists.nexusformat.org/mailman/listinfo/nexus">http://lists.nexusformat.org/mailman/listinfo/nexus</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
NeXus mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NeXus@nexusformat.org">NeXus@nexusformat.org</a>
<a class="moz-txt-link-freetext" href="http://lists.nexusformat.org/mailman/listinfo/nexus">http://lists.nexusformat.org/mailman/listinfo/nexus</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
NeXus mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NeXus@nexusformat.org">NeXus@nexusformat.org</a>
<a class="moz-txt-link-freetext" href="http://lists.nexusformat.org/mailman/listinfo/nexus">http://lists.nexusformat.org/mailman/listinfo/nexus</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
NeXus mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NeXus@nexusformat.org">NeXus@nexusformat.org</a>
<a class="moz-txt-link-freetext" href="http://lists.nexusformat.org/mailman/listinfo/nexus">http://lists.nexusformat.org/mailman/listinfo/nexus</a>
</pre>
</blockquote>
<br>
</body>
</html>