xmlschema-formal: targetNamespace problems

Here are a few problems related to targetNamespace:

1) The example schema contains a "targetns" attribute, whereas XML Schema
specifies this attribute as "targetNamespace".

2) There is no provision for schema components that specify a
targetNamespace URI which (already) includes a fragment identifier.

3) In 2.2.2, there are no examples of "regular expression notation for
component content" where the content model includes schema components from
different targetNamespaces.

-Ray