Input: [Primary Feature Tested] Base64 Valid [Microsoft Result] Valid Valid Base64EncodedSchemaAndDoc (row 22) base64\Base64EncodedSchemaAndDoc.xml Revision 1.5 CVS Log [Test Case Description] Taken from ValidCycles1.xml. Encoded data in both definition and instance sections. 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 [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] Base64 Valid [Microsoft Result] Valid Valid Base64EncodedSchemaAndDocs (row 23) base64\Base64EncodedSchemaAndDocs.xml Revision 1.4 CVS Log [Test Case Description] Taken from acylic test suite. (ValidCycles1.xml) Encoded data in both definition and instance sections. 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 [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] Base64 Invalid [Microsoft Result] Invalid Invalid Base64InvalidEncoding (row 24) base64\Base64InvalidEncoding.xml Revision 1.5 CVS Log [Test Case Description] Taken from acylic test suite. (ValidCycles1.xml) Schema is encoded. Encoded data in both definition and instance sections. 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 [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] Base64 Invalid [Microsoft Result] Invalid Invalid Base64InvalidSML (row 25) base64\Base64InvalidSML.xml Revision 1.5 CVS Log [Test Case Description] All instance documents in this SML-IF are base64-encoded. The instance documents have a cycle for an acyclic type. The SML-IF should be validated to false. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Invalid [Microsoft Result] Invalid Invalid SingleRef (row 26) deref\InValidUnrecognizedScheme.xml Revision 1.3 CVS Log [Test Case Description] Verify a schematron test using a deref function to resolve an unrecognized reference scheme will fail [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Invalid [Microsoft Result] Invalid Invalid InvalidSchemeDerefUsed (row 27) deref\InValidUsageWithScheme.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if an smlxpath1 scheme contains a deref() in the evaluator. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid MultipleDeref (row 28) deref\Multiple.xml Revision 1.12 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid SingleRef (row 30) deref\Single.xml Revision 1.11 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Invalid [Microsoft Result] Invalid Invalid InvalidConstraintSubstitution (row 32) identity\InValidConstraintGroup.xml Revision 1.3 CVS Log [Test Case 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 MUST have the same set of {SML identity-constraints definitions}. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Invalid [Microsoft Result] Invalid Invalid InvalidConstraintRefAttributes (row 33) identity\InValidConstraintRefAttributes.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if an identity constraint includes both the 'ref' and 'name' attribute [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Invalid [Microsoft Result] Invalid Invalid InvalidConstraintRefElements (row 34) identity\InValidConstraintRefElements.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if the sml:field or sml:selector child elements are specified for a referenced identity constraint. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Invalid [Microsoft Result] Invalid Invalid InvalidConstraintRefKey (row 35) identity\InValidConstraintRefKey.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if a referenced identity constraint type does not match to what it's resolved to. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Invalid [Microsoft Result] Invalid Invalid InvalidConstraintRefNoKey (row 36) identity\InValidConstraintRefNoKey.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if a referenced identity constraint cannot be resolved [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Invalid [Microsoft Result] Invalid Invalid InvalidConstraintSubstitution (row 37) identity\InValidConstraintSubstitution.xml Revision 1.2 CVS Log [Test Case Description] 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. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Invalid [Microsoft Result] Invalid Invalid InvalidDuplicateConstraintSubst (row 38) identity\InValidDuplicateConstraintNameSubst.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if two constraint names indirectly declared through substitution group have the same name [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Invalid [Microsoft Result] Invalid Invalid InvalidDuplicateConstraintName1 (row 39) identity\InValidDuplicateKeyConstraintName.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if two constraint names under the same element have the same name [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Invalid [Microsoft Result] Invalid Invalid InValidKeyDuplicate (row 40) identity\InValidKeyDuplicate.xml Revision 1.12 CVS Log [Test Case Description] Verify that a model with a key constraint is invalid if the field values are not unique. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Invalid [Microsoft Result] Invalid Invalid InValidKeyMissing (row 41) identity\InValidKeyMissing.xml Revision 1.12 CVS Log [Test Case Description] Verify that a model with a key constraint is invalid if some field values are missing. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Invalid [Microsoft Result] Invalid Invalid InvalidConstraintSubstitution (row 42) identity\InValidUnionConstraintWithSubstitution.xml Revision 1.3 CVS Log [Test Case Description] 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. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Invalid [Microsoft Result] Invalid Invalid InValidUnique (row 43) identity\InValidUnique.xml Revision 1.12 CVS Log [Test Case Description] Verify that a model with a unique constraint is invalid if the field values are not unique. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Invalid [Microsoft Result] Invalid Invalid ValidConstraintRefKeyref (row 44) identity\ValidConstraintRefKeyref.xml Revision 1.4 CVS Log [Test Case Description] A model is valid if a referenced identity constraint is used using the 'ref' attribute [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Valid [Microsoft Result] Valid Valid ValidKeyref (row 45) identity\ValidKeyref.xml Revision 1.13 CVS Log [Test Case Description] Verify keyref constraint. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Valid [Microsoft Result] Valid Valid ValidKeyUnique (row 46) identity\ValidKeyUnique.xml Revision 1.12 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Valid [Microsoft Result] Valid Valid ValidKeyUniqueInScopeOnly (row 47) identity\ValidKeyUniqueInScopeOnly.xml Revision 1.12 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] idConstraint Valid [Microsoft Result] Valid Valid InValidKeyDuplicate (row 48) identity\ValidSmlXSKey.xml Revision 1.3 CVS Log [Test Case Description] It is not an error if SML identity constraint and XML identity constraint share the same name. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] locator Valid [Microsoft Result] Valid Valid InValidInCompleteModel (row 49) others\InValid.xml Revision 1.4 CVS Log [Test Case Description] This test verifies that an unresolved locator/documentURI is flagged with a warning. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] aliases Invalid [Microsoft Result] Invalid Invalid InValidAliasValue (row 50) others\InValidAliasValue.xml Revision 1.7 CVS Log [Test Case Description] This test verifies that the code returns an error when an alias contains an invalid value. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] aliases Invalid [Microsoft Result] Invalid Invalid InValidAliasHasFragmentComp (row 51) others\InValidAliasWithFragment.xml Revision 1.8 CVS Log [Test Case Description] This test verifies that the code returns an error when an alias contains a fragment component. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] aliases Invalid [Microsoft Result] Invalid Invalid InValidDuplicateAliases (row 52) others\InValidDuplicateAliases.xml Revision 1.8 CVS Log [Test Case Description] This test verifies that the code returns an error when two aliases resolve to the same URI [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] validation Invalid [Microsoft Result] Invalid Invalid InvalidMultipleDocument (row 53) others\InValidMultipleDocument.xml Revision 1.7 CVS Log [Test Case Description] This test verifies that the code returns an error if the data element contains more than one document. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] locator Valid [Microsoft Result] Valid Valid TestDocumentLocator (row 54) others\remote-document.xml Revision 1.11 CVS Log [Test Case Description] Tests the correct implementation of the locator element [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] rules Invalid [Microsoft Result] Invalid Invalid TestRulesWithMultiplePatterns (row 55) others\rulesWithMultiplePattern.xml Revision 1.11 CVS Log [Test Case Description] Tests that rules that have multiple patterns are handled correctly [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] rules Invalid [Microsoft Result] Invalid Invalid TestMultipleRulesUnderOnePattern (row 56) others\rulesWithMultipleRulesUnderOnePattern.xml Revision 1.11 CVS Log [Test Case Description] Tests that patterns with multiple rules are handled correctly [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] validation Invalid [Microsoft Result] Invalid Invalid TestSchemaValidationFailure (row 57) others\schemaValidationFailure.xml Revision 1.14 CVS Log [Test Case Description] Tests that validation against the schema fails. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] Embedded Valid [Microsoft Result] Valid Valid ValidEmptyDocument (row 58) others\ValidEmptyDocument.xml Revision 1.6 CVS Log [Test Case Description] This test verifies that it is valid to have an empty document. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid UnresolvedRef (row 59) references\DanglingRef.xml Revision 1.12 CVS Log [Test Case Description] A valid model can contain unresolved references [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid IntraDocumentRef (row 60) references\IntraDocumentRef.xml Revision 1.13 CVS Log [Test Case Description] It is valid for a reference to target an element in the same document. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid InvalidBareNameUnresolved (row 61) references\InvalidBareNameDangling.xml Revision 1.2 CVS Log [Test Case Description] This SML-IF contains an SML reference that is a unresolved reference. Bare name is used in this reference. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlifBaseUri Invalid [Microsoft Result] Invalid Invalid InValidBaseURI (row 63) references\InValidBaseURI.xml Revision 1.8 CVS Log [Test Case Description] A model is invalid if base URI is not valid [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlifBaseUri Invalid [Microsoft Result] Invalid Invalid InValidBaseURIRelative (row 64) references\InValidBaseURIRelative.xml Revision 1.3 CVS Log [Test Case Description] A model is invalid if the base URI is not absolute [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlifBaseUri Invalid [Microsoft Result] Invalid Invalid InValidBaseURIHasFragmentComp (row 65) references\InValidBaseURIWithFragment.xml Revision 1.3 CVS Log [Test Case Description] A model is invalid if the base URI contains a fragment [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlifBaseUri Invalid [Microsoft Result] Invalid Invalid InValidMissingBaseURIAttr1 (row 68) references\InValidMissingBaseURI.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if a reference is relative and the base URI is missing [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Invalid [Microsoft Result] Invalid Invalid InvalidRefResolvesToMultipleElements (row 69) references\InValidMultipleElements.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if a reference scheme resolves to multiple elements [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Invalid [Microsoft Result] Invalid Invalid InvalidRefResolvesToMultipleElements (row 70) references\InValidMultipleElementsVariation.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if a reference element is identified with sml:ref="1" and its scheme resolves to multiple elements [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Invalid [Microsoft Result] Invalid Invalid SingleRef (row 71) references\InValidNullifiedDeref.xml Revision 1.4 CVS Log [Test Case Description] The deref() function of a nullified reference should not return a target even if the ref has a valid sml:uri child element. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Invalid [Microsoft Result] Invalid Invalid InvalidSchemeResultContainsNonElements (row 72) references\InValidSchemeResult.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if a reference using smlxpath1 scheme resolves to anything other than an element set. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Invalid [Microsoft Result] Invalid Invalid InvalidSchemeSyntaxError (row 73) references\InValidSchemeSyntax.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if the content of the smlxpath1 scheme is syntactically incorrect. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] validation Invalid [Microsoft Result] Invalid Invalid InvalidSmlRefValue (row 74) references\InValidSMLRefValue.xml Revision 1.3 CVS Log [Test Case Description] A model is invalid if the value of sml:ref is not valid [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Invalid [Microsoft Result] Invalid Invalid InvalidSchemeNamespaceUnknown (row 75) references\InValidUnknownNamespace.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if a reference using the smlxpath1 scheme uses a prefix without a bound namespace. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] xmlBase Invalid [Microsoft Result] Invalid Invalid InValidXMLBase (row 76) references\InValidXmlBase.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if xml:base is not valid [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] xmlBase Valid [Microsoft Result] Valid Valid InValidXMLBaseRelative (row 77) references\InValidXmlBaseRelative.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if the xml:base is not absolute [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid MultipleRefToAnElement (row 78) references\MultipleRefToAnElement.xml Revision 1.13 CVS Log [Test Case Description] It is valid for an element in a document to be targeted by multiple different references from other documents [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Invalid [Microsoft Result] Invalid Invalid NullRefElement (row 79) references\NullRefElement.xml Revision 1.12 CVS Log [Test Case Description] It is valid for a reference element to be null [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid RefToNonRootElement (row 80) references\RefToNonRootElement.xml Revision 1.14 CVS Log [Test Case Description] It is valid for a reference in a document to target a non-root element in some other document. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid RefToRootElement (row 81) references\RefToRootElement.xml Revision 1.13 CVS Log [Test Case Description] It is valid for a reference in a document to target the root element in some other document. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid ValidBareNameAbsURI (row 82) references\ValidBareName.xml Revision 1.1 CVS Log [Test Case Description] This SML-IF demonstrates the use of bare names in sml:uri references. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid ValidBareNameSameDocRef (row 84) references\ValidBareNameSameDocRef.xml Revision 1.1 CVS Log [Test Case Description] This SML-IF contains an SML URI reference that only contains the fragment component. The fragment component is a bare name. This URI reference will be dereferenced to an element in the same document. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid ValidRefTwoSchemesNilSpecified (row 85) references\ValidDanglingReference.xml Revision 1.3 CVS Log [Test Case Description] A model is valid if it contains a nullified reference with two schemes, one resolving to an element and another unresolved. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid ValidMissingBaseURIAttr2 (row 86) references\ValidFragmentOnlyReference.xml Revision 1.4 CVS Log [Test Case Description] It is valid for a model to contain a reference with only a fragment. In which case, the reference points to a target element in the same document. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid ValidRefNilrefSpecified1 (row 87) references\ValidInconsistentNonReference.xml Revision 1.2 CVS Log [Test Case Description] 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 [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid ValidRefNilrefSpecified1 (row 88) references\ValidInconsistentReference.xml Revision 1.2 CVS Log [Test Case Description] A model is valid if it contains a nullified reference with multiple schemes resolving to two different elements [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid ValidMissingBaseURIAttr1 (row 89) references\ValidMissingBaseURI.xml Revision 1.2 CVS Log [Test Case Description] A model is valid if there are not references and the base URI is missing [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid ValidNilRefDefinition (row 91) references\ValidNilRef.xml Revision 1.2 CVS Log [Test Case Description] A model is valid if sml:nilref is used in conjunction with sml:ref="true" [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid ValidNilRefPSVI (row 92) references\ValidNilRefPSVI.xml Revision 1.4 CVS Log [Test Case Description] A model is valid if sml:nilref is used in conjunction with sml:ref="true", even if the sml:nilref value is defaulted from the schema [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid ValidSchemeNamespaceInherited (row 93) references\ValidReferenceScheme.xml Revision 1.3 CVS Log [Test Case Description] A model is valid when a reference using the smlxpath1 scheme uses a prefix declared in a containing element [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid SingleRef (row 94) references\ValidSMLRefPSVI.xml Revision 1.3 CVS Log [Test Case Description] The deref() function of a nullified reference should not return a target even if the ref has a valid sml:uri child element. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid ValidRefOneSchemeResolvesOtherUnknown (row 95) references\ValidUnknownRefScheme.xml Revision 1.3 CVS Log [Test Case Description] A model is valid if a reference contains two schemes, one resolving to an element and the other being unknown. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] xmlBase Valid [Microsoft Result] Valid Valid ValidXmlBase (row 96) references\ValidXmlBase.xml Revision 1.2 CVS Log [Test Case Description] A valid xml:base should not result in an error. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] xmlBase Valid [Microsoft Result] Valid Valid ValidXmlBaseOnDocumentElement (row 97) references\ValidXmlBaseOnDocumentElement.xml Revision 1.1 CVS Log [Test Case Description] A valid xml:base specified on a 'document' element should not result in an error. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] xmlBase Valid [Microsoft Result] Valid Valid ValidXmlBaseOnInstance (row 98) references\ValidXmlBaseOnInstance.xml Revision 1.2 CVS Log [Test Case Description] A valid xml:base on an instance document should not result in an error. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] xmlBase Valid [Microsoft Result] Valid Valid ValidXmlBaseWinsOverBaseURI (row 99) references\ValidXmlBaseWinsOverBaseURI.xml Revision 1.2 CVS Log [Test Case Description] When both a baseURI and xml:base are specified, xml:base should be used. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] rules Invalid [Microsoft Result] Invalid Invalid InValidSchematronRule (row 100) Rules\InValid.xml Revision 1.14 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] locid Invalid [Microsoft Result] Invalid Invalid InValidSchematronRuleEnglish (row 101) Rules\InvalidLocidEnglish.xml Revision 1.5 CVS Log [Test Case 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. Error message will be taken from the English resource bundle. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] locid Invalid [Microsoft Result] Invalid Invalid InValidSchematronRuleGerman (row 102) Rules\InvalidLocidGerman.xml Revision 1.5 CVS Log [Test Case 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. Error message will be taken from the German resource bundle. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] locid Invalid [Microsoft Result] Invalid Invalid InValidSchematronRuleMissingBundle (row 103) Rules\InvalidLocidMissingBundle.xml Revision 1.5 CVS Log [Test Case 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. 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). [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] locid Invalid [Microsoft Result] Invalid Invalid InValidSchematronRuleMissingBundlePackage (row 104) Rules\InvalidLocidMissingBundlePackage.xml Revision 1.5 CVS Log [Test Case 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. 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). [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] locid Invalid [Microsoft Result] Invalid Invalid InValidSchematronRuleMissingKey (row 105) Rules\InvalidLocidMissingKey.xml Revision 1.5 CVS Log [Test Case 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. 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. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] ruleBindings Invalid [Microsoft Result] Invalid Invalid InValidRuleBinding-MultipleRulesSameDocument-BothFail (row 106) Rules\InValidRuleBinding-MultipleRulesSameDocument-BothFail.xml Revision 1.13 CVS Log [Test Case Description] Two rules are bound to the same document - both fail. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] ruleBindings Invalid [Microsoft Result] Invalid Invalid InValidRuleBinding-MultipleRulesSameDocument (row 107) Rules\InValidRuleBinding-MultipleRulesSameDocument.xml Revision 1.12 CVS Log [Test Case Description] Two rules are bound to the same document. One passes, one fails. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] ruleBindings Invalid [Microsoft Result] Invalid Invalid InValidRuleBinding (row 108) Rules\InValidRuleBinding.xml Revision 1.12 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] ruleBindings Invalid [Microsoft Result] Invalid Invalid InValidRuleBindingWithBaseURI (row 109) Rules\InValidRuleBindingWithBaseURI.xml Revision 1.2 CVS Log [Test Case 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. This example binds an instance document with a rule binding using the base URI. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] ruleBindings Invalid [Microsoft Result] Invalid Invalid InValidRuleBindingWithPrefix (row 110) Rules\InValidRuleBindingWithPrefix.xml Revision 1.1 CVS Log [Test Case 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. This example binds an instance document based on the prefix of document aliases [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] rules Invalid [Microsoft Result] Invalid Invalid InValidRuleType (row 111) Rules\InValidRuleType.xml Revision 1.9 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] rules Invalid [Microsoft Result] Invalid Invalid InValidRuleTypeExtension (row 112) Rules\InValidRuleTypeExtension.xml Revision 1.9 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] rules Invalid [Microsoft Result] Invalid Invalid InValidRuleTypeRestriction (row 113) Rules\InValidRuleTypeRestriction.xml Revision 1.9 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] rules Invalid [Microsoft Result] Invalid Invalid ValidSchematronRule (row 114) Rules\Valid.xml Revision 1.14 CVS Log [Test Case Description] A model with a Schematron rule defined for an element is valid if all instances of the element satisfy the rule. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] validation Valid [Microsoft Result] Valid Valid ValidXMLSchema (row 115) Rules\ValidNoSML.xml Revision 1.10 CVS Log [Test Case Description] Basic XML Schema file, no SML extensions used. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] ruleBindings Valid [Microsoft Result] Valid Valid ValidRuleBinding (row 116) Rules\ValidRuleBinding.xml Revision 1.13 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetElement Invalid [Microsoft Result] Invalid Invalid InvalidTargetElement (row 117) targetElement\InValid.xml Revision 1.13 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetElement Invalid [Microsoft Result] Invalid Invalid InValidDerivationByRestriction (row 118) targetElement\InValidDerivationByRestriction.xml Revision 1.9 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetElement Invalid [Microsoft Result] Invalid Invalid InValidSameNameElements (row 119) targetElement\InValidSameNameElements.xml Revision 1.9 CVS Log [Test Case 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}. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetElement Invalid [Microsoft Result] Invalid Invalid ValidateTargetElementExists2 (row 120) targetElement\InvalidValue.xml Revision 1.5 CVS Log [Test Case 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) [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetElement Invalid [Microsoft Result] Invalid Invalid InvalidTargetElementWithSubstitutionGroup (row 121) targetElement\InValidWithSubstitutionGroup.xml Revision 1.13 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetElement Valid [Microsoft Result] Valid Valid ValidTargetElement (row 122) targetElement\Valid.xml Revision 1.13 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetElement Valid [Microsoft Result] Valid Valid ValidDerivationByRestriction (row 123) targetElement\ValidDerivationByRestriction.xml Revision 1.6 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetElement Valid [Microsoft Result] Valid Valid ValidSameNameElements (row 124) targetElement\ValidSameNameElements.xml Revision 1.6 CVS Log [Test Case 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}. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetElement Valid [Microsoft Result] Valid Valid ValidTargetElementWithSubstitutionGroup (row 125) targetElement\ValidWithSubstitutionGroup.xml Revision 1.13 CVS Log [Test Case 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 [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetRequired Invalid [Microsoft Result] Invalid Invalid InvalidTargetRequired (row 126) targetRequired\InValid.xml Revision 1.11 CVS Log [Test Case Description] If targetElement=GTE for a global element declaration E, and targetRequired=true, an instance of the SML reference cannot contain an unresolved reference which does not target any element in the model. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetRequired Invalid [Microsoft Result] Invalid Invalid InvalidTargetRequiredMissingReference (row 127) targetRequired\InvalidMissingReference.xml Revision 1.1 CVS Log [Test Case Description] If targetElement=GTE for a global element declaration E, and targetRequired=true, an instance of the SML reference must exist. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetRequired Invalid [Microsoft Result] Invalid Invalid InvalidTargetRequiredNullReference (row 128) targetRequired\InvalidNullReference.xml Revision 1.1 CVS Log [Test Case Description] If targetElement=GTE for a global element declaration E, and targetRequired=true, an instance of the SML reference cannot be null. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetRequired Invalid [Microsoft Result] Invalid Invalid InValidSameNameElements (row 129) targetRequired\InValidSameNameElements.xml Revision 1.9 CVS Log [Test Case 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}. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetRequired Valid [Microsoft Result] Valid Valid ValidTargetRequired (row 130) targetRequired\valid.xml Revision 1.11 CVS Log [Test Case Description] Tests for correct usage of targetRequired. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetRequired Valid [Microsoft Result] Valid Valid ValidTargetRequiredFalse (row 131) targetRequired\ValidFalseRequire.xml Revision 1.11 CVS Log [Test Case 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. targetRequired=false. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetRequired Valid [Microsoft Result] Valid Valid ValidTargetRequiredSameNameElements (row 132) targetRequired\ValidSameNameElements.xml Revision 1.7 CVS Log [Test Case 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}. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetRequired Valid [Microsoft Result] Valid Valid ValidTargetRequiredWithTargetType (row 133) targetRequired\ValidType.xml Revision 1.12 CVS Log [Test Case 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. Includes targetRequired=true. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetRequired Valid [Microsoft Result] Valid Valid ValidTargetRequiredFalseWithTargetType (row 134) targetRequired\ValidTypeFalse.xml Revision 1.11 CVS Log [Test Case 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. Includes targetRequired=false. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetType Invalid [Microsoft Result] Invalid Invalid InvalidTargetType (row 135) targetType\InValid.xml Revision 1.13 CVS Log [Test Case Description] If targetType='T' 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 T [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetType Invalid [Microsoft Result] Invalid Invalid InValidDerivationByRestriction (row 136) targetType\InValidDerivationByRestriction.xml Revision 1.8 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetType Invalid [Microsoft Result] Invalid Invalid InValidSameNameElements (row 137) targetType\InValidSameNameElements.xml Revision 1.7 CVS Log [Test Case 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}. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetType Invalid [Microsoft Result] Invalid Invalid ValidateTargetTypeExists1 (row 138) targetType\InValidValue.xml Revision 1.7 CVS Log [Test Case 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) [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetType Invalid [Microsoft Result] Invalid Invalid InValidTargetTypeWithSubstitutionGroup (row 139) targetType\InValidWithSubstitutionGroup.xml Revision 1.12 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetType Valid [Microsoft Result] Valid Valid ValidTargetType (row 140) targetType\Valid.xml Revision 1.12 CVS Log [Test Case Description] If targetType='T' 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 T or a derived type of T [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetType Valid [Microsoft Result] Valid Valid ValidDerivationByRestriction (row 141) targetType\ValidDerivationByRestriction.xml Revision 1.7 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetType Valid [Microsoft Result] Valid Valid ValidSameNameElements (row 142) targetType\ValidSameNameElements.xml Revision 1.7 CVS Log [Test Case 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}. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetType Valid [Microsoft Result] Valid Valid ValidTargetTypeWithSubstitutionGroup (row 143) targetType\ValidWithSubstitutionGroup.xml Revision 1.11 CVS Log [Test Case 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. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Invalid [Microsoft Result] Invalid Invalid InvalidWrongSMLNSURI.xml (row 144) InvalidWrongSMLNSURI.xml No CVS revision information was found for this file [Test Case Description] SML prefix bound to wrong namespace URI [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetRequired Invalid [Microsoft Result] Invalid Invalid TargetRequiredInValidDerivationByRestriction.xml (row 145) TargetRequiredInValidDerivationByRestriction.xml No CVS revision information was found for this file [Test Case 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. Copied from /org.eclipse.cosmos.rm.validation.tests/src/test-resources/targetElement/InValidDerivationByRestriction.xml and changed to work with target required instead [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetRequired Valid [Microsoft Result] Valid Valid TargetRequiredValidDerivationByRestriction.xml (row 146) TargetRequiredValidDerivationByRestriction.xml No CVS revision information was found for this file [Test Case 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. Copied from /org.eclipse.cosmos.rm.validation.tests/src/test-resources/targetElement/ValidDerivationByRestriction.xml and changed to work with target required instead 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. Copied from /org.eclipse.cosmos.rm.validation.tests/src/test-resources/targetElement/InValidDerivationByRestriction.xml and changed to work with target required instead [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetRequired Invalid [Microsoft Result] Invalid Invalid TargetRequiredInValidWithSubstitutionGroup.xml (row 147) TargetRequiredInValidWithSubstitutionGroup.xml No CVS revision information was found for this file [Test Case 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. Copied from /org.eclipse.cosmos.rm.validation.tests/src/test-resources/targetElement/InValidDerivationByRestriction.xml and changed to work with target required instead [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] targetRequired Valid [Microsoft Result] Valid Valid TargetRequiredValidWithSubstitutionGroup.xml (row 148) TargetRequiredValidWithSubstitutionGroup.xml No CVS revision information was found for this file [Test Case 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. Copied from /org.eclipse.cosmos.rm.validation.tests/src/test-resources/targetElement/ValidDerivationByRestriction.xml and changed to work with target required instead 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. Copied from /org.eclipse.cosmos.rm.validation.tests/src/test-resources/targetElement/InValidDerivationByRestriction.xml and changed to work with target required instead [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] acyclic Invalid [Microsoft Result] Invalid Invalid AcyclicInValidCycleSameDoc.xml (row 149) AcyclicInValidCycleSameDoc.xml No CVS revision information was found for this file [Test Case Description] A model is invalid if an instance of an acyclic type CT references itself, even w/in the same document [Eclipse COSMOS Result]

Output: Invalid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] acyclic Valid [Microsoft Result] Valid Valid AcyclicValidCycleSameDoc.xml (row 150) AcyclicValidCycleSameDoc.xml No CVS revision information was found for this file [Test Case Description] Let R1 be a reference type with sml:acyclic=᾿false᾿. Then a model is valid if it has same-document cycles using instances of R1 [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] dtdID Valid [Microsoft Result] Invalid Invalid ValidBareNameDTDDeterminedIDBareName.xml (row 151) ValidBareNameDTDDeterminedIDBareName.xml No CVS revision information was found for this file [Test Case Description] This SML-IF demonstrates the use of bare names in sml:uri references. Copied from ValidBareName and converted from schema- to DTD-determined ID. [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Primary Feature Tested] smlref Valid [Microsoft Result] Valid Valid ValidKeyUniqueDeref.xml (row 152) ValidKeyUniqueDeref.xml No CVS revision information was found for this file [Test Case 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. Copy and tweak based on /org.eclipse.cosmos.rm.validation.tests/src/test-resources/identity/ValidKeyUnique.xml [Eclipse COSMOS Result]

Output: Valid

W3C SML Working Group Implementation Results by Test Case


Input: [Name] type [Required] false [Attribute Constraints] Must not occur with the 'typeexpr' attribute. [Type] URI [Valid Values] http://www.w3.org/TR/scxml/, http://www.w3.org/TR/ccxml/, http://www.w3.org/TR/voicexml30/, http://www.w3.org/TR/voicexml21/ plus other platform-specific values. [Description] A URI specifying the type of the external service. See below for details. [Default Value]

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] typeexpr [Required] false [Attribute Constraints] Must not occur with the 'type' attribute. [Type] value expression [Valid Values] Any value expression that evaluates to a URI that would be a valid value for 'type'. [Description] A dynamic alternative to 'type'. If this attribute is present, the SCXML Processor MUST evaluate it when the parent element is evaluated and treat the result as if it had been entered as the value of 'type'. [Default Value]

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] src [Required] false [Attribute Constraints] Must not occur with the 'srcexpr' attribute or the element. [Type] URI [Valid Values] Any URI. [Description] A URI to be passed to the external service. See below for details. [Default Value]

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] srcexpr [Required] false [Attribute Constraints] Must not occur with the 'src' attribute or the element. [Type] Value expression [Valid Values] Any expression evaluating to a valid URI. [Description] A dynamic alternative to 'src'. If this attribute is present, the SCXML Processor MUST evaluate it when the parent element is evaluated and treat the result as if it had been entered as the value of 'src'. [Default Value]

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] id [Required] false [Attribute Constraints] Must not occur with the 'idlocation' attribute. [Type] ID [Valid Values] Any valid token [Description] A string literal to be used as the identifier for this instance of . See 3.14 IDs for details. [Default Value]

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] idlocation [Required] false [Attribute Constraints] Must not occur with the 'id' attribute. [Type] Location expression [Valid Values] Any valid location expression [Description] Any data model expression evaluating to a data model location. See 5.9.2 Location Expressions for details. [Default Value]

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] namelist [Required] false [Attribute Constraints] Must not occur with the element. [Type] List of location expressions [Valid Values] List of data model locations [Description] A space-separated list of one or more data model locations to be included as attribute/value pairs with the message. (The name of the location is the attribute and the value stored at the location is the value.) See 6.4.4 Data Sharing and 5.9.2 Location Expressions for details. [Default Value]

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] autoforward [Required] false [Type] boolean [Valid Values] true or false [Description] A flag indicating whether to forward events to the invoked process. See below for details. [Default Value]

Output: false

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Event Name] dragstart [Cancelable?] ✓ Cancelable [Drag data store mode] Read/write mode [dropEffect] "none" [Default Action] Initiate the drag-and-drop operation [Target]

Output: Source node

7.7 Drag and drop — HTML5: Edition for Web Authors


Input: [Event Name] drag [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] "none" [Default Action] Continue the drag-and-drop operation [Target]

Output: Source node

7.7 Drag and drop — HTML5: Edition for Web Authors


Input: [Event Name] dragenter [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] Based on effectAllowed value [Default Action] Reject immediate user selection as potential target element [Target]

Output: Immediate user selection or the body element

7.7 Drag and drop — HTML5: Edition for Web Authors


Input: [Event Name] dragleave [Cancelable?] — [Drag data store mode] Protected mode [dropEffect] "none" [Default Action] None [Target]

Output: Previous target element

7.7 Drag and drop — HTML5: Edition for Web Authors


Input: [Event Name] dragover [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] Based on effectAllowed value [Default Action] Reset the current drag operation to "none" [Target]

Output: Current target element

7.7 Drag and drop — HTML5: Edition for Web Authors


Input: [Event Name] drop [Cancelable?] ✓ Cancelable [Drag data store mode] Read-only mode [dropEffect] Current drag operation [Default Action] Varies [Target]

