2.1.2.103 [ISO/IEC9075-14:2011] X211, XML 1.1 support

V0138:

The specification states the following:

 Subclause 6.14, "<XML element>":
  
 Without Feature X211, "XML 1.1 support", in conforming SQL language, an <XML element name> shall be an XML 1.0 QName.
  
 Without Feature X211, "XML 1.1 support", in conforming SQL language, an <XML attribute name> shall be an XML 1.0 QName.
  
 Subclause 6.15, "<XML forest>": 
  
 Without Feature X211, "XML 1.1 support", in conforming SQL language, a <forest element name> shall be an XML 1.0 QName.
  
 Subclause 6.17, "<XML PI>": 
  
 Without Feature X211, "XML 1.1 support", in conforming SQL language, an <identifier> contained in an <XML PI target>, when mapped to Unicode, shall be an XML 1.0 NCName.
  
 Note -- The set of XML 1.0 NCNames is a proper subset of the set of XML 1.1 NCNames. That is, all XML 1.0 NCNames are also XML 1.1 NCNames, but not all XML 1.1 NCNames are also XML 1.0 NCNames.
  
 Subclause 6.18, "<XML query>":
  
 Without Feature X211, "XML 1.1 support", in conforming SQL language, the value of the <XQuery expression> shall be an XQuery expression with XML 1.0 lexical rules.
  
 Without Feature X211, "XML 1.1 support", in conforming SQL language, the <identifier> contained in an <XML query variable> shall be an XML 1.0 NCName.
  
 Subclause 11.3, "<XML lexically scoped options>": 
  
 Without Feature X211, "XML 1.1 support", in conforming SQL language, each <XML namespace prefix> shall be an XML 1.0 NCName.

Microsoft SQL Server 2008 R2 and Microsoft SQL Server 2012 vary as follows:

Transact-SQL does not support this feature.

This variation pertains to XML 1.0 [XML10/5] functionality in SQL Server.