-
Notifications
You must be signed in to change notification settings - Fork 56
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
"definition" element enumeration #910
Comments
Additionally, we could allow any case presentation or the NXDL class name to pass validation. Those names that do not match exactly should be flagged as a warning but not marked as invalid. The NIAC must ensure we do not allow multiple different NXDL classes that have the same name, differing only in case. |
We should fix this situation in NXspe (in #911) by removing line 39: definitions/applications/NXspe.nxdl.xml Line 39 in a232ead
Make a new issue, PR, contact the community, and get approval from the NIAC. |
The manual must make clear how to properly construct an NXDL file that connects this same name with the And, any content referenced by the NXDL (such as images) be placed in a subdirectory with the name chosen by stripping off the file: In the NXDL file: <definition name="NXthing" ... />
<!-- later -->
<field name="definition">
<doc>Official NeXus NXDL schema to which this file conforms.</doc>
<enumeration>
<item value="NXthing"/>
</enumeration>
</field> |
In https://github.com/nexusformat/definitions/blob/main/applications/NXspe.nxdl.xml, the
definition
field enumerates more than one valid representation of this application definition.The XML Schema should control how many enumeration item field are allowed for the
definition
element. In our case, only one value is allowed, not zero (for an application definition), not more than one. The validation process can then properly deliver a message when a data file does not present this structure.The text was updated successfully, but these errors were encountered: