COSMOS SML Test Plan

COSMOS SML and SML-IF Validator Test Plan

Version 1.2, 11 August 2008

Authors: David Whiteman, Ali Mehregani

Introduction

The goal of this test plan is to document the test coverage for the SML and SML-IF validator found in the Eclipse COSMOS project. Using this document, we will describe the test suite used to achieve compliance with the SML and SML-IF 1.1 specifications.

The source for these tests can be found in the org.eclipse.cosmos.rm.validation.tests plug-in in CVS.

Test Suite

Acyclic Tests

Tests that check for valid cycles using sml:acyclic

Test Name	Description	Status
InvalidCyclesWithAcyclicReferences	This test verifies that it is an error to create cycles with instances of acyclic references	Complete
InvalidDerivationWithAcyclicAttribute	A model is invalid if it has a reference type R1 with sml:acyclic=?true? and another reference type R2 derived from R1 such that sml:acyclic=?false?	Complete
ValidateAcyclicDefinition	This test returns a warning if the sml:acyclic attribute is defined on an element declaration	Complete
ValidCyclesWithAcyclicReference1	Let R1 and R2 be two reference types with sml:acyclic=?true?. Then a model is valid if it has inter-document cycles that using instances of both R1 and R2	Complete
ValidCyclesWithAcyclicReference2	Let R1 be a reference type with sml:acyclic=?false?. Then a model is valid if it has inter-document cycles using instances of R1	Complete
ValidCycles3	This test verifies that it is valid to create cycles within documents, as long as instances of acyclic references do not create cycles.	Complete
ValidDerivationWithAcyclicAttribute	A model is valid if it has a reference type R1 with sml:acyclic=?false? and another reference type R2 derived from R1 such that sml:acyclic=?true?	Complete

Deref Tests

Tests that ensure proper operation of the deref() function

Test Name	Description	Status
InvalidSchemeDerefUsed	This test verifies that the code returns error when an smlxpath1 scheme contains a deref() in the evaluator. The deref() XPath extension function MUST NOT be present in the expression evaluation context function library when processing the location path in SMLXPath1_SchemeData : SMLXPath1_Fragment_ID ::= 'smlxpath1' '(' SMLXPath1_SchemeData ')' SMLXPath1_SchemeData ::= XPath1.0_LocationPath	Complete
MultipleDeref	Verify that deref() can accept a node set of reference elements, i.e., elements for which sml:ref=?true?, and return a node set that is union of the element nodes targeted by references in the node set such that the reference targets exactly one element in the model. The returned node set must not contain any nodes for references that do not target an element in the model.	Complete
MultipleXpointer	Verify that deref() can resolve references that target non-root elements using XPointer scheme.	Complete
SingleRef	Verify that deref() can resolve a single reference. The deref() function must return a single node (i.e. a node set with a single node) that corresponds to the element node of the reference’s target when the reference targets a single element in the model.	Complete

Identity Tests

Tests that validate the resolution of key references to elements

Test Name	Description	Status
InValidKeyDuplicate	Verify that a model with a key constraint is invalid if the field values are not unique.	Complete
InValidKeyMissing	Verify that a model with a key constraint is invalid if some field values are missing.	Complete
InValidUnique	Verify that a model with a unique constraint is invalid if the field values are not unique.	Complete
InvalidConstraintDefinition	This test returns a warning when the id constraints are defined on a complexType. They should be defined on an element declaration.	Complete
InvalidConstraintRefAttributes	Verifies that the code returns an error when the name attribute is specified on a constraint with the ref attribute specified. Ref attribute I am referring to here is the one defined on the keybase type. For each sml:key, sml:unique, or sml:keyref element with the ref attribute specified, {SML identity-constraints definitions} contains the component resolved to by the actual value of the ref attribute, with the following conditions: 1.The name attribute MUST NOT be specified.	Complete
InvalidConstraintRefElements	Verifies that the code returns an error when the sml:field and sml:selector child elements are defined on a constraint with the ref attribute specified. For each sml:key, sml:unique, or sml:keyref element with the ref attribute specified, {SML identity-constraints definitions} contains the component resolved to by the actual value of the ref attribute, with the following conditions: 2.The sml:selector and sml:field child elements MUST NOT be specified.	Complete
InvalidConstraintRefKey	Verifies that the code returns an error when the key's ref attribute value resolves to an element which is not a key.	Complete
InvalidConstraintRefKeyref	Verifies that the code returns an error when the keyref's ref attribute value resolves to a key element instead of a keyref element. For each sml:key, sml:unique, or sml:keyref element with the ref attribute specified, {SML identity-constraints definitions} contains the component resolved to by the actual value of the ref attribute, with the following conditions: If element is sml:keyref, then the value of the ref attribute MUST resolve to an SML keyref constraint [..]	Complete
InvalidConstraintRefNoKey	Verifies that the code returns an error when the key's ref attribute value doesn't resolve to an SML key constraint. For each sml:key, sml:unique, or sml:keyref element with the ref attribute specified, {SML identity-constraints definitions} contains the component resolved to by the actual value of the ref attribute, with the following conditions: If the element is sml:key, then the value of ref attribute MUST resolve to an SML key constraint.	Complete
InvalidConstraintRefNoKeyRef	Verifies that the code returns an error when the keyref's ref attribute value doesn't resolve to an SML keyref constraint. For each sml:key, sml:unique, or sml:keyref element with the ref attribute specified, {SML identity-constraints definitions} contains the component resolved to by the actual value of the ref attribute, with the following conditions: If element is sml:keyref, then the value of the ref attribute MUST resolve to an SML keyref constraint, and the refer attribute MUST NOT be specified.	Complete
InvalidConstraintRefNoKeyUnique	Verifies that the code returns an error when the unique's ref attribute value doesn't resolve to an SML unique constraint. For each sml:key, sml:unique, or sml:keyref element with the ref attribute specified, {SML identity-constraints definitions} contains the component resolved to by the actual value of the ref attribute, with the following conditions: If the element is sml:unique, then the value of the ref attribute MUST resolve to an SML unique constraint.	Complete
InvalidConstraintRefUnique	Verifies that the code returns an error when the unique's ref attribute value resolves to an element that is not of type sml:unique.	Complete
InvalidConstraintSubstitution	This test verifies that substitution group elements validate id constraints defined on their group affiliation. If an element declaration S has a {substitution group affiliation} G, then its {SML identity-constraints definitions} also contains members of {SML identity-constraints definitions} of G.	Complete
InvalidDuplicateConstraintName	This test verifies that the code returns a error when two constraints defined on an element have the same name ( Constraints should have unique names; ie there cannot be an sml:key that has the same name with a sml:key, sml:keyref or sml:unique on the same element declaration).	Complete
InvalidDuplicateConstraintName1	This test verifies that the code returns a error when two constraints defined on an element have the same name ( Constraints should have unique names; ie there cannot be an sml:key that has the same name with a sml:key, sml:keyref or sml:unique on the same element declaration). The {SML identity-constraints definitions} of an element declaration MUST NOT contain two identity constraints with the same name.	Complete
InvalidDuplicateConstraintSubst	This test verifies that the code returns a error when two constraints defined on an element have the same name ( Constraints should have unique names; ie there cannot be an sml:key that has the same name with a sml:key, sml:keyref or sml:unique on the same element declaration). If a global element declaration S has a {substitution group affiliation} G, then {SML identity-constraints definitions} of S MUST be a superset of that of G.	Complete
ValidConstraintRefKeyref	Verifies that the code returns success when the keyref's ref attribute value resolves to a keyref element. For each sml:key, sml:unique, or sml:keyref element with the ref attribute specified, {SML identity-constraints definitions} contains the component resolved to by the actual value of the ref attribute, with the following conditions: If element is sml:keyref, then the value of the ref attribute MUST resolve to an SML keyref constraint [..]	Complete
ValidKeyref	Verify keyref constraint.	Complete
ValidKeyUnique	Verify that a model with a key and unique constraint is valid if the field values are unique, though some field values for the unique constraint may be missing.	Complete
ValidKeyUniqueInScopeOnly	Verify that a model with a key and unique constraint is valid if the constraints are satisfied in scope even though the constraints may not be satisfied globally in the model.	Complete

Model Completeness Tests

Tests that check for the completeness of the model

Test Name	Description	Status
InValidInCompleteModel	This test verifies that an incomplete model is invalid	Complete

miscellaneous

No description provided

Test Name	Description	Status
TestDocumentLocator	A model is invalid if one/more documents in the model are specified through an external locator and the validator is unable to retrieve these documents.	Complete

Miscellaneous Tests

Tests that check miscellaneous issues to ensure valid SML documents

Test Name	Description	Status
InValidAliasValue	This test verifies that the code returns an error when an alias contains an invalid value.	Complete
InValidAliasHasFragmentComp	This test verifies that the code returns an error when an alias contains a fragment component.	Complete
InvalidBase64Content	This test verifies that the code returns an error when a document that is a child of the base64Data element is not encoded in Base64 format.	Complete
InvalidDataContentBase64	This test verifies that the code returns an error when a document that is a child of the data element is encoded in base64 format.	Complete
InValidDuplicateAliases	This test verifies that the code returns an error when two aliases resolve to the same URI	Complete
InvalidMultipleDocument	This test verifies that the code returns an error if the data element contains more than one document.	Complete
TestDocumentLocator	Tests the correct implementation of the locator element	Complete
TestRulesWithMultiplePatterns	Tests that rules that have multiple patterns are handled correctly	Complete
TestMultipleRulesUnderOnePattern	Tests that patterns with multiple rules are handled correctly	Complete
ValidateSchemaBinding	Used to ensure that a warning is displayed when a schema binding element is used in an SML-IF document	Complete
TestSchemaValidationFailure	Tests that validation against the schema fails.	Complete
ValidBase64Content	This test verifies that the code returns success when a document that is a child of the base64Data element is encoded in Base64 format.	Complete
ValidateDefaultSchemaBinding	This test verifies that the code is using the defaultSchema information to locate the definition file for instance documents not included in schemaBinding. In this sample, the Course1 and Course2 instances should be validated against the University.xsd schema. Course3 will be validated against the Univerity_v1.xsd schema since Course3 is not included in any schemaBinding element.	Complete
ValidEmptyDocument	This test verifies that it is valid to have an empty document.	Complete
ValidateNoSchemaBinding	If a namespace ns is not included in any schemaBinding or defaultSchema element, then the schema defining this namespace is built by composing all definition documents whose target namespace matches ns. This resulted schema will be used to validate any instance document using ns namespace. The test should return an error on acyclic	Complete
ValidateSchemaBinding	This test verifies that the code is using the schemaBinding information to locate the definition file for instance documents. In this sample, there are two xsd files with the same namespace, tns. The instance documents are bound to the first xsd definition, University.xsd using the schemaBinding element. As a result, the validation should be run using the schema defined in University.xsd and ignore University_v1.xsd. The validation returns success since Univesity.xsd does not have the acyclic attribute specified on the OptionalCourseRefType type. If the schemaBinding is ignored, then the validator should return error ( the schema file used to validate the instances will be composed from both xsd files; the first definition of the OptionalCourseRefType type in the University.xsd will be overwritten by the OptionalCourseRefType - acyclic = true in the University_v1.xsd )	Complete

Reference Tests

Tests that validate the implementation of sml:ref

Test Name	Description	Status
DanglingRef	A valid model can contain dangling references	Complete
IntraDocumentRef	It is valid for a reference to target an element in the same document.	Complete
InValidBaseURI	A model is invalid if base URI is not valid	Complete
InValidBaseURIHasFragmentComp	A model is invalid if the base URI contains a fragment	Complete
InvalidRefTwoSchemes	A model is invalid if it contains a reference with two schemes, one resolving to an element and the other dangling	Complete
InvalidRefOneSchemeResolves	A model is invalid if a reference contains multiple schemes resolving to different elements.	Complete
InValidMissingBaseURIAttr1	A model is invalid if a reference is relative and the base URI is missing	Complete
InvalidRefResolvesToMultipleElements	A model is invalid if a reference scheme resolves to multiple elements	Complete
InvalidRefResolvesToMultipleElements	A model is invalid if a reference element is identified with sml:ref="1" and its scheme resolves to multiple elements	Incomplete
InvalidNillRefDefinition	A model is invalid if sml:nilref is used on an element that is not a reference element	Incomplete
SingleRef	The deref() function of a nullified reference should not return a target even if the ref has a valid sml:uri child element.	Incomplete
InvalidSchemeResultContainsNonElements	A model is invalid if a reference using smlxpath1 scheme resolves to anything other than an element set.	Complete
InvalidSchemeSyntaxError	A model is invalid if the content of the smlxpath1 scheme is syntactically incorrect.	Complete
InvalidSmlRefValue	A model is invalid if the value of sml:ref is not valid	Complete
InvalidSchemeNamespaceUnknown	A model is invalid if a reference using the smlxpath1 scheme uses a prefix without a bound namespace.	Complete
MultipleRefToAnElement	It is valid for an element in a document to be targeted by multiple different references from other documents	Complete
NullRefElement	It is valid for a reference element to be null	Complete
RefToNonRootElement	It is valid for a reference in a document to target a non-root element in some other document.	Complete
RefToRootElement	It is valid for a reference in a document to target the root element in some other document.	Complete
ValidRefTwoSchemesNilSpecified	A model is valid if it contains a nullified reference with two schemes, one resolving to an element and another dangling.	Incomplete
ValidRefNilrefSpecified1	A model is valid if it contains a none reference element (i.e. sml:ref is not specified) with multiple schemes resolving to two different elements	Incomplete
ValidRefNilrefSpecified1	A model is valid if it contains a nullified reference with multiple schemes resolving to two different elements	Complete
ValidMissingBaseURIAttr1	A model is valid if there are not references and the base URI is missing	Complete
ValidRefTwoSchemes	A model is valid if a reference contains two schemes, both resolving to the same element	Complete
ValidNilRefDefinition	A model is valid if sml:nilref is used in conjunction with sml:ref="true"	Incomplete
ValidSchemeNamespaceInherited	A model is valid when a reference using the smlxpath1 scheme uses a prefix declared in a containing element	Incomplete
ValidRefOneSchemeResolvesOtherUnknown	A model is valid if a reference contains two schemes, one resolving to an element and the other being unknown.	Complete

Rule Tests

Tests that ensure that Schematron rules and rule bindings are correctly handled

Test Name	Description	Status
InValidSchematronRule	A model with a Schematron rule defined for an element is invalid if at least one instances of the element does not satisfy the rule.	Complete
InValidSchematronRule	A model with a Schematron rule defined for an element is invalid if at least one instances of the element does not satisfy the rule. Error message will be taken from the English resource bundle.	Complete
InValidSchematronRule	A model with a Schematron rule defined for an element is invalid if at least one instances of the element does not satisfy the rule. Error message will be taken from the German resource bundle.	Complete
InValidSchematronRule	A model with a Schematron rule defined for an element is invalid if at least one instances of the element does not satisfy the rule. locid indicates the locale of the error message to be French, but since French resource bundle doesn't exist, we expect the error message to be taken from the English resource bundle (the default locale).	Complete
InValidSchematronRule	A model with a Schematron rule defined for an element is invalid if at least one instances of the element does not satisfy the rule. locid indicates the locale of the error message to be French, but since French resource bundle doesn't exist, we expect the error message to be taken from the English resource bundle (the default locale).	Complete
InValidSchematronRule	A model with a Schematron rule defined for an element is invalid if at least one instances of the element does not satisfy the rule. locid is specified in a schematron to get a message from the English resource bundle. However, since the key "abc" does not exist in the resource bundle, the text in the schematron is used.	Complete
InValidRuleBinding-MultipleRulesSameDocument	Two rules are bound to the same document - both fail.	Complete
InValidRuleBinding-MultipleRulesSameDocument	Two rules are bound to the same document. One passes, one fails.	Complete
InValidRuleBinding	A model with a Schematron rule that is bound to some instance documents is invalid if the rule is not satisfied by some bound documents.	Complete
InValidRuleType	A model with a Schematron rule defined for a type CT is invalid if at least one instance element of CT type doesn't satisfy the rule.	Complete
InValidRuleTypeExtension	A model with a Schematron rule defined for a type CT is invalid if at least one instance element of CT type or a type derived from CT ( derivation by extension ) doesn't satisfy the rule.	Complete
InValidRuleTypeRestriction	A model with a Schematron rule defined for a type CT is invalid if at least one instance element of CT type or a type derived from CT ( derivation by restriction ) doesn't satisfy the rule.	Complete
ValidSchematronRule	A model with a Schematron rule defined for an element is valid if all instances of the element satisfy the rule.	Complete
ValidXMLSchema	Basic XML Schema file, no SML extensions used.	Complete
ValidRuleBinding	A model with a Schematron rule that is bound to some instance documents is valid if the rule is satisfied by all bound documents.	Complete

Schema Binding Tests

Tests the optional schema binding feature of SML.

Test Name	Description	Status
NoSchemaBinding	Schema binding with a default binding	Complete
NoSchemaBinding	This SML-IF document is composed of two schema documents, S1 & S2, and three instance documents, I1, I2, & I3. <S1, I1, I2, I3> is a valid set whereas <S2, I1, I2, I3> is invalid. The default binding is used to bind S2 with I1, I2, and I3	Complete
NoSchemaBinding	This SML-IF document attempts to bind S1 to dangling instance documents. It also attempts to bind the instance documents to a dangling definition document.	Complete
NoSchemaBinding	This SML-IF document is composed of two schema documents, S1 & S2, and three instance documents, I1, I2, & I3. <S1, I1, I2, I3> is a valid set whereas <S2, I1, I2, I3> is invalid. Schema binding is used to describe both validation sets	Complete
NoSchemaBinding	This SML-IF document attempts to bind S1 to dangling instance documents. It also attempts to bind the instance documents to a dangling definition document.	Complete
NoSchemaBinding	This SML-IF document is composed of two schema documents, S1 & S2, and three instance documents, I1, I2, & I3. <S1, I1, I2, I3> is a valid set whereas <S2, I1, I2, I3> is invalid. Schema binding is used to describe the latter.	Complete
NoSchemaBinding	Schema binding with a missing document alias	Complete
NoSchemaBinding	Schema binding with multiple bindings	Complete
NoSchemaBinding	This SML-IF document is composed of two schema documents, S1 & S2, and three instance documents, I1, I2, & I3. <S1, I1, I2, I3> is a valid set whereas <S2, I1, I2, I3> is invalid. Schema binding is used to describe the former.	Complete

smlModelUnits

No description provided

Test Name	Description	Status

Target Element Tests

Tests that ensure correct implementation of targetElement

Test Name	Description	Status
InValidTargetElement	If targetElement=?GTE? for a global element declaration E, then a model is invalid if the target of some instance of E in the model is not an instance of GTE.	Complete
InValidDerivationByRestriction	If the element declaration ED is contained (directly, indirectly, or implicitly) in a content model of a complex type D, who is a restriction of another complex type B and B contains an element declaration EB with the same name as ED, then{target element} of ED is the same as that of EB. In the example below, the EnrolledCourse element contained by the GraduateStudentType should have the same {targetElement} as the EnrolledCourse element contained by the StudentType.	Complete
InValidSameNameElements	If two element declarations E1 and E2 have the same {namespace name} and {name} and they are both contained (directly, indirectly, or implicitly) in a content model of a complex type, then E1 and E2 have the same {target required}, {target element}, and {target type}. In the example below, the two EnrolledCourse elements contained by the StudentType through the graduateGroup and basicGroup should have the same {targetElement}.	Complete
ValidateTargetElementExists2	This test verifies that the value of the sml:targetElement is a global element. Returns an error if the value does not match any element in the corresponding namespace. The test verifies that the error is displayed even when no model instances are defined for this IF document (ie the validation runs against the xsd file containing the sml:targetElement, regardless of the instances being defined in that model)	Complete
InValidTargetElementWithSubstitutionGroup	Let targetElement=?GTE? be specified for a GED E. Let SubE be another GED in the substitution group whose head element is E for which the targetElement attribute is not specified. Then a model is invalid if an instance of SubE targets an element that is not an instance of GTE or an instance of some GED in the substitution group hierarchy whose head is GTE.	Complete
ValidTargetElement	If targetElement=?GTE? for a global element declaration E, then a model is valid if the target of each instances of E in the model is an instance of GTE.	Complete
ValidateTargetElementDefinition	This test returns a warning if the sml:targetElement attribute is defined on a type definition.	Complete
ValidDerivationByRestriction	If the element declaration ED is contained (directly, indirectly, or implicitly) in a content model of a complex type D, who is a restriction of another complex type B and B contains an element declaration EB with the same name as ED, then{target element} of ED is the same as that of EB. In the example below, the EnrolledCourse element contained by the GraduateStudentType has the same {targetElement} as the EnrolledCourse element contained by the StudentType.	Complete
ValidSameNameElements	If two element declarations E1 and E2 have the same {namespace name} and {name} and they are both contained (directly, indirectly, or implicitly) in a content model of a complex type, then E1 and E2 have the same {target required}, {target element}, and {target type}. In the example below, the two EnrolledCourse elements contained by the StudentType through the basicGroup and graduateGroup have the same {targetElement}.	Complete
ValidTargetElementWithSubstitutionGroup	If targetElement=?GTE? for a global element declaration E, then a model is valid if the target of each instances of E in the model is an instance of GTE, or an instance of some global element declaration in the substitution group hierarchy whose head is GTE	Complete

Target Required Tests

Tests that ensure correct validation of sml:targetRequired attribute

Test Name	Description	Status
ValidTargetElement	If targetElement=GTE for a global element declaration E, then a model is valid if the target of each instances of E in the model is an instance of GTE.	Complete
InValidDerivationByRestriction	If the element declaration ED is contained (directly, indirectly, or implicitly) in a content model of a complex type D, who is a restriction of another complex type B and B contains an element declaration EB with the same name as ED, then {target required} of ED is the same as that of EB. In the example below, the EnrolledCourse element contained by the GraduateStudentType should have the same {target required} as the EnrolledCourse element contained by the StudentType.	Complete
InValidSameNameElements	If two element declarations E1 and E2 have the same {namespace name} and {name} and they are both contained (directly, indirectly, or implicitly) in a content model of a complex type, then E1 and E2 have the same {target required}, {target element}, and {target type}. In the example below, the two EnrolledCourse elements contained by the StudentType through the graduateGroup and basicGroup should have the same {target required}.	Complete
ValidTargetType	If targetType=?T? for a global element declaration E, then a model is valid if the type of the target of each instances of E in the model is T or a derived type of T	Complete
ValidTargetElementWithSubstitutionGroup	If targetElement="GTE" for a global element declaration E, then a model is valid if the target of each instances of E in the model is an instance of GTE, or an instance of some global element declaration in the substitution group hierarchy whose head is GTE	Complete
ValidTargetElement	If targetElement=GTE for a global element declaration E, then a model is valid if the target of each instances of E in the model is an instance of GTE.	Complete
ValidateTargetRequireDefinition	This test returns a warning if the sml:targetRequired attribute is defined on a type definition.	Complete
ValidDerivationByRestriction	If the element declaration ED is contained (directly, indirectly, or implicitly) in a content model of a complex type D, who is a restriction of another complex type B and B contains an element declaration EB with the same name as ED, then {target required} of ED is the same as that of EB. In the example below, the EnrolledCourse element contained by the GraduateStudentType has the same {target required} as the EnrolledCourse element contained by the StudentType.	Complete
ValidTargetElement	If targetElement=GTE for a global element declaration E, then a model is valid if the target of each instances of E in the model is an instance of GTE.	Complete
ValidSameNameElements	If two element declarations E1 and E2 have the same {namespace name} and {name} and they are both contained (directly, indirectly, or implicitly) in a content model of a complex type, then E1 and E2 have the same {target required}, {target element}, and {target type}. In the example below, the two EnrolledCourse elements contained by the StudentType through the basicGroup and graduateGroup have the same {target required}.	Complete
ValidTargetType	If targetType="T" for a global element declaration E, then a model is valid if the type of the target of each instances of E in the model is T or a derived type of T	Complete
ValidTargetType	If targetType="T" for a global element declaration E, then a model is valid if the type of the target of each instances of E in the model is T or a derived type of T	Complete
ValidTargetElementWithSubstitutionGroup	If targetElement="GTE" for a global element declaration E, then a model is valid if the target of each instances of E in the model is an instance of GTE, or an instance of some global element declaration in the substitution group hierarchy whose head is GTE	Complete
ValidTargetElementWithSubstitutionGroup	If targetElement="GTE" for a global element declaration E, then a model is valid if the target of each instances of E in the model is an instance of GTE, or an instance of some global element declaration in the substitution group hierarchy whose head is GTE	Complete

Target Type Tests

Tests that ensure correct validation of targetType

Test Name	Description	Status
InValidTargetType	If targetType=?T? for a global element declaration E, then a model is invalid if the type of the target of some instance of E in the model is not T	Complete
InValidDerivationByRestriction	If the element declaration ED is contained (directly, indirectly, or implicitly) in a content model of a complex type D, who is a restriction of another complex type B and B contains an element declaration EB with the same name as ED, then {target type} of ED is the same as that of EB. In the example below, the EnrolledCourse element contained by the GraduateStudentType should have the same {targetType} as the EnrolledCourse element contained by the StudentType.	Complete
InValidSameNameElements	If two element declarations E1 and E2 have the same {namespace name} and {name} and they are both contained (directly, indirectly, or implicitly) in a content model of a complex type, then E1 and E2 have the same {target required}, {target element}, and {target type}. In the example below, the two EnrolledCourse elements contained by the StudentType through the graduateGroup and basicGroup should have the same {target type}.	Complete
ValidateTargetTypeExists1	This test verifies that the value of the sml:targetType resolves to a global type definition. Returns an error if the value does not match any type in the corresponding namespace. The test verifies that the error is displayed even when no model instances are defined for this IF document (ie the validation runs against the xsd file containing the sml:targetType, regardless of the instances being defined in that model)	Complete
InValidTargetTypeWithSubstitutionGroup	Let targetType=?T? be specified for a GED E. Let SubE be another GED in the substitution group whose head element is E for which the targetType attribute is not specified. Then a model is invalid if an instance of SubE targets an element that is not an instance of T or an instance of some derived type of T.	Complete
ValidTargetType	If targetType=?T? for a global element declaration E, then a model is valid if the type of the target of each instances of E in the model is T or a derived type of T	Complete
ValidateTargetTypeDefinition	This test returns a warning if the sml:targetType attribute is defined on a type definition.	Complete
ValidDerivationByRestriction	If the element declaration ED is contained (directly, indirectly, or implicitly) in a content model of a complex type D, who is a restriction of another complex type B and B contains an element declaration EB with the same name as ED, then {target type} of ED is the same as that of EB. In the example below, the EnrolledCourse element contained by the GraduateStudentType has the same {targetType} as the EnrolledCourse element contained by the StudentType.	Complete
ValidSameNameElements	If two element declarations E1 and E2 have the same {namespace name} and {name} and they are both contained (directly, indirectly, or implicitly) in a content model of a complex type, then E1 and E2 have the same {target required}, {target element}, and {target type}. In the example below, the two EnrolledCourse elements contained by the StudentType through the graduateGroup and basicGroup have the same {target type}.	Complete
ValidTargetTypeWithSubstitutionGroup	Let targetType=?T? be specified for a GED E. Let SubE be another GED in the substitution group whose head element is E for which the targetType attribute is not specified. Then a model is valid if all instances of SubE target elements whose type is T.	Complete