Issues 2.12 and 2.31

[David Hull <dmh@tibco.com>]

The editors have reviewed the tape and ...

These issues concern the handling of qnames, that is "prefix:localname" 
constructions in string content.  In particular, 2.12 recommends that 
xmlns attributes for prefixes used in string content be placed close to 
the string content itself, noting that various tools may change this 
placement.  2.31 warns that various tools may also reassign prefix 
mappings, breaking content altogether.

This are listed as BaseN issues, but BaseN does not define any such 
content.  BaseN does define a TopicExpression element, and if the 
dialect for that element is WS-Topics, then there may be QName issues, 
but this is clearly a Topics issue, not a BaseN issue.

We recommend that these issues be moved to WS-Topics, and generally 
recommend that qname issues be mentioned in (and only in) any 
specifications that allow for qnames in string content.