Revision as of 10:00, 11 March 2008 (view source) David whiteman.us.ibm.com (Talk | contribs) ← Older edit		Revision as of 16:21, 11 March 2008 (view source) David whiteman.us.ibm.com (Talk | contribs) (→‎Acyclic Tests) Newer edit →
Line 13:		Line 13:
	== Test Suite ==		== Test Suite ==
−	=== Acyclic Tests ===	+
−	Tests that check for valid cycles using sml:acyclic	+
	=== Acyclic Tests ===		=== Acyclic Tests ===

---

Revision as of 16:21, 11 March 2008

COSMOS SML and SML-IF Validator Test Plan

Version 1.0, 10 March 2008

Author: David Whiteman

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

InvalidCyclesWithAcyclicReferences

File: acyclic\InValidCycles.xml (src)

Description: This test verifies that it is an error to create cycles with instances of acyclic references

InvalidDerivationWithAcyclicAttribute

File: acyclic\InValidDerivation.xml (src)

Description: 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”

ValidateAcyclicDefinition

File: acyclic\ValidateDefinition.xml (src)

Description: This test returns a warning if the sml:acyclic attribute is defined on an element declaration

ValidCyclesWithAcyclicReference1

File: acyclic\ValidCycles1.xml (src)

Description: 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

ValidCyclesWithAcyclicReference2

File: acyclic\ValidCycles2.xml (src)

Description: 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

ValidCycles3

File: acyclic\ValidCycles3.xml (src)

Description: This test verifies that it is valid to create cycles within documents, as long as instances of acyclic references do not create cycles.

ValidDerivationWithAcyclicAttribute

File: acyclic\ValidDerivation.xml (src)

Description: 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”

Deref Tests

Tests that ensure proper operation of the deref() function

MultipleDeref

File: deref\Multiple.xml (src)

Description: 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.

MultipleXpointer

File: deref\MultipleNonRoot.xml (src)

Description: Verify that deref() can resolve references that target non-root elements using XPointer scheme.

SingleRef

File: deref\Single.xml (src)

Description: 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.

Identity Tests

Tests that validate the resolution of key references to elements

InValidKeyDuplicate

File: identity\InValidKeyDuplicate.xml (src)

Description: Verify that a model with a key constraint is invalid if the field values are not unique.

InValidKeyMissing

File: identity\InValidKeyMissing.xml (src)

Description: Verify that a model with a key constraint is invalid if some field values are missing.

InValidUnique

File: identity\InValidUnique.xml (src)

Description: Verify that a model with a unique constraint is invalid if the field values are not unique.

InvalidConstraintDefinition

File: identity\LC\InValidConstraintDefinition.xml (src)

Description: This test returns a warning when the id constraints are defined on a complexType. They should be defined on an element declaration.

InvalidConstraintRefAttributes

File: identity\LC\InValidConstraintRefAttributes.xml (src)

Description: 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.

InvalidConstraintRefElements

File: identity\LC\InValidConstraintRefElements.xml (src)

Description: 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.

InvalidConstraintRefKey

File: identity\LC\InValidConstraintRefKey.xml (src)

Description: Verifies that the code returns an error when the key's ref attribute value resolves to an element which is not a key.

InvalidConstraintRefKeyref

File: identity\LC\InValidConstraintRefKeyref.xml (src)

Description: 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 [..]

InvalidConstraintRefNoKey

File: identity\LC\InValidConstraintRefNoKey.xml (src)

Description: 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.

InvalidConstraintRefNoKeyRef

File: identity\LC\InValidConstraintRefNoKeyref.xml (src)

Description: 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.

InvalidConstraintRefNoKeyUnique

File: identity\LC\InValidConstraintRefNoUnique.xml (src)

Description: 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.

InvalidConstraintRefUnique

File: identity\LC\InValidConstraintRefUnique.xml (src)

Description: 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.

InvalidConstraintSubstitution

File: identity\LC\InValidConstraintSubstitution.xml (src)

Description: 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.

InvalidDuplicateConstraintName

File: identity\LC\InValidDuplicateConstraintName.xml (src)

Description: 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).

InvalidDuplicateConstraintName1

File: identity\LC\InValidDuplicateConstraintName1.xml (src)

Description: 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.

InvalidDuplicateConstraintSubst

File: identity\LC\InValidDuplicateConstraintNameSubst.xml (src)

Description: 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.

ValidConstraintRefKeyref

File: identity\LC\ValidConstraintRefKeyref.xml (src)

Description: 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 [..]

ValidKeyref

File: identity\ValidKeyref.xml (src)

Description: Verify keyref constraint.

ValidKeyUnique

File: identity\ValidKeyUnique.xml (src)

Description: 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.

ValidKeyUniqueInScopeOnly

File: identity\ValidKeyUniqueInScopeOnly.xml (src)

Description: 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.

Incomplete Tests

Tests that check for the completeness of the model

InValidInCompleteModel

File: incomplete\InValid.xml (src)

Description: This test verifies that an incomplete model is invalid

Miscellaneous Tests

Tests that check miscellaneous issues to ensure valid SML documents

TestDocumentLocator

File: others\remote-document.xml (src)

Description: Tests the correct implementation of the locator element

TestRulesWithMultiplePatterns

File: others\rulesWithMultiplePattern.xml (src)

Description: Tests that rules that have multiple patterns are handled correctly

TestMultipleRulesUnderOnePattern

File: others\rulesWithMultipleRulesUnderOnePattern.xml (src)

Description: Tests that patterns with multiple rules are handled correctly

TestSchemaValidationFailure

File: others\schemaValidationFailure.xml (src)

Description: Tests that validation against the schema fails.

Reference Tests

Tests that validate the implementation of sml:ref

InvalidRefOneSchemeResolves

File: references\ConsistentReferences\InvalidRefOneSchemeResolves.xml (src)

Description: An SML model MUST be declared invalid when a recognized scheme resolves to a target that's different from the target resolved to by another recognized scheme or when one recognized scheme resolves and another does not. This test verifies that the code returns an error when an SML references contains two reference scheme, resolving to two different elements.

InvalidRefResolvesToMultipleElements

File: references\ConsistentReferences\InvalidRefResolvesToMultipleElements.xml (src)

Description: Every non-null reference MUST target at most one element in a model. When a recognized scheme in a reference resolves to more than one target then the model MUST be declared invalid. This test verifies that the code returns an error when an SML references contains a reference scheme that resolves to more than one element.

InvalidRefTwoSchemes

File: references\ConsistentReferences\InvalidRefTwoSchemes.xml (src)

Description: An SML model MUST be declared invalid when a recognized scheme resolves to a target that's different from the target resolved to by another recognized scheme or when one recognized scheme resolves and another does not. This test verifies that the code returns an error when an SML references contains two reference scheme, and one scheme resolves while the other doesn't.

ValidRefNilrefSpecified1

File: references\ConsistentReferences\ValidRefNilrefSpecified1.xml (src)

Description: A null reference is an explicit declaration of intent by the document author that the reference itself does not exist, and a processing directive (not a hint) to processors not to attempt to recognize any reference schemes in it.If a reference element is recognized as null, then processors MUST NOT attempt to resolve it. The question of whether a null reference is resolved or not is undefined; it is an ill-formed question. This test verifies that the validator does not try to resolve a reference that is marked as null. If the reference is to be resolved, the validator will return an exception since the two reference schemes resolve to two different elements. This test should return success because the sml:nilref is specified.

ValidRefOneSchemeResolvesOtherUnknown

File: references\ConsistentReferences\ValidRefOneSchemeResolvesOtherUnknown.xml (src)

Description: An SML model MUST be declared invalid when a recognized scheme resolves to a target that's different from the target resolved to by another recognized scheme or when one recognized scheme resolves and another does not. This test verifies that the code returns success when an SML references contains two reference scheme, one resolving to a valid target and the other scheme being unknown to the processor.

ValidRefTwoSchemes

File: references\ConsistentReferences\ValidRefTwoSchemes.xml (src)

Description: An SML model MUST be declared invalid when a recognized scheme resolves to a target that's different from the target resolved to by another recognized scheme or when one recognized scheme resolves and another does not. This test verifies that the code returns success when an SML references contains two reference scheme, both resolving to the same target.

ValidRefTwoSchemesNilSpecified

File: references\ConsistentReferences\ValidRefTwoSchemesNilSpecified.xml (src)

Description: A null reference is an explicit declaration of intent by the document author that the reference itself does not exist, and a processing directive (not a hint) to processors not to attempt to recognize any reference schemes in it.If a reference element is recognized as null, then processors MUST NOT attempt to resolve it. The question of whether a null reference is resolved or not is undefined; it is an ill-formed question. This test verifies that the validator does not try to resolve a reference that is marked as null. If the reference below is to be resolved, the validator will return an exception since only one reference scheme resolves. This test should return success because the sml:nilref is specified.

ValidRefTwoSchemesReturnsNull

File: references\ConsistentReferences\ValidRefTwoSchemesReturnsNull.xml (src)

Description: A null reference is an explicit declaration of intent by the document author that the reference itself does not exist, and a processing directive (not a hint) to processors not to attempt to recognize any reference schemes in it.If a reference element is recognized as null, then processors MUST NOT attempt to resolve it. The question of whether a null reference is resolved or not is undefined; it is an ill-formed question. This test verifies that the validator does not try to resolve a reference that is marked as null. If the reference below is to be resolved, the validator will return a non null target element. This test should return success but with a reference target of null.

DanglingRef

File: references\DanglingRef.xml (src)

Description: This test verifies that a valid model can contain dangling references

EmptyRefElement

File: references\EmptyRefElement.xml (src)

Description: This test verifies that reference elements can be empty

IntraDocumentRef

File: references\IntraDocumentRef.xml (src)

Description: This test verifies that a reference element can target an element in the same document

MultipleRefToAnElement

File: references\MultipleRefToAnElement.xml (src)

Description: This test verifies that an element can be targeted by multiple different references

NullRefElement

File: references\NullRefElement.xml (src)

Description: This test verifies that reference elements can be null

InvalidNillRefDefinition

File: references\NullReferences\InvalidNilRefDefinition.xml (src)

Description: This test verifies that sml:nilref attribute is only defined on instance elements with sml:ref="true" specified. This global attribute is used to identify null reference elements. This attribute MUST NOT be used on an element unless it also has sml:ref="true" specified.

InvalidNillRefDefinition

File: references\NullReferences\ValidNilRefDefinition.xml (src)

Description: This test verifies that sml:nilref attribute can only be defined on instance elements with sml:ref="true" specified. This global attribute is used to identify null reference elements. This attribute MUST NOT be used on an element unless it also has sml:ref="true" specified.

RefToNonRootElement

File: references\RefToNonRootElement.xml (src)

Description: This test verifies that a reference element in a document can target non-root elements in some other document

RefToRootElement

File: references\RefToRootElement.xml (src)

Description: This test verifies that a reference element in a document can target the root element in some other document

InvalidSchemeDerefUsed

File: references\smlxpath1Scheme\InvalidSchemeDerefUsed.xml (src)

Description: 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

InvalidSchemeNamespaceUnknown

File: references\smlxpath1Scheme\InvalidSchemeNamespaceUnknown.xml (src)

Description: This test verifies that the code returns error when an smlxpath1 scheme uses a namespace not defined in the containing element. Namespace Binding Context: The smlxpath1() scheme inherits the set of namespace bindings available to the containing element.

InvalidSchemeResultContainsNonElements

File: references\smlxpath1Scheme\InvalidSchemeResultContainsNonElements.xml (src)

Description: This test verifies that the code returns error when an smlxpath1 scheme resolves to a set containing non-elements. The element(s) targeted by a scheme instance are obtained by applying the location path in SMLXPath1_SchemeData to the root element of the document in the document context. The result MUST be a set of elements. The set MAY be empty. If the result of applying the location path is something other than a set of elements, then the XPointer result is an error.

InvalidSchemeSyntaxError

File: references\smlxpath1Scheme\InvalidSchemeSyntaxError.xml (src)

Description: This test verifies that the code returns error when an smlxpath1 location path has an invalid syntax.

ValidSchemeNamespaceInherited

File: references\smlxpath1Scheme\ValidSchemeNamespaceInherited.xml (src)

Description: This test verifies that the code returns success when an smlxpath1 scheme uses a namespace defined by the containing element. Namespace Binding Context: The smlxpath1() scheme inherits the set of namespace bindings available to the containing element.

ValiSchemeNamespaceInherited

File: references\smlxpath1Scheme\ValidSchemeNamespaceInherited1.xml (src)

Description: This test verifies that the code returns success when an smlxpath1 scheme uses a namespace defined by the containing element. Namespace Binding Context: The smlxpath1() scheme inherits the set of namespace bindings available to the containing element.

Rule Tests

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

InValidSchematronRule

File: Rules\InValid.xml (src)

Description: 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.

InValidRuleBinding-MultipleRulesSameDocument

File: Rules\InValidRuleBinding-MultipleRulesSameDocument-BothFail.xml (src)

Description: Two rules are bound to the same document - both fail.

InValidRuleBinding-MultipleRulesSameDocument

File: Rules\InValidRuleBinding-MultipleRulesSameDocument.xml (src)

Description: Two rules are bound to the same document. One passes, one fails.

InValidRuleBinding

File: Rules\InValidRuleBinding.xml (src)

Description: 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.

InValidRuleType

File: Rules\InValidRuleType.xml (src)

Description: 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.

InValidRuleTypeExtension

File: Rules\InValidRuleTypeExtension.xml (src)

Description: 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.

InValidRuleTypeRestriction

File: Rules\InValidRuleTypeRestriction.xml (src)

Description: 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.

ValidSchematronRule

File: Rules\Valid.xml (src)

Description: A model with a Schematron rule defined for an element is valid if all instances of the element satisfy the rule.

ValidXMLSchema

File: Rules\ValidNoSML.xml (src)

Description: Basic XML Schema file, no SML extensions used.

ValidRuleBinding

File: Rules\ValidRuleBinding.xml (src)

Description: A model with a Schematron rule that is bound to some instance documents is valid if the rule is satisfied by all bound documents.

SML-IF 1.1 Tests

Tests that validate the implementation of new SML-IF 1.1 conditions and features

InValidAliasHasFragmentComp

File: smlif_lc\InValidAliasHasFragmentComp.xml (src)

Description: This test verifies that the code returns an error when an alias contains a fragment component.

InValidAliasValue

File: smlif_lc\InValidAliasValue.xml (src)

Description: This test verifies that the code returns an error when an alias contains an invalid value.

InvalidBase64Content

File: smlif_lc\InvalidBase64Content.xml (src)

Description: 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.

InValidBaseURI

File: smlif_lc\InValidBaseURI.xml (src)

Description: This test verifies that the code returns an error when the base URI is not an absolute URI

InValidBaseURIHasFragmentComp

File: smlif_lc\InValidBaseURIHasFragmentComp.xml (src)

Description: This test verifies that the code returns an error when the base URI contains a fragment component.

InvalidDataContentBase64

File: smlif_lc\InvalidDataContentBase64.xml (src)

Description: 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.

InValidDuplicateAliases

File: smlif_lc\InValidDuplicateAliases.xml (src)

Description: This test verifies that the code returns an error when two aliases resolve to the same URI

InValidMissingBaseURIAttr1

File: smlif_lc\InValidMissingBaseURIAttr.xml (src)

Description: This test verifies that the code returns an error when there is relative reference in a document and the baseURI is not defined.

InvalidMultipleDocument

File: smlif_lc\InValidMultipleDocument.xml (src)

Description: This test verifies that the code returns an error if the data element contains more than one document.

ValidateDefaultSchemaBinding

File: smlif_lc\ValidateDefaultSchemaBinding.xml (src)

Description: 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.

ValidateNoSchemaBinding

File: smlif_lc\ValidateNoSchemaBinding.xml (src)

Description: 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

ValidateSchemaBinding

File: smlif_lc\ValidateSchemaBinding.xml (src)

Description: 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 )

ValidateSchemaBinding

File: smlif_lc\ValidateSchemaBinding1.xml (src)

Description: 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 )

ValidateSchemaBinding

File: smlif_lc\ValidateSchemaBinding2.xml (src)

Description: 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 )

ValidateSchemaBinding

File: smlif_lc\ValidateSchemaBinding3.xml (src)

Description: 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 )

ValidBase64Content

File: smlif_lc\ValidBase64Content.xml (src)

Description: This test verifies that the code returns success when a document that is a child of the base64Data element is encoded in Base64 format.

ValidEmptyDocument

File: smlif_lc\ValidEmptyDocument.xml (src)

Description: This test verifies that it is valid to have an empty document.

ValidMissingBaseURIAttr1

File: smlif_lc\ValidMissingBaseURIAttr1.xml (src)

Description: This test verifies that it is valid to not define the baseURI when there is no relative URI defined within any document.

ValidMissingBaseURIAttr2

