With DOMDocument 4 there seem to be just a few referential integrity issues, like and attribute being confused for a childnode and descendancy. I have been able to work around most.

When my parsing PRG gets to this node:

<imsss:minNormalizedMeasure>0.6</imsss:minNormalizedMeasure>

I am guessing the 0.6 should be oNode.text. However I am not adressing it as the node's text - but I can. Anyway, after the "imsss:minNormalizedMeasure" is added a node to my parser's treeview the parser goes and loops through any attributes:

PROCEDURE ADD_Attributes_PRTV(oTV,oNode,lcParentKey)
FOR ii = 0 TO oNode.attributes.length-1
oTV.Nodes.Add(lcParentKey,4,lcParentKey+[A]+TRANSFORM(ii),"someAttribtext")
ENDFOR &&ii = 0 TO oMD.childNodes.length-1

In the case of the imsss node, VFP errors out and reports:
Member's attribute does not evaluate to an object (#1943)
Then a childnode in the treeview is added and reports the "nodename" as "#text"!

Should my parser adress the 0.6 as the nodes text?

Any workaround suggestions?:)