> 
> Is the following a complete list of the new functionality in 
> XML Schema 1.1?

Some additions, from comparing with a list I did a few months ago.
> 
> 1. Assertions - the <assert> element and 
> xPathDefaultNamespace attribute
> 
> 2. Conditional type alternatives - the <alternative> element
> 
> 3. Inheritable attributes
> 
> 4. Changes to the <all> element - its content elements are 
> not limited to no more than one occurrence

4a "all" model groups can now contain wildcard particles
4b derivation by extension on "all" model groups.
> 
> 5. Non-deterministic content models are now permitted

I think that statement is too broad. The rules have only been relaxed in
quite minor ways.
> 
> 6. Additions to <any> and <anyAttribute> elements - 
> @notNamespace, @notQName

6a not #defined, not #definedSibling
> 
> 7. Open content - the <openContent> and <defaultOpenContent> elements

7a the default attributeSet
> 
> 8. Changes of the ID datatype - an element can have multiple 
> ID attributes; the ID type can have a fixed or default value
> 
> 9. A schema can define multiple targetNamespaces

Slightly misstated. A schema has always been able to define multiple
namespaces. The change is that in some circumstances a schema DOCUMENT can
now define components in more than one target namespace. 
> 
> 10. The override element (redefine is deprecated)
> 
> 11. The value of substitutionGroup can be a list
> 
> 12. Vendor-unique extensions are permitted
> 
> 13. Version control - @minVersion, @maxVersion, 
> @typeAvailable, @typeUnavailable, @facetAvailable, @facetUnavailable
> 
> 14. New datatypes:
> 
>      - error
>      - precisionDecimal
>      - datetimeStamp
>      - anyAtomicType
> 
> 15. New facets:
> 
>      - assert (plus the $value variable)
>      - minScale
>      - maxScale

15a explicitTimezone
> 
> Anything else?
> 

16. Changes to union types: bug-fixing really, but a substantial change to
the model that makes restrictions of a union type work properly, when they
never worked properly before.

17. A complete change of approach to the rules for
derivation-by-restriction, replacing the whole set of rules for how a
restricted type compares syntactically to its base type, with a simple rule
that says if the extent is a subset, then it's a valid restriction.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay