Annotations provide for human- and machine-targeted annotations of schema components. In the test the human-targeted annotation is provided for a wildcard schema component (anyAttribute). Annotations provide for human- and machine-targeted annotations of schema components. In the test the human-targeted annotation is provided for a wildcard schema component (anyAttribute). The annotation is specified twice. Annotations provide for human- and machine-targeted annotations of schema components. In the test the machine-targeted annotation is provided for a wildcard schema component (anyAttribute). Annotations provide for human- and machine-targeted annotations of schema components. In the test the machine-targeted annotation is provided for a wildcard schema component (anyAttribute). The annotation is specified twice. Annotations provide for human- and machine-targeted annotations of schema components. In the test the human-targeted annotation is provided for a wildcard schema component (any). Annotations provide for human- and machine-targeted annotations of schema components. In the test the human-targeted annotation is provided for a wildcard schema component (any). The annotation is specified twice. Annotations provide for human- and machine-targeted annotations of schema components. In the test the machine-targeted annotation is provided for a wildcard schema component (any). Annotations provide for human- and machine-targeted annotations of schema components. In the test the machine-targeted annotation is provided for a wildcard schema component (any). The annotation is specified twice. {namespace constraint} provides for *validation* of attribute and element items that: 1. (any) have any namespace or are not namespace qualified; {namespace constraint} provides for *validation* of attribute and element items that: 1. (any) have any namespace or are not namespace qualified; {namespace constraint} provides for *validation* of attribute and element items that: 1. (any) have any namespace or are not namespace qualified; {namespace constraint} provides for *validation* of attribute and element items that: 1. (any) have any namespace or are not namespace qualified; {namespace constraint} provides for *validation* of attribute and element items that: 2. (not and a namespace name) have any namespace other than the specified namespace name; {namespace constraint} provides for *validation* of attribute and element items that: 2. (not and a namespace name) have any namespace other than the specified namespace name; {namespace constraint} provides for *validation* of attribute and element items that: 4. (a set whose members are either namespace names or *absent*) have any of the specified namespaces and/or, if *absent* is included in the set, are unqualified. {namespace constraint} provides for *validation* of attribute and element items that: 4. (a set whose members are either namespace names or *absent*) have any of the specified namespaces and/or, if *absent* is included in the set, are unqualified. {process contents} controls the impact on *assessment* of the information items allowed by wildcards, as follows: strict There must be a top-level declaration for the item available, or the item must have an xsi:type, and the item must be *valid* as appropriate. {process contents} controls the impact on *assessment* of the information items allowed by wildcards, as follows: strict There must be a top-level declaration for the item available, or the item must have an xsi:type, and the item must be *valid* as appropriate. {process contents} controls the impact on *assessment* of the information items allowed by wildcards, as follows: strict There must be a top-level declaration for the item available, or the item must have an xsi:type, and the item must be *valid* as appropriate. {process contents} controls the impact on *assessment* of the information items allowed by wildcards, as follows: strict There must be a top-level declaration for the item available, or the item must have an xsi:type, and the item must be *valid* as appropriate. {process contents} controls the impact on *assessment* of the information items allowed by wildcards, as follows: skip No constraints at all: the item must simply be well-formed XML. {process contents} controls the impact on *assessment* of the information items allowed by wildcards, as follows: skip No constraints at all: the item must simply be well-formed XML. {process contents} controls the impact on *assessment* of the information items allowed by wildcards, as follows: lax If the item, or any items among its [children] if it's an element information item, has a uniquely determined declaration available, it must be *valid* with respect to that definition, that is, *validate* where you can, don't worry when you can't. {process contents} controls the impact on *assessment* of the information items allowed by wildcards, as follows: lax If the item, or any items among its [children] if it's an element information item, has a uniquely determined declaration available, it must be *valid* with respect to that definition, that is, *validate* where you can, don't worry when you can't. {process contents} controls the impact on *assessment* of the information items allowed by wildcards, as follows: lax If the item, or any items among its [children] if it's an element information item, has a uniquely determined declaration available, it must be *valid* with respect to that definition, that is, *validate* where you can, don't worry when you can't. {process contents} controls the impact on *assessment* of the information items allowed by wildcards, as follows: lax If the item, or any items among its [children] if it's an element information item, has a uniquely determined declaration available, it must be *valid* with respect to that definition, that is, *validate* where you can, don't worry when you can't.