[NeXus-definitions-tickets] [NeXusDefinitions] #65: Points to consider for NXDL

[NeXus Base Classes and Instrument Definitions]

#65: Points to consider for NXDL
------------------------+---------------------------------------------------
Reporter:  Pete Jemian  |        Owner:     
    Type:  defect       |       Status:  new
Priority:  major        |   Resolution:     
Keywords:               |  
------------------------+---------------------------------------------------
Comment (by Freddie Akeroyd):

 With regard to (2) isn't this already covered by the "definition" field in
 the NXentry?

 I think there may be an option to use "xsi:type" at the NXentry level to
 asist with schema validation of the NXDL translated files ... i've been
 updating the "definition" option of nxconvert to add such an attribute so
 we would have e.g.
 <pre>
 <NXentry name="SCAN_0001" xsi:type="NXmonopd">
   <definition url="...">NXmonopd</definition>
 </NXentry>
 </pre>
 to validate against a schema. If NXmonopd is inherited from NXentry, then
 xsi:type will tell the schema validation process to use "NXmonopd" rather
 than "NXentry" when it is run.

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