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

 The {{{xs:redefine}}} element will be able to make this rule change
 happen.  In the ''fieldType'' and ''groupType'' sections, the lists of
 attributes should be defined in a separate {{{xs:attributeGroup}}}
 element.  Actually two elements each: common and category-specific
 attribute groups.  Then, create a simple ''applications/nxdl.xsd file''
 that calls {{{<xs:redefine schemaLocation="../nxdl.xsd">}}} and has the
 redefined rules for the minOccurs attribute.  Also, need to adjust the
 ''xsi:schemaLocation'' attribute of the ''definitions'' element in each
 applications/*.nxdl.xml file to refer to the local ''nxdl.xsd'' file that
 defines the change of rules.

 **NOTE: This will probably break the current validation code.**  Thus, the
 changes should be first implemented in a branch.

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