GeezerVison

It tells how many of the attributes reported to StartElementHandler were
given in the start tag rather than defaulted from the DTD.

* The factory methods now raise InvalidCharacterErr if the name is not a
  valid XML name.
* appendChild(), insertBefore() and replaceChild() now raise
  WrongDocumentErr if the new child was created by other document, and
  HierarchyRequestErr if it is the node itself or its ancestor.
* Attributes defaulted in the DTD are no longer omitted when parsing, and
  Attr.specified now reports whether the attribute was given in the start
  tag.
* EntityReference nodes and Document.createEntityReference() are now
  implemented.

A node without children cannot be an ancestor, so testing this first
keeps appending leaf nodes linear in the depth of the tree.

Also fix references which do not resolve on main.

The documented module is xml.parsers.expat, there is no target for
pyexpat.

…nd NEWS

Suggested by dgelessus in the review of pythonGH-155632, where the same
wording was used.

A document can have only one element child and only one document type
child.  This was only checked in Document.appendChild(), and only for
elements, so insertBefore() and replaceChild() could add a second one.

A document fragment no longer accepts notation children, which the DOM
does not allow.

…dom-level-1

It now reports whether the attribute was given in the start tag.

The DOM requires it if the attribute was created by another document.
Only insertion of child nodes was checked.

It is the same interface as Element.setAttributeNode(), so it now raises
WrongDocumentErr for an attribute created by another document and
InuseAttributeErr for an attribute which belongs to another element.

It is minidom specific, so document it in the minidom documentation.

The DOM requires InvalidCharacterErr for an invalid XML name,
WrongDocumentErr for a node created by another document, and
HierarchyRequestErr for making a node a descendant of itself.  None of
this was documented.

…dom-level-1

The DOM does not allow Element.removeAttribute() and
removeAttributeNS() to raise NotFoundErr in this case, it is a deviation
of minidom, documented in pythonGH-156636.