[NeXus-tech] application definitions and NXsubentry or NXentry

[Pete Jemian]

our rule:
application definitions will be used to replace NXsubentry (preferred) 
or NXentry


Trac Ticket #179 is to clarify NXsubentry and use of application 
definitions in the manual.  Here's the general pattern for use:


      name:NXsubentry (or NXentry but NXsubentry is preferred)
        @NX_class = NXsubentry  (as above)
        definition = {NXapplicationdefinition}
          @version = {this is optional}
          @URL= {this is optional}
        {fields, groups, attributes of NXapplicationdefinition}


These two points make sense:
[1] Application definitions should only be used by NXsubentry
     Is there any meaningful use at NXentry instead?
     NXsubentry might be better understood as NXappdef (or similar)
     (we debated this at some length at NIAC2010 and voted)

[2] application definitions should extend "NXsubentry"
     (or some other class hierarchy that extends from NXsubentry)
     rather than "NXobject"
     This is done by editing the definition/@extends attribute
     in the NXDL file of the application definition.

Discussion?


_______________________________________________
NeXus-definitions-tickets mailing list
NeXus-definitions-tickets at nexusformat.org
http://lists.nexusformat.org/mailman/listinfo/nexus-definitions-tickets