File: smlif_lc\ValidMissingBaseURIAttr2.xml (src)

Description: This test verifies that it is valid to have no baseURI, no aliases and a relative reference in a document, if the reference contains only a fragment component. In which case the reference points to an element within the same document.

Target Element Tests

Tests that ensure correct implementation of targetElement

InValidTargetElement

File: targetElement\InValid.xml (src)

Description: 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.

InValidDerivationByRestriction

File: targetElement\InValidDerivationByRestriction.xml (src)

Description: 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.

InValidSameNameElements

File: targetElement\InValidSameNameElements.xml (src)

Description: 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}.

ValidateTargetElementExists2

File: targetElement\InvalidValue.xml (src)

Description: 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)

InValidTargetElementWithSubstitutionGroup

File: targetElement\InValidWithSubstitutionGroup.xml (src)

Description: 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.

ValidTargetElement

File: targetElement\Valid.xml (src)

Description: 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.

ValidateTargetElementDefinition

File: targetElement\ValidateTargetElementDefinition.xml (src)

Description: This test returns a warning if the sml:targetElement attribute is defined on a type definition.

ValidDerivationByRestriction

File: targetElement\ValidDerivationByRestriction.xml (src)

Description: 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.

ValidSameNameElements

File: targetElement\ValidSameNameElements.xml (src)

Description: 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}.

ValidTargetElementWithSubstitutionGroup

File: targetElement\ValidWithSubstitutionGroup.xml (src)

Description: 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

Target Required Tests

Tests that ensure correct validation of sml:targetRequired attribute

ValidTargetElement

File: targetRequired\InValid.xml (src)

Description: 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.

InValidDerivationByRestriction

File: targetRequired\InValidDerivationByRestriction.xml (src)

Description: 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.

InValidSameNameElements

File: targetRequired\InValidSameNameElements.xml (src)

Description: 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}.

ValidTargetType

File: targetRequired\InValidType.xml (src)

Description: 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

ValidTargetElementWithSubstitutionGroup

File: targetRequired\InValidWithSubstitutionGroup.xml (src)

Description: 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

ValidTargetElement

File: targetRequired\valid.xml (src)

Description: 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.

ValidateTargetRequireDefinition

File: targetRequired\ValidateTargetRequiredDefinition.xml (src)

Description: This test returns a warning if the sml:targetRequired attribute is defined on a type definition.

ValidDerivationByRestriction

File: targetRequired\ValidDerivationByRestriction.xml (src)

Description: 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.

ValidTargetElement

File: targetRequired\ValidFalseRequire.xml (src)

Description: 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.

ValidSameNameElements

File: targetRequired\ValidSameNameElements.xml (src)

Description: 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}.

ValidTargetType

File: targetRequired\ValidType.xml (src)

Description: 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

ValidTargetType

File: targetRequired\ValidTypeFalse.xml (src)

Description: 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

ValidTargetElementWithSubstitutionGroup

File: targetRequired\ValidWithSubstitutionGroup.xml (src)

Description: 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

ValidTargetElementWithSubstitutionGroup

File: targetRequired\ValidWithSubstitutionGroupFalseRequire.xml (src)

Description: 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

Target Type Tests

Tests that ensure correct validation of targetType

InValidTargetType

File: targetType\InValid.xml (src)

Description: 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

InValidDerivationByRestriction

File: targetType\InValidDerivationByRestriction.xml (src)

Description: 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.

InValidSameNameElements

File: targetType\InValidSameNameElements.xml (src)

Description: 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}.

ValidateTargetTypeExists1

File: targetType\InValidValue.xml (src)

Description: 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)

InValidTargetTypeWithSubstitutionGroup

File: targetType\InValidWithSubstitutionGroup.xml (src)

Description: 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.

ValidTargetType

File: targetType\Valid.xml (src)

Description: 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

ValidateTargetTypeDefinition

File: targetType\ValidateTargetTypeDefinition.xml (src)

Description: This test returns a warning if the sml:targetType attribute is defined on a type definition.

ValidDerivationByRestriction

File: targetType\ValidDerivationByRestriction.xml (src)

Description: 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.

ValidSameNameElements

File: targetType\ValidSameNameElements.xml (src)

Description: 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}.

ValidTargetTypeWithSubstitutionGroup

File: targetType\ValidWithSubstitutionGroup.xml (src)

Description: 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.