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

 Hi Pete,

 the xs:attributeGroup is a neat way to solve the problem - well done!

 at the moment the scheme has a different "nxdl.xsd" file in the separate
 directories, I'm wondering if this might cause potential confusion with
 them all having the same file name. Maybe having "nxdl_base.xsd",
 "nxdl_application.nxdl" etc. referencing a common nxdl.xsd would make
 things clearer?

 I've also though of another possible way that might avoid separate xsd
 files, but does require more changes to the definitions themselves. At the
 moment they all use <definition> for their content, but if this changed to
 <base_definition>,  <application_definition> etc. then a single nxdl.xsd
 might be able to validate each group differently?

 Regards,

 Freddie

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