Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow string array content #281

Closed
prjemian opened this issue Jun 18, 2014 · 3 comments
Closed

allow string array content #281

prjemian opened this issue Jun 18, 2014 · 3 comments
Milestone

Comments

@prjemian
Copy link
Contributor

need to allow string array content in addition to standard strings (an enhancement to NeXus)

in some instances, strings may be limited to rank=1 (which is, in effect, what exists now)
in some cases, we can be less restrictive, up to NX_RANK_MAX

@prjemian prjemian modified the milestone: NXDL 3.4 Jun 30, 2017
@prjemian
Copy link
Contributor Author

prjemian commented Jul 3, 2017

What work is required to close this ticket? Perhaps this added to the manual in the right place:

Clients should support string arrays. When shape is (1,) then that means there is only one string and the string array can be flattened to just string.

@zjttoefs
Copy link
Contributor

zjttoefs commented Jul 3, 2017

The @axes does make use of it, doesn't it? Then there should be no work required.

@prjemian
Copy link
Contributor Author

prjemian commented Jul 3, 2017

The datarules.rst file is one place to add the text under the strings definition.

http://download.nexusformat.org/doc/html/datarules.html#nexus-data-types

Also, to be like the other definitions nearby, start this definition with

NX_CHAR:

Could also expand the documentation of NX_CHAR in nxdlTypes.xsd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants