David A. Arroyo

So if I understand, this creates an `xmlns:` attribute, then hard-codes `QNAME` into the name of each xml element in the struct. It's a clever way to work around the...

Just so I understand, would this be an acceptable marshalling? blah blah blah

The above marshalling should be doable by adding an XMLName attribute to any structs, and removing any duplicate namespaces from the field, e.g. type BaseFilterType struct { XMLName xml.Name `xml:"http://www.fdsn.org/xml/station/1...

This also raises an issue I had not considered -- case mismatch in root-level element names. If the type name in the schema was `baseFilterType`, this package would produce invalid...

Thank you for opening this. Are you sure this resolves #86 ? #86 happens during parsing within the `xsd` package, but your change is to the `xsdgen` package. I have...

Thanks for the report. It's possible that a loop was created in the tree during parsing by one of the passes in the xsd package. If you are able to...

Thanks, I have it and reproduced your issue. I am still in the process of debugging. The problem appears to be in the `xsd.flattenRef` transformation. It is creating a loop...

I think I see the issue. There is an element in `mod_base.xsd` refers to itself: ... XML schema *does* allow recursive types[1], I've just never accounted for them. For `xsdgen`,...

I'm not sure I understand. The `xsd` package does support the `extension` element. Types defined as extensions of simpleContent or complexContent are understood by this package, and `xsdgen` can generate...

You've probably thought about this more than I have. Can we do something like this for default values? func (x *MyType) UnmarshalXML(d *xml.Decoder, start xml.StartElement) error { // avoid recursing...