It is expected that certain attributes have fixed values, ie.
It is expected that certain attributes have fixed values, ie. booleans or based on schema enums etc, this function allows such optimisations.
The qname will have been obtained via a call to either noNamespaceQName, unprefixedQName or prefixedQName, so any optimisations provided by them can be leveraged.
Start a new "tree", pushing the elem to TreeProxies
For files without large (and varied) attribute counts per repeated element it may represent significant space savings to optimise against the entire Elem itself.
For files without large (and varied) attribute counts per repeated element it may represent significant space savings to optimise against the entire Elem itself.
The Elements QName is garaunteed to be the last QName evaluated via the QName functions (i.e. Attributes are done first then the Elems QName)
By default calls TreeProxies.
By default calls TreeProxies.elementEnd. Replacing entire subtrees can be performed here.
Certain paths may be repeated (based on QNames of parents etc) and known to be by the developer, its also possible that the developer simply is not interested in this path.
Developers may also customise the creation of paths, for example adding starting children, replacing the XmlChildren implementation or replacing entire subtrees.