[NeXus-definitions-tickets] [NeXusDefinitions] #266: implement difference in rules between base classes and application definitions

[NeXus Base Classes and Instrument Definitions]

#266: implement difference in rules between base classes and application
definitions
-------------------------+--------------------------
 Reporter:  Pete Jemian  |       Owner:  Pete Jemian
     Type:  defect       |      Status:  new
 Priority:  major        |   Milestone:
Component:  general      |  Resolution:
 Keywords:  NXDL schema  |
-------------------------+--------------------------

Comment (by Pete Jemian):

 === about the nxdl.xsd files ===

 Continuing Freddie's last suggestion further, perhaps change the
 ''definitions'' element to ''base_class'' or ''application_definition''
 and eliminate the category-specific {{{nxdl.xsd}}} files?  Keep the NXDL
 files in their respective subdirectories.  NXDL files in the contributed
 definitions would be either of these two elements (since the contributed
 definitions are in incubation status before they move to one of the other
 two directories anyway).  This would return us to just one {{{nxdl.xsd}}}
 file.

 === about the version number ===

 Also, regarding the version number increment, these changes are more
 infrastructure rather than changes to the data files themselves.  The
 current standard was tagged as v3.1.0.  Suggest that we tag these changes,
 once complete, as v3.1.1 which will compel no major changes to the
 validation process and data files that depend on this version of the
 standard.

-- 
Ticket URL: <http://trac.nexusformat.org/definitions/ticket/266#comment:10>
NeXus Base Classes and Instrument Definitions <http://www.nexusformat.org/>
NeXus Base Classes and Instrument Definitions