Martin, this one has puzzled me for a while - so many thanks to you for sharing this example. I was able to import it after some kludging/gorilla coding - attached working CAM template below.
Both XMLSpy and Oxygen opened the schema - but it seems there is a flaw in it - the XML root says that elementFormDefault="qualified" - but there is no default namespace. I changed that to elementFormDefault="unqualified".
Now the CAMEditor is using Saxon under the hood - and an earlier version - it appears to not fully understand this namespace default tap dance. I have the XSLT set to using asm1 when it has no clue, but this broke cam-utils.xsl, so I had to kludge that to get it to work and insert a URI for asm1. Then I manually edited and stripped out the asm1: from the template post-import. This is all messy. I need to fix this for a new release; at least I now have a sample, and some gorilla coding that got over it for now. That gorilla coding will need to work with our regression testing on other schema before I'm comfortable releasing that.
Plus I need to understand why XMLSpy and Oxygen are fluoting a W3C attribute; but that's not new; do as we do, not as we say.
If you have more of these to import - let me know - and I can share the kludged cam-utils.xsl to use.
While doing Create New CAM Template from XSD I get an Invalid Thread Access error. I'll add the XSD as an attachment.
Any help would be appreciated :) I've been using XML Spy for awhile and am looking forward to a viable open source alternative.
Last edit: Martin Robb 2016-09-26
Martin, this one has puzzled me for a while - so many thanks to you for sharing this example. I was able to import it after some kludging/gorilla coding - attached working CAM template below.
Both XMLSpy and Oxygen opened the schema - but it seems there is a flaw in it - the XML root says that elementFormDefault="qualified" - but there is no default namespace. I changed that to elementFormDefault="unqualified".
Now the CAMEditor is using Saxon under the hood - and an earlier version - it appears to not fully understand this namespace default tap dance. I have the XSLT set to using asm1 when it has no clue, but this broke cam-utils.xsl, so I had to kludge that to get it to work and insert a URI for asm1. Then I manually edited and stripped out the asm1: from the template post-import. This is all messy. I need to fix this for a new release; at least I now have a sample, and some gorilla coding that got over it for now. That gorilla coding will need to work with our regression testing on other schema before I'm comfortable releasing that.
Plus I need to understand why XMLSpy and Oxygen are fluoting a W3C attribute; but that's not new; do as we do, not as we say.
If you have more of these to import - let me know - and I can share the kludged cam-utils.xsl to use.
Attached schema generated out from CAM template. Compare and contrast.