[NeXus-definitions-tickets] [NeXusDefinitions] #109: Soleil example data uses a NXtechnical_data class : add to base_classes

[NeXus Base Classes and Instrument Definitions]

#109: Soleil example data uses a NXtechnical_data class : add to base_classes
-------------------------+--------------------------
 Reporter:  Pete Jemian  |       Owner:  Pete Jemian
     Type:  enhancement  |      Status:  assigned
 Priority:  major        |   Milestone:  later
Component:  general      |  Resolution:
 Keywords:               |
-------------------------+--------------------------

Comment (by Tobias Richter):

 === formal procedure ===

 The proper sequence of events for application definitions is:
  1. Send you application definition to the NIAC for review
  1. Correct your definition for the comments of the NIAC
  1. Cure and use the definition for a year
  1. After a final review, it becomes the standard
 So there is no automatic acceptance and I do not see why the procedure
 should be different for base classes.

 All that has happened in this case is //use the definition for a year//.

 === my view on these two classes ===
 No idea what a `NXsai_controller` is. And second guessing that from an
 example file without a proposal is not how we should progress NeXus.

 `NXtechnical_data` adds is another group holding the dataset `data`
 instead of having `data` (or whatever the name of `NXtechnical_data` is)
 in the expected place. So it is incompatible with what we generally use in
 NeXus. If this gets ratified we officially give up standardising on
 anything.

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