PUBLIC MARKS with tags libxml & sax

HTML5, however, exposes the varying state of the tree throughout; an application may examine a new element's parent pointer at one point, find one value, and then examine it after new events have been processed and find a different value. The very nature of SAX events prohibits that degree of flexibility.

Implémenter le modèle de parsing de HTML5 dans libxml est-il possible sans bouleverser la structure interne de libxml ?