Output: Current target element

7.7 Drag and drop — HTML5: Edition for Web Authors


Input: [Event Name] dragend [Cancelable?] — [Drag data store mode] Protected mode [dropEffect] Current drag operation [Default Action] Varies [Target]

Output: Source node

7.7 Drag and drop — HTML5: Edition for Web Authors


Input: [Description] The ability of users to obtain and correct information that an entity has collected about them [Applies to] proposal or statement [Required in Every Proposal] yes [Default Type of Label] URI or text string [May be Defined in Vocabulary] yes [Clause]

Output: Access


Input: [Description] The entity who the user is entering into an agreement with [Applies to] proposal or statement [Required in Every Proposal] yes [Default Type of Label] certificate, URI, or text string [May be Defined in Vocabulary] yes [Clause]

Output: Agreement With


Input: [Description] The impact on the user of reaching an agreement [Applies to] proposal or statement [Required in Every Proposal] yes [Default Type of Label] URI or text string [May be Defined in Vocabulary] yes [Clause]

Output: Consequence


Input: [Description] Information for contacting a service with inquiries about the services privacy practices. [Applies to] proposal or statement [Required in Every Proposal] yes [Default Type of Label] URI or text string [May be Defined in Vocabulary] yes [Clause]

Output: Contact


Input: [Description] The space where a particular statement is valid [Applies to] proposal or statement [Required in Every Proposal] yes [Default Type of Label] set of URIs [May be Defined in Vocabulary] no [Clause]

Output: Experience Space


Input: [Description] What a service will do with data [Applies to] statement [Required in Every Proposal] yes [Default Type of Label] none [May be Defined in Vocabulary] yes [Clause]

Output: Practice


Input: [Description] The data a service proposes to collect or requests [Applies to] statement [Required in Every Proposal] yes [Default Type of Label] see definition below [May be Defined in Vocabulary] no, but qualifier and category components may be [Clause]

Output: Qualified Data Set


Input: [Description] Used by the creator of a vocabulary to provide extra functionality beyond that in the base P3 Proposal Grammar [Applies to] proposal, statement, or clause [Required in Every Proposal] no [Default Type of Label] none [May be Defined in Vocabulary] yes [Clause]

Output: Qualifier


Input: [Description] A binary value indicating whether a particular practice, qualified data set, or statement is required in an agreement [Applies to] practice clause, qualified data set clause, or statement [Required in Every Proposal] no (defaults to 1 when not present) [Default Type of Label] 0 or 1 [May be Defined in Vocabulary] no [Clause]

Output: Required


Input: [Description] A URI that identifies a particular P3 proposal vocabulary [Applies to] proposal [Required in Every Proposal] yes [Default Type of Label] URI [May be Defined in Vocabulary] no [Clause]

Output: Schema


Input: [Description] Signature and attribution information as defined by the Digital Signature effort [Applies to] Proposal or statement [Required in Every Proposal] no [Default Type of Label] none [May be Defined in Vocabulary] yes [Clause]

Output: Signature


Input: [Additive?] yes ['animate'] yes ['animate Color'] yes ['animate Transform'] no [Notes] Only RGB color values are additive. ['set']

Output: yes


Input: [Additive?] yes ['animate'] yes ['animate Color'] no ['animate Transform'] no ['set']

Output: yes


Input: [Additive?] no ['animate'] yes ['animate Color'] no ['animate Transform'] no ['set']

Output: yes


Input: [Additive?] no ['animate'] no ['animate Color'] no ['animate Transform'] no ['set']

Output: no


Input: [Additive?] yes ['animate'] no ['animate Color'] no ['animate Transform'] yes [Notes] Additive means that a transformation is post-multiplied to the base set of transformations. ['set']

Output: no


Input: [Data type] All other data types used in animatable attributes and properties [Additive?] no ['animate'] yes ['animate Color'] no ['animate Transform'] no ['set']

Output: yes


Input: [Module] Skeleton [Term Name] FeatureOfInterest [Type] class [Definition]

Output: A feature is an abstraction of real world phenomena (thing, person, event, etc).


Input: [Module] Skeleton [Term Name] Observation [Type] class [Definition]

Output: An Observation is a Situation in which a Sensing method has been used to estimate or calculate a value of a Property of a FeatureOfInterest. Links to Sensing and Sensor describe what made the Observation and how; links to Property and Feature detail what was sensed; the result is the output of a Sensor; other metadata details times etc.


Input: [Module] Skeleton [Term Name] Property [Type] class [Definition]

Output: An observable Quality of an Event or Object. That is, not a quality of an abstract entity as is also allowed by DUL's Quality, but rather an aspect of an entity that is intrinsic to and cannot exist without the entity and is observable by a sensor.


Input: [Module] Skeleton [Term Name] Sensing [Type] class [Definition]

Output: Sensing is a process that results in the estimation, or calculation, of the value of a phenomenon.


Input: [Module] Skeleton [Term Name] Sensor [Type] class [Definition]

Output: A sensor can do (implements) sensing: that is, a sensor is any entity that can follow a sensing method and thus observe some Property of a FeatureOfInterest. Sensors may be physical devices, computational methods, a laboratory setup with a person following a method, or any other thing that can follow a Sensing Method to observe a Property.


Input: [Module] Skeleton [Term Name] SensorInput [Type] class [Definition]

Output: An Event in the real world that 'triggers' the sensor. The properties associated to the stimulus may be different to eventual observed property. It is the event, not the object that triggers the sensor.


Input: [Module] Skeleton [Term Name] SensorOutput [Type] class [Definition]

Output: A sensor outputs a piece of information (an observed value), the value itself being represented by an ObservationValue.


Input: [Module] Skeleton [Term Name] Stimulus [Type] class [Definition]

Output: An Event in the real world that 'triggers' the sensor. The properties associated to the stimulus may be different to eventual observed property. It is the event, not the object that triggers the sensor.


Input: [Module] Skeleton [Term Name] detects [Type] property [Definition]

Output: A relation from a sensor to the Stimulus that the sensor can detect. The Stimulus itself will be serving as a proxy for (see isProxyOf) some observable property.


Input: [Module] Skeleton [Term Name] featureOfInterest [Type] property [Definition]

Output: A relation between an observation and the entity whose quality was observed. For example, in an observation of the weight of a person, the feature of interest is the person and the quality is weight.


Input: [Module] Skeleton [Term Name] forProperty [Type] property [Definition]

Output: A relation between some aspect of a sensing entity and a property. For example, from a sensor to the properties it can observe, or from a deployment to the properties it was installed to observe. Also from a measurement capability to the property the capability is described for. (Used in conjunction with ofFeature).


Input: [Module] Skeleton [Term Name] hasProperty [Type] property [Definition]

Output: A relation between a FeatureOfInterest and a Property of that feature.


Input: [Module] Skeleton [Term Name] implementedBy [Type] property [Definition]

Output: A relation between the description of an algorithm, procedure or method and an entity that implements that method in some executable way. For example, between a scientific measuring method and a sensor the senses via that method.


Input: [Module] Skeleton [Term Name] implements [Type] property [Definition]

Output: A relation between an entity that implements a method in some executable way and the description of an algorithm, procedure or method. For example, between a Sensor and the scientific measuring method that the Sensor uses to observe a Property.


Input: [Module] Skeleton [Term Name] isPropertyOf [Type] property [Definition]

Output: Relation between a FeatureOfInterest and a Property (a Quality observable by a sensor) of that feature.


Input: [Module] Skeleton [Term Name] isProxyFor [Type] property [Definition]

Output: A relation from a Stimulus to the Property that the Stimulus is serving as a proxy for. For example, the expansion of the quicksilver is a stimulus that serves as a proxy for temperature, or an increase or decrease in the spinning of cups on a wind sensor is serving as a proxy for wind speed.


Input: [Module] Skeleton [Term Name] observationResult [Type] property [Definition]

Output: Relation linking an Observation (i.e., a description of the context, the Situation, in which the observatioin was made) and a Result, which contains a value representing the value associated with the observed Property.


Input: [Module] Skeleton [Term Name] observedProperty [Type] property [Definition]

Output: Relation linking an Observation to the Property that was observed. The observedProperty should be a Property (hasProperty) of the FeatureOfInterest (linked by featureOfInterest) of this observation.


Input: [Module] Skeleton [Term Name] ofFeature [Type] property [Definition]

Output: A relation between some aspect of a sensing entity and a feature. For example, from a sensor to the features it can observe properties of, or from a deployment to the features it was installed to observe. Also from a measurement capability to the feature the capability is described for. (Used in conjunction with forProperty).


Input: [Module] Skeleton [Term Name] sensingMethodUsed [Type] property [Definition]

Output: A (measurement) procedure is a detailed description of a measurement according to one or more measurement principles and to a given measurement method, based on a measurement model and including any calculation to obtain a measurement result [VIM 2.6]


Input: [Clause] Access [Description] The ability of users to obtain and correct information that an entity has collected about them [Required in Every Proposal] yes [Default Type of Label] URI or text string [May be Defined in Vocabulary] yes [Applies to]

Output: proposal or statement


Input: [Clause] Agreement With [Description] The entity who the user is entering into an agreement with [Required in Every Proposal] yes [Default Type of Label] certificate, URI, or text string [May be Defined in Vocabulary] yes [Applies to]

Output: proposal or statement


Input: [Clause] Consequence [Description] The impact on the user of reaching an agreement [Required in Every Proposal] yes [Default Type of Label] URI or text string [May be Defined in Vocabulary] yes [Applies to]

Output: proposal or statement


Input: [Clause] Contact [Description] Information for contacting a service with inquiries about the services privacy practices. [Required in Every Proposal] yes [Default Type of Label] URI or text string [May be Defined in Vocabulary] yes [Applies to]

Output: proposal or statement


Input: [Clause] Experience Space [Description] The space where a particular statement is valid [Required in Every Proposal] yes [Default Type of Label] set of URIs [May be Defined in Vocabulary] no [Applies to]

Output: proposal or statement


Input: [Clause] Practice [Description] What a service will do with data [Required in Every Proposal] yes [Default Type of Label] none [May be Defined in Vocabulary] yes [Applies to]

Output: statement


Input: [Clause] Qualified Data Set [Description] The data a service proposes to collect or requests [Required in Every Proposal] yes [Default Type of Label] see definition below [May be Defined in Vocabulary] no, but qualifier and category components may be [Applies to]

Output: statement


Input: [Clause] Qualifier [Description] Used by the creator of a vocabulary to provide extra functionality beyond that in the base P3 Proposal Grammar [Required in Every Proposal] no [Default Type of Label] none [May be Defined in Vocabulary] yes [Applies to]

Output: proposal, statement, or clause


Input: [Clause] Required [Description] A binary value indicating whether a particular practice, qualified data set, or statement is required in an agreement [Required in Every Proposal] no (defaults to 1 when not present) [Default Type of Label] 0 or 1 [May be Defined in Vocabulary] no [Applies to]

Output: practice clause, qualified data set clause, or statement


Input: [Clause] Schema [Description] A URI that identifies a particular P3 proposal vocabulary [Required in Every Proposal] yes [Default Type of Label] URI [May be Defined in Vocabulary] no [Applies to]

Output: proposal


Input: [Clause] Signature [Description] Signature and attribution information as defined by the Digital Signature effort [Required in Every Proposal] no [Default Type of Label] none [May be Defined in Vocabulary] yes [Applies to]

Output: Proposal or statement


Input: [Language feature] address element [Restrictions] If specified, role must be contentinfo [Default implied ARIA semantic]

Output: No role


Input: [Language feature] article element [Restrictions] Role must be either article, document, application, or main [Default implied ARIA semantic]

Output: article role


Input: [Language feature] aside element [Restrictions] Role must be either note, complementary, or search [Default implied ARIA semantic]

Output: note role


Input: [Language feature] audio element [Restrictions] If specified, role must be application [Default implied ARIA semantic]

Output: No role


Input: [Language feature] details element [Restrictions] Role must be a role that supports aria-expanded [Default implied ARIA semantic]

Output: group role


Input: [Language feature] embed element [Restrictions] If specified, role must be either application, document, or img [Default implied ARIA semantic]

Output: No role


Input: [Language feature] footer element [Restrictions] If specified, role must be contentinfo [Default implied ARIA semantic]

Output: No role


Input: [Language feature] header element [Restrictions] If specified, role must be banner [Default implied ARIA semantic]

