[NeXus-tech] NXvalidate progress

[Akeroyd, Freddie (STFC,RAL,ISIS)]

Hi,

 

I've been doing a bit of work on NXvalidate and can sort of validate an
HDF file against an NXroot type definition. To get further and do
NXmonopd correctly I think we need to do the following.

 

Unlike base classes that "extend" definitions (add new optional
entries), application definitions "restrict" existing definitions by
saying what is mandatory. We need to add a new keyword into the nxdl
syntax for this and, due to the way schema work, the xslt will need to
do quite a bit of extra work. The problem with "restrict" in schema is
that you need to list every element you inherit and then say what you
want to do with them. The writer of the definition will, of course, only
want to list the changed ones in nxdl so we will need to get the xslt
transform to copy across all inherited members that are not mentioned in
the nxdl. We can talk about this at the meeting

 

Freddie

 


-- 
Scanned by iCritical.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.nexusformat.org/mailman/private/nexus-tech/attachments/20090812/b0ef3284/attachment.html