[NeXus-tech] suggestion for all NXDL files

[freddie.akeroyd at stfc.ac.uk]

Pete,

We currently have an svn revision attribute attached to a definition and
also an overall version number as part of "xmlns". What was the thinking
on the format and usage of this version number - is it e.g purely
descriptive or would it be used in validation (and hence need to tie up
with xmlns in some way)? Currently we would release and version all
definitions together - this gets round the problem of "version x of
something requiring version y of something else", but it a little
restrictive for minor changes to definitions. Maybe we need to look at a
more general definition dependencies system e.g. specifying the version
of a definition you extend/inherit from.

Freddie

-----Original Message-----
From: nexus-tech-bounces at nexusformat.org
[mailto:nexus-tech-bounces at nexusformat.org] On Behalf Of Pete R. Jemian
Sent: 13 January 2010 08:34
To: NeXus Technical sub-committee list
Subject: [NeXus-tech] suggestion for all NXDL files


one suggestion from the HDF5 workshop is to add a required attribute to
the
<definition> element for a "version" attribute that is a character
string.

I agree with this idea and am ready to commit it to the rules.
Discussion or objections?

Pete

-- 
----------------------------------------------------------
  Pete R. Jemian, Ph.D.                <jemian at anl.gov>
  Beam line Controls and Data Acquisition, Group Leader
  Advanced Photon Source,   Argonne National Laboratory
  Argonne, IL  60439                   630 - 252 - 3189
-----------------------------------------------------------
     Education is the one thing for which people
        are willing to pay yet not receive.
-----------------------------------------------------------
_______________________________________________
NeXus-tech mailing list
NeXus-tech at nexusformat.org
http://lists.nexusformat.org/mailman/listinfo/nexus-tech
-- 
Scanned by iCritical.