-
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
NXsas: review use of minOccurs on various components #522
Comments
important to make next milestone |
Do this with a branch+PR |
NXsas has no instances of max* or minOccurs. What is there to review? Is this a proposal to change the application definition? |
The application definition should be examined to determine which components must be given or that some components need a declaration of |
@benajamin : Yes, and Yes. @zjttoefs You asked above:
We should review the definition with this question:
If they are missing (it is likely the existing application did not consider these attributes) and the need for them sufficient, we should propose changes to NXsas in a branch. |
This is the structure of the NXsas definition at this time. None of the items are marked optional or minOccurs=0:
|
For base classes, minOccurs=0 is the default and means the dataset is optional. For application definitions, the default is minOccurs=1 which means it is required. (HDF5 imposes maxOccurs=1 since item names must be unique within a group).
add: NXsas documentation
The text was updated successfully, but these errors were encountered: