Annotations provide for human- and machine-targeted annotations of schema components. In the test the human-targeted annotation is provided for an Identity-constraint Definition. Annotations provide for human- and machine-targeted annotations of schema components. In the test the human-targeted annotation is provided for an Identity-constraint Definition. The annotation is misplaced. Annotations provide for human- and machine-targeted annotations of schema components. In the test the human-targeted annotation is provided for an Identity-constraint Definition. 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 an Identity-constraint Definition. Annotations provide for human- and machine-targeted annotations of schema components. In the test the machine-targeted annotation is provided for an Identity-constraint Definition. The annotation is misplaced. Annotations provide for human- and machine-targeted annotations of schema components. In the test the machine-targeted annotation is provided for an Identity-constraint Definition. The annotation is specified twice. Define a uniqueness constraint with fields of different types. The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the fields of type decimal have values 3.0 and -3. The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the fields of type decimal have values 3.0 and 3. The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the fields of type decimal have values 3.0 and 3.0. The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the fields of type string have values 3.0 and 3. The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the fields of type string have values 3.0 and 3.0. The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the first field of type string has value "3.0". The second field of type decimal has value "-3". The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the first field of type string has value "3.0". The second field of type decimal has value "3". The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the first field of type string has value "3.0". The second field of type decimal has value "3.0". The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the first field of type string has value "3.0". The second field of type string has value "3". The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the first field of type string has value "3.0". The second field of type string has value "3.0". The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the fields have local type decimal and values "3.0" and "-3". The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the fields have local type decimal and values "3.0" and "3". The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the fields have local type decimal and values "3.0" and "3.0". The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the fields have local type string and values "3.0" and "3". The equality and inequality conditions appealed to in checking these constraints apply to the value of the fields selected, so that for example 3.0 and 3 would be conflicting keys if they were both number, but non-conflicting if they were both strings, or one was a string and one a number. In the test the fields have local type string and values "3.0" and "3.0". Declare an element. Define a key identity constraint. Define another key identity constraint with another name. Check that the schema is valid. Declare an element. Define a key identity constraint. Define another key identity constraint with the same name. Check that the schema is invalid. With the same name declare a global element, a local element, an attribute, define a type and a constraint. Check that there is no name clash. Declare an element. Define a key identity constraint and a keyref to that key inside the element declaration. Declare another element with the same key and keyref. Check that if the second element declaration is in the same namespace, that the schema is invalid, otherwise it is valid. Declare an element. Define a key identity constraint and a keyref to that key inside the element declaration. Declare another element with the same key and keyref. Check that if the second element declaration is in the same namespace, that the schema is invalid, otherwise it is valid.