Hello David, The main reason for this change was because the users wanted to add elements from no namespace in the Schematron file. This is because of the quick fixes support, if you want to create quick fixes for an XML document that doesn't have a namespace. The common mistake that they made was to add the elements without a prefix in the Schematron file, and because the default namespace was mapped to the Schematron namespace they ended up to add the elements in the Schematron namespace. Best Regards, Octavian -- Octavian Nadolu <oXygen/> XML Editor http://www.oxygenxml.com On 06.08.2015 17:48, David Birnbaum wrote:
Dear <oXygen/> users,
The template loaded when I create a new Schematron seems to have changed in version 17 not only with the addition of Schematron Quick Fix capabilities, but also by replacing the default namespace declaration:
xmlns="http://purl.oclc.org/dsdl/schematron"
with a namespace prefix definition:
xmlns:sch="http://purl.oclc.org/dsdl/schematron"
so that the Schematron document is now, by default, in no namespace. This isn't a problem (I can live with it or change it, as I prefer), but it makes me wonder why the default behavior was changed. Are there advantages to defaulting to no namespace, instead of to the Schematron namespace?
Thanks,
David
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user