This issues is to catch any changes that have not been propagated to the JDF 1.7 version of the schema. i.e. It requests a manual trawl throught the latest version of the specification to ensure that the schema is fully up to date.
This will involve modifications missed from earlier versions, certainly there are 1.6 changes missed.
Rainer Prosi Once done should there be an attempt to merge/cherry pick changes back into the JDF 1.6 branch of the schema?