Output: No role


Input: [Language feature] iframe element [Restrictions] If specified, role must be either application, document, or img [Default implied ARIA semantic]

Output: No role


Input: [Language feature] img element whose alt attribute's value is absent [Restrictions] No restrictions [Default implied ARIA semantic]

Output: img role


Input: [Language feature] input element with a type attribute in the Checkbox state [Restrictions] Role must be either checkbox or menuitemcheckbox [Default implied ARIA semantic]

Output: checkbox role


Input: [Language feature] input element with a type attribute in the Radio Button state [Restrictions] Role must be either radio or menuitemradio [Default implied ARIA semantic]

Output: radio role


Input: [Language feature] li element whose parent is an ol or ul element [Restrictions] Role must be either listitem, menuitemcheckbox, menuitemradio, option, tab, or treeitem [Default implied ARIA semantic]

Output: listitem role


Input: [Language feature] object element [Restrictions] If specified, role must be either application, document, or image [Default implied ARIA semantic]

Output: No role


Input: [Language feature] ol element [Restrictions] Role must be either directory, list, listbox, menu, menubar, tablist, toolbar, tree [Default implied ARIA semantic]

Output: list role


Input: [Language feature] output element [Restrictions] No restrictions [Default implied ARIA semantic]

Output: status role


Input: [Language feature] section element [Restrictions] Role must be either alert, alertdialog, application, contentinfo, dialog, document, log, main, marquee, region, search, or status [Default implied ARIA semantic]

Output: region role


Input: [Language feature] ul element [Restrictions] Role must be either directory, list, listbox, menu, menubar, tablist, toolbar, tree [Default implied ARIA semantic]

Output: list role


Input: [Language feature] video element [Restrictions] If specified, role must be application [Default implied ARIA semantic]

Output: No role


Input: [Language feature] The body element [Restrictions] Role must be either document or application [Default implied ARIA semantic]

Output: document role


Input: [event handler] onpollstart [event name] pollstart [short description] fired when the polling state changes to true [event type]

Output: simple event

Low-level Web NFC API for Trusted Applications


Input: [event handler] onpollstop [event name] pollstop [short description] fired when the polling state changes to false [event type]

Output: simple event

Low-level Web NFC API for Trusted Applications


Input: [event handler] ontagfound [event name] tagfound [short description] detect a new NFCTag [event type]

Output: NFCTagEvent with tag property set to the new NFCTag object.

Low-level Web NFC API for Trusted Applications


Input: [event handler] ontaglost [event name] taglost [short description] fired when the NFCTag detected by the adaptor moves out of range. [event type]

Output: simple event

Low-level Web NFC API for Trusted Applications


Input: [event handler] onpeerfound [event name] peerfound [short description] detect a new NFCPeer [event type]

Output: NFCPeerEvent with peer property set to the new NFCPeer object.

Low-level Web NFC API for Trusted Applications


Input: [event handler] onpeerlost [event name] peerlost [short description] fired when the NFCPeer detected by the adaptor moves out of range. [event type]

Output: simple event

Low-level Web NFC API for Trusted Applications


Input: [Module] Measuring [Term Name] SensingDevice [Type] class [Definition]

Output: A sensing device is a device that implements sensing.


Input: [Module] Measuring [Term Name] SensorDataSheet [Type] class [Definition]

Output: A data sheet records properties of a sensor. A data sheet might describe for example the accuracy in various conditions, the power use, the types of connectors that the sensor has, etc. Generally a sensor's properties are recorded directly (with hasMeasurementCapability, for example), but the data sheet can be used for example to record the manufacturers specifications verses observed capabilites, or if more is known than the manufacturer specifies, etc. The data sheet is an information object about the sensor's properties, rather than a direct link to the actual properties themselves.


Input: [Module] Measuring [Term Name] observes [Type] property [Definition]

Output: Relation between a Sensor and a Property that the sensor can observe. Note that, given the DUL modelling of Qualities, a sensor defined with 'observes only Windspeed' technically links the sensor to particular instances of Windspeed, not to the concept itself - OWL can't express concept-concept relations, only individual-individual. The property composition ensures that if an observation is made of a particular quality then one can infer that the sensor observes that quality.


Input: [Module] MeasuringCapability [Term Name] Accuracy [Type] class [Definition]

Output: The closeness of agreement between the value of an observation and the true value of the observed quality.


Input: [Module] MeasuringCapability [Term Name] DetectionLimit [Type] class [Definition]

Output: An observed value for which the probability of falsely claiming the absence of a component in a material is ÃŽÂ², given a probability ÃŽÂ± of falsely claiming its presence.


Input: [Module] MeasuringCapability [Term Name] Drift [Type] class [Definition]

Output: A, continuous or incremental, change in the reported values of observations over time for an unchanging quality.


Input: [Module] MeasuringCapability [Term Name] Frequency [Type] class [Definition]

Output: The smallest possible time between one observation and the next.


Input: [Module] MeasuringCapability [Term Name] Latency [Type] class [Definition]

Output: The time between a request for an observation and the sensor providing a result.


Input: [Module] MeasuringCapability [Term Name] MeasurementCapability [Type] class [Definition]

Output: Collects together measurement properties (accuracy, range, precision, etc) and the environmental conditions in which those properties hold, representing a specification of a sensor's capability in those conditions. The conditions specified here are those that affect the measurement properties, while those in OperatingRange represent the sensor's standard operating conditions, including conditions that don't affect the observations.


Input: [Module] MeasuringCapability [Term Name] MeasurementProperty [Type] class [Definition]

Output: An identifiable and observable characteristic of a sensor's observations or ability to make observations.


Input: [Module] MeasuringCapability [Term Name] MeasurementRange [Type] class [Definition]

Output: The set of values that the sensor can return as the result of an observation under the defined conditions with the defined measurement properties. (If no conditions are specified or the conditions do not specify a range for the observed qualities, the measurement range is to be taken as the condition for the observed qualities.)


Input: [Module] MeasuringCapability [Term Name] Precision [Type] class [Definition]

Output: The closeness of agreement between replicate observations on an unchanged or similar quality value: i.e., a measure of a sensor's ability to consitently reproduce an observation.


Input: [Module] MeasuringCapability [Term Name] Resolution [Type] class [Definition]

Output: The smallest difference in the value of a quality being observed that would result in perceptably different values of observation results.


Input: [Module] MeasuringCapability [Term Name] ResponseTime [Type] class [Definition]

Output: The time between a (step) change inthe value of an observed quality and a sensor (possibly with specified error) 'settling' on an observed value.


Input: [Module] MeasuringCapability [Term Name] Selectivity [Type] class [Definition]

Output: Selectivity is a property of a sensor whereby it provides observed values for one or more qualities such that the values of each quality are independent of other qualities in the phenomenon, body, or substance being investigated.


Input: [Module] MeasuringCapability [Term Name] Sensitivity [Type] class [Definition]

Output: Sensitivity is the quotient of the change in a result of sensor and the corresponding change in a value of a quality being observed.


Input: [Module] MeasuringCapability [Term Name] hasMeasurementCapability [Type] property [Definition]

Output: Relation from a Sensor to a MeasurementCapability describing the measurement properties of the sensor.


Input: [Module] MeasuringCapability [Term Name] hasMeasurementProperty [Type] property [Definition]

Output: Relation from a MeasurementCapability to a MeasurementProperty. For example, to an accuracy (see notes at MeasurementCapability).


Input: [Component] FTCaseOption [Default initial value] case insensitive overwriteable by prolog [Scope] lexical [Consistency rules] Value must be case insensitive, case sensitive, lowercase, or uppercase.

Output: overwriteable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] FTDiacriticsOption [Default initial value] diacritics insensitive overwriteable by prolog [Scope] lexical [Consistency rules] Value must be diacritics insensitive or diacritics sensitive.

Output: overwriteable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] FTStemOption [Default initial value] no stemming overwriteable by prolog [Scope] lexical [Consistency rules] Value must be stemming or no stemming.

Output: overwriteable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] FTThesaurusOption [Default initial value] no thesaurus overwriteable by prolog (refer to default to augment) [Scope] lexical [Consistency rules] Each URI in the value must be found in the statically known thesauri.

Output: overwriteable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] Statically known thesauri [Default initial value] none cannot be augmented or overwritten by prolog [Scope] module [Consistency rules] Each URI uniquely identifies a thesaurus list.

Output: augmentable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] FTStopWordOption [Default initial value] no stop words overwriteable by prolog (refer to default to augment) [Scope] lexical [Consistency rules] Each URI in the value must be found in the statically known stop word lists.

Output: overwriteable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] Statically known stop word lists [Default initial value] none cannot be augmented or overwritten by prolog [Scope] module [Consistency rules] Each URI uniquely identifies a stop word list.

Output: augmentable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] FTLanguageOption [Default initial value] implementation-defined overwriteable by prolog [Scope] lexical [Consistency rules] Value must be castable to xs:language.

Output: overwriteable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] Statically known languages [Default initial value] none cannot be augmented or overwritten by prolog [Scope] module [Consistency rules] Each string uniquely identifies a language.

Output: augmentable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] FTWildCardOption [Default initial value] no wildcards overwriteable by prolog [Scope] lexical [Consistency rules] Value must be wildcards or no wildcards.

Output: no

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Name] src [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with the fetchid attribute. [Default Value] none [Valid Values] a valid URI [Description] A URI which references a resource which is the script content, and which must be resolved when the CCXML document is compiled. Note that the value of the src attribute must not be an ECMAScript expression in order to allow it to be resolved at compile-time. If the ECMAScript script referenced can not be loaded at the CCXML document loading and parsing phase it should be considered a Fetching & compilation error as defined in section 9.5.1. [Type]

Output: Valid URI

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] fetchid [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with the src attribute, otherwise ignored. [Default Value] none [Valid Values] valid fetch ID [Description] An ECMAScript expression which returns the fetch identifier of a completed fetch request, acquired either in a fetch with the fetchid attribute, or from the fetchid attribute of a fetch.done event. If the fetch identifier is invalid, has not completed, or the fetched content is not valid ECMAScript, an error.semantic event must be thrown. [Type]

Output: ECMAScript Expression

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] timeout [Required] false [Attribute Constraints] This attribute is only valid in conjunction with the src attribute, otherwise ignored. [Default Value] none [Valid Values] Character string in CSS2 [CSS2] format [Description] The character string must be interpreted as a time interval. This interval must begin when the script is requested; If the script has not been fetched at the end of this interval, an error.fetch or error.createccxml event must be thrown. [Type]

Output: Character string

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxage [Required] false [Attribute Constraints] This attribute is only valid in conjunction with the src attribute, otherwise ignored. [Default Value] none [Valid Values] A valid time value for the HTTP 1.1 request [RFC2616] [Description] The character string must be interpreted as a time interval. This indicates that the document is willing to use content whose age must be no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616]). The document is not willing to use stale content, unless maxstale is also provided. [Type]

Output: Character string

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxstale [Required] false [Attribute Constraints] This attribute is only valid in conjunction with the src attribute, otherwise ignored. [Default Value] none [Valid Values] A valid time value for the HTTP 1.1 request [RFC2616] [Description] The character string must be interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-stale' in HTTP 1.1 [RFC2616]). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds. [Type]

Output: Character string

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] charset [Required] false [Default Value] UTF-8 [Valid Values] valid character encoding type [Description] A character string that indicates the character encoding type of the script. UTF-8 and UTF-16 encodings of ISO/IEC 10646 must be supported (as in [XML] ) and other encodings, as defined in the [IANA] , may be supported. [Type]

Output: Character string

Voice Browser Call Control: CCXML Version 1.0


Input: [Keyword] hidden [Data type] An arbitrary string [Control type] n/a [State]

Output: Hidden


Input: [Keyword] text [Data type] Text with no line breaks [Control type] A text field [State]

Output: Text


Input: [Keyword] search [Data type] Text with no line breaks [Control type] Search field [State]

Output: Search


Input: [Keyword] tel [Data type] Text with no line breaks [Control type] A text field [State]

Output: Telephone


Input: [Keyword] url [Data type] An absolute URL [Control type] A text field [State]

Output: URL


Input: [Keyword] email [Data type] An e-mail address or list of e-mail addresses [Control type] A text field [State]

Output: E-mail


Input: [Keyword] password [Data type] Text with no line breaks (sensitive information) [Control type] A text field that obscures data entry [State]

Output: Password


Input: [Keyword] datetime [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with the time zone set to UTC [Control type] A date and time control [State]

Output: Date and Time


Input: [Keyword] date [Data type] A date (year, month, day) with no time zone [Control type] A date control [State]

Output: Date


Input: [Keyword] month [Data type] A date consisting of a year and a month with no time zone [Control type] A month control [State]

Output: Month


Input: [Keyword] week [Data type] A date consisting of a week-year number and a week number with no time zone [Control type] A week control [State]

Output: Week


Input: [Keyword] time [Data type] A time (hour, minute, seconds, fractional seconds) with no time zone [Control type] A time control [State]

Output: Time


Input: [Keyword] datetime-local [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with no time zone [Control type] A date and time control [State]

Output: Local Date and Time


Input: [Keyword] number [Data type] A numerical value [Control type] A text field or spinner control [State]

Output: Number


Input: [Keyword] range [Data type] A numerical value, with the extra semantic that the exact value is not important [Control type] A slider control or similar [State]

Output: Range


Input: [Keyword] color [Data type] An sRGB color with 8-bit red, green, and blue components [Control type] A color well [State]

Output: Color


Input: [Keyword] checkbox [Data type] A set of zero or more values from a predefined list [Control type] A checkbox [State]

Output: Checkbox


Input: [Keyword] radio [Data type] An enumerated value [Control type] A radio button [State]

Output: Radio Button


Input: [Keyword] file [Data type] Zero or more files each with a MIME type and optionally a file name [Control type] A label and a button [State]

Output: File Upload


Input: [Keyword] submit [Data type] An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission [Control type] A button [State]

Output: Submit Button


Input: [Keyword] image [Data type] A coordinate, relative to a particular image's size, with the extra semantic that it must be the last value selected and initiates form submission [Control type] Either a clickable image, or a button [State]

Output: Image Button


Input: [Keyword] reset [Data type] n/a [Control type] A button [State]

Output: Reset Button


Input: [Keyword] button [Data type] n/a [Control type] A button [State]

Output: Button


Input: [Component] FTCaseOption [Default initial value] case insensitive overwriteable overwriteable by prolog [Consistency rules] Value must be case insensitive, case sensitive, lowercase, or uppercase. [Scope]

Output: lexical

Static Context Components


Input: [Component] FTDiacriticsOption [Default initial value] diacritics insensitive overwriteable overwriteable by prolog [Consistency rules] Value must be diacritics insensitive or diacritics sensitive. [Scope]

Output: lexical

Static Context Components