[NeXus-tech] XML and new attribute

Tobias Richter Tobias.Richter at esss.se
Thu Feb 12 16:15:37 GMT 2015


Hi,

We do want data to be stored as arrays, rather than comma (or whatever) separated strings that we had in the past.
As we can only deal with attribute arrays in NAPI since some time last summer I would be surprised if NXDL could handle that. That’s one of the motivations to move to a different validation scheme.

On the meta level: According to my memory at the NIAC we’d decided not to use this list for technical discussions, but have them in the main list. That isn’t overflowing with messages and providing small life signs like this would help people engage. 
The idea for the moment was to only announce Telcos in nexus-tech to avoid spamming everyone’s calendar with entires.

Do people disagree or do be just need to break old habits?

Regards,

Tobias


> On 12 Feb 2015, at 16:56, Eugen Wintersberger <eugen.wintersberger at desy.de> wrote:
> 
> Hi folks 
>  I have an interesting question about attributes and NXDL. As we
> defined a whole bunch of new attributes during the last NAIC meeting I
> was wondering how they will be represented in NXDL. Will they go in the
> tag, for instance like 
> 
> <field name="phi" type="NX_FLOAT" depends_on="chi"
> transformation_type="rotation" vector="0,1,0" offset="0,0,0">
> 
> </field>
> 
> or will we store them using the attribute tag 
> 
> <field name="phi" type="NX_FLOAT">
> 	<attribute name="depends_on" type="NX_CHAR">chi</attribute>
> 	<attribute name="transformation_type" type="NX_CHAR">rotation</attribute>
> 	<attribute name="vector" type="NX_FLOAT"> 0 1 0 </attribute>
> 	<attribute name="offset" type="NX_FLOAT"> 0 0 0 </attribute>
> </field>
> 
> In the latter case we should also ask if we would have to use a
> "dimensions" tag to denote that this is a vector instead of a scalar. 
> The reason why I am asking is that I am currently adopting my XML to
> Nexus/Nexus to XML toolchain and just now stumbled upon this problem. 
> 
> Myabe (as usual) I missed something in the documentation. Any advice?
> 
> best regards
>  Eugen
> 
> _______________________________________________
> NeXus-tech mailing list
> NeXus-tech at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus-tech




More information about the NeXus-tech mailing list