[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):

 Turns out the {{{xs:redefine}}} element has unintended consequences when
 used this way.  Instead of redefining all *subsequent* uses, it redefines
 *all* uses which means that a redefinition in an application definition
 will change the rules for a base class contained within that appplication
 definition.  **Not what we want.**

 Instead, separate rules must be created for base classes and application
 definitions.  As already shown with the use of {{{xs:attributeGroup}}}
 elements, common components will be gathered together to the greatest
 extent possible.

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