The base module
Aucent.MAX.AXE.XBRLParser has a serious bug; XBRL instances that have
different bindings for namespaces in different elements. For example,
<context xmlns="http://www.xbrl.org/2003/instance" ... />
<Assets
xmlns="http://xbrl.us/us-gaap/2008-03-31" ... />
will blow out every time with this error:
Index was outside the bounds of the array. at
Aucent.MAX.AXE.XBRLParser.MarkupProperty.TryCreateFromXml(Int32 index,
XmlNodeList nodes, ArrayList contexts, ArrayList units, MarkupProperty& mp,
ArrayList& errors)
at Aucent.MAX.AXE.XBRLParser.Instance.ValidateAndParse(ArrayList&
errors)
at Aucent.MAX.AXE.XBRLParser.Instance.TryLoadInstanceDoc(String
filename, ArrayList& errors)
Since that module is also used in the SEC viewer and in Dragon View, the
consequences are going to be severe for anyone who's created an instance
programmatically - they have to do a final pass on the instance to enforce
a restricted syntax for namespace prefix bindings. (!)
Thank you for submitting this defect. I have forwarded it to our QA Department for review.