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

Output: lexical

Static Context Components


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

Output: lexical

Static Context Components


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

Output: module

Static Context Components


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

Output: lexical

Static Context Components


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

Output: module

Static Context Components


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

Output: lexical

Static Context Components


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

Output: module

Static Context Components


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

Output: lexical

Static Context Components


Input: [Notes] Sub property of dcterms:creator and foaf:maker. [Type] RDF Data Property [Introduced] Section 2.2 [Term]

Output: issuedby

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Notes] RDF/OWL tools must understand the POWDER Semantic Extension to process the semantics of this property. [Type] RDF Data Property [Introduced] Section 2.2 [Term]

Output: matchesregex

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Notes] Property used by a POWDER Processor that it does not have any information about a particular IRI [Type] RDF Data Property [Introduced] Section 3 [Term]

Output: notknownto

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Notes] The class of POWDER Processors [Type] RDF Class [Introduced] Section 3 [Term]

Output: Processor

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Notes] An RDF property that links a described resource to a POWDER document. For use with RDFa and other rich formats. [Type] RDF Data Property [Introduced] Section 4.1.3 [Term]

Output: describedby

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Notes] The class of POWDER documents [Type] RDF Class [Introduced] Section 4.1.3 [Term]

Output: Document

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Notes] An RDF property that links a dcterms:Agent or foaf:Agent class to a resource describing how to authenticate its DRs. [Type] RDF Data Property [Introduced] Section 5.1 [Term]

Output: authenticate

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Name] target [Required] false [Attribute Constraints] Must not occur with 'targetexpr' [Type] URI [Default Value] none [Description] The unique identifier of the message target that the platform should send the event to. See 6.2.4 The Target of Send for details. [Valid Values]

Output: A valid target URI

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


Input: [Name] targetexpr [Required] false [Attribute Constraints] Must not occur with 'target' [Type] Value expression [Default Value] none [Description] A dynamic alternative to 'target'. 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 'target'. [Valid Values]

Output: An expression evaluating to a valid target URI

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


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

Output: Any valid token

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


Input: [Name] idlocation [Required] false [Attribute Constraints] Must not occur with 'id'. [Type] Location expression [Default Value] none [Description] Any location expression evaluating to a data model location in which a system-generated id can be stored. See below for details. [Valid Values]

Output: Any valid location expression

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


Input: [Name] delay [Required] false [Attribute Constraints] Must not occur with 'delayexpr' or when the attribute 'target' has the value "_internal". [Type] Duration.datatype [Default Value] None [Description] Indicates how long the processor should wait before dispatching the message. See E Schema for details on the data type. [Valid Values]

Output: A time designation as defined in CSS2 [CSS2] format

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


Input: [Name] delayexpr [Required] false [Attribute Constraints] Must not occur with 'delay' or when the attribute 'target' has the value "_internal". [Type] Value expression [Default Value] None [Description] A dynamic alternative to 'delay'. 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 'delay'. [Valid Values]

Output: A value expression which returns a time designation as defined in CSS2 [CSS2] format

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


Input: [Name] namelist [Required] false [Attribute Constraints] Must not be specified in conjunction with element. [Type] List of location expressions [Default Value] none [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 5.9.2 Location Expressions for details. [Valid Values]

Output: List of data model locations

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


Input: [Name] event [Required] false [Attribute Constraints] Must not occur with 'eventexpr'. If the type is http://www.w3.org/TR/scxml/#SCXMLEventProcessor, either this attribute or 'eventexpr' must be present. [Default Value] none [Description] A string indicating the name of message being generated. See E Schema for details on the data type. [Type]

Output: EventType.datatype

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


Input: [Name] eventexpr [Required] false [Attribute Constraints] Must not occur with 'event'. If the type is http://www.w3.org/TR/scxml/#SCXMLEventProcessor, either this attribute or 'event' must be present. [Default Value] none [Description] A dynamic alternative to 'event'. 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 'event'. [Type]

Output: Value expression

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


Input: [Name] target [Required] false [Attribute Constraints] Must not occur with 'targetexpr' [Default Value] none [Valid Values] A valid target URI [Description] The unique identifier of the message target that the platform should send the event to. See 6.2.4 The Target of Send for details. [Type]

Output: URI

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


Input: [Name] targetexpr [Required] false [Attribute Constraints] Must not occur with 'target' [Default Value] none [Valid Values] An expression evaluating to a valid target URI [Description] A dynamic alternative to 'target'. 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 'target'. [Type]

Output: Value expression

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


Input: [Name] type [Required] false [Attribute Constraints] Must not occur with 'typeexpr' [Default Value] none [Description] The URI that identifies the transport mechanism for the message. See 6.2.5 The Type of Send for details. [Type]

Output: URI

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


Input: [Name] typeexpr [Required] false [Attribute Constraints] Must not occur with 'type' [Default Value] none [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'. [Type]

Output: value expression

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


Input: [Name] id [Required] false [Attribute Constraints] Must not occur with 'idlocation'. [Default Value] none [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. [Type]

Output: xml:ID

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


Input: [Name] idlocation [Required] false [Attribute Constraints] Must not occur with 'id'. [Default Value] none [Valid Values] Any valid location expression [Description] Any location expression evaluating to a data model location in which a system-generated id can be stored. See below for details. [Type]

Output: Location expression

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


Input: [Name] delay [Required] false [Attribute Constraints] Must not occur with 'delayexpr' or when the attribute 'target' has the value "_internal". [Default Value] None [Valid Values] A time designation as defined in CSS2 [CSS2] format [Description] Indicates how long the processor should wait before dispatching the message. See E Schema for details on the data type. [Type]

Output: Duration.datatype

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


Input: [Name] delayexpr [Required] false [Attribute Constraints] Must not occur with 'delay' or when the attribute 'target' has the value "_internal". [Default Value] None [Valid Values] A value expression which returns a time designation as defined in CSS2 [CSS2] format [Description] A dynamic alternative to 'delay'. 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 'delay'. [Type]

Output: Value expression

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


Input: [Name] namelist [Required] false [Attribute Constraints] Must not be specified in conjunction with element. [Default Value] none [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 5.9.2 Location Expressions for details. [Type]

Output: List of location expressions

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


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

Output: overwriteable by prolog

Static Context Components

Can be overwritten or augmented by a query?


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

Output: overwriteable by prolog

Static Context Components

Can be overwritten or augmented by a query?


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

Output: overwriteable by prolog

Static Context Components

Can be overwritten or augmented by a query?


Input: [Component] FTThesaurusOption [Default initial value] no thesaurus overwriteable [Scope] lexical [Consistency rules] Each URI in the value must be found in the statically known thesauri.

Output: overwriteable by prolog (refer to default to augment)

Static Context Components

Can be overwritten or augmented by a query?


Input: [Component] Statically known thesauri [Default initial value] none augmentable [Scope] module [Consistency rules] Each URI uniquely identifies a thesaurus list.

Output: cannot be augmented or overwritten by prolog

Static Context Components

Can be overwritten or augmented by a query?


Input: [Component] FTStopWordOption [Default initial value] no stop words overwriteable [Scope] lexical [Consistency rules] Each URI in the value must be found in the statically known stop word lists.

Output: overwriteable by prolog (refer to default to augment)

Static Context Components

Can be overwritten or augmented by a query?


Input: [Component] Statically known stop word lists [Default initial value] none augmentable [Scope] module [Consistency rules] Each URI uniquely identifies a stop word list.

Output: cannot be augmented or overwritten by prolog

Static Context Components

Can be overwritten or augmented by a query?


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

Output: overwriteable by prolog

Static Context Components

Can be overwritten or augmented by a query?


Input: [Component] Statically known languages [Default initial value] none augmentable [Scope] module [Consistency rules] Each string uniquely identifies a language.

Output: cannot be augmented or overwritten by prolog

Static Context Components

Can be overwritten or augmented by a query?


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

Output: overwriteable by prolog

Static Context Components

Can be overwritten or augmented by a query?


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

Output: FTCaseOption

Static Context Components


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

Output: FTDiacriticsOption

Static Context Components


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

Output: FTStemOption

Static Context Components


Input: [Default initial value] no thesaurus overwriteable 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. [Component]

Output: FTThesaurusOption

Static Context Components


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

Output: Statically known thesauri

Static Context Components


Input: [Default initial value] no stop words overwriteable 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. [Component]

Output: FTStopWordOption

Static Context Components


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

Output: Statically known stop word lists

Static Context Components


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

Output: FTLanguageOption

Static Context Components


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

Output: Statically known languages

Static Context Components


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

Output: FTWildCardOption

Static Context Components


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

Output: dragstart

7.7 Drag and drop — HTML5: Edition for Web Authors


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

Output: drag

7.7 Drag and drop — HTML5: Edition for Web Authors


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

Output: dragenter

7.7 Drag and drop — HTML5: Edition for Web Authors


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

Output: dragleave

7.7 Drag and drop — HTML5: Edition for Web Authors


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

Output: dragover

7.7 Drag and drop — HTML5: Edition for Web Authors


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

Output: drop

7.7 Drag and drop — HTML5: Edition for Web Authors


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

Output: dragend

7.7 Drag and drop — HTML5: Edition for Web Authors


Input: [Identifier] eq [Semantics]

Output: The “Equals” operator indicating that a given value equals the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.3.2: Terms for the attribute “operator” of the entity Constraint


Input: [Identifier] gt [Semantics]

Output: The “Greater Than” operator indicating that a given value is greater than the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] gteq [Semantics]

Output: The “Greater Than or Equal To” operator indicating that a given value is greater than or equal to the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] hasPart [Semantics]

Output: The “Has Part” operator indicating that a given value contains the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isA [Semantics]

Output: The “Is A” operator indicating that a given value is an instance of the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isAllOf [Semantics]

Output: The “Is All Of” operator indicating that a given value is all of the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isAnyOf [Semantics]

Output: The “Is Any Of” operator indicating that a given value is any of the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isNoneOf [Semantics]

Output: The “Is None Of” operator indicating that a given value is none of the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isPartOf [Semantics]

Output: The “Is Part Of” operator indicating that a given value is contained by the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] lt [Semantics]

Output: The “Less Than” operator indicating that a given value is less than the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] lteq [Semantics]

Output: The “Less Than or Equal To” operator indicating that a given value is less than or equal to the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] neq [Semantics]

Output: The “Not Equal To” operator indicating that a given value is not equal to the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: "none"

7.7 Drag and drop — HTML5: Edition for Web Authors


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

Output: "none"

7.7 Drag and drop — HTML5: Edition for Web Authors


Input: [Event Name] dragenter [Target] Immediate user selection or the body element [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [Default Action] Reject immediate user selection as potential target element [dropEffect]

Output: Based on effectAllowed value

7.7 Drag and drop — HTML5: Edition for Web Authors


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

Output: "none"

7.7 Drag and drop — HTML5: Edition for Web Authors


Input: [Event Name] dragover [Target] Current target element [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [Default Action] Reset the current drag operation to "none" [dropEffect]

Output: Based on effectAllowed value

7.7 Drag and drop — HTML5: Edition for Web Authors


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

Output: Current drag operation

7.7 Drag and drop — HTML5: Edition for Web Authors


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

Output: Current drag operation

7.7 Drag and drop — HTML5: Edition for Web Authors


Input: [Clause] Access [Applies to] proposal or statement [Required in Every Proposal] yes [Default Type of Label] URI or text string [May be Defined in Vocabulary] yes [Description]

Output: The ability of users to obtain and correct information that an entity has collected about them


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

Output: The entity who the user is entering into an agreement with


Input: [Clause] Consequence [Applies to] proposal or statement [Required in Every Proposal] yes [Default Type of Label] URI or text string [May be Defined in Vocabulary] yes [Description]

Output: The impact on the user of reaching an agreement


Input: [Clause] Contact [Applies to] proposal or statement [Required in Every Proposal] yes [Default Type of Label] URI or text string [May be Defined in Vocabulary] yes [Description]

Output: Information for contacting a service with inquiries about the services privacy practices.


Input: [Clause] Experience Space [Applies to] proposal or statement [Required in Every Proposal] yes [Default Type of Label] set of URIs [May be Defined in Vocabulary] no [Description]

Output: The space where a particular statement is valid


Input: [Clause] Practice [Applies to] statement [Required in Every Proposal] yes [Default Type of Label] none [May be Defined in Vocabulary] yes [Description]

Output: What a service will do with data


Input: [Clause] Qualified Data Set [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 [Description]

Output: The data a service proposes to collect or requests


Input: [Clause] Qualifier [Applies to] proposal, statement, or clause [Required in Every Proposal] no [Default Type of Label] none [May be Defined in Vocabulary] yes [Description]

Output: Used by the creator of a vocabulary to provide extra functionality beyond that in the base P3 Proposal Grammar


Input: [Clause] Required [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 [Description]

Output: A binary value indicating whether a particular practice, qualified data set, or statement is required in an agreement


Input: [Clause] Schema [Applies to] proposal [Required in Every Proposal] yes [Default Type of Label] URI [May be Defined in Vocabulary] no [Description]

Output: A URI that identifies a particular P3 proposal vocabulary


Input: [Clause] Signature [Applies to] Proposal or statement [Required in Every Proposal] no [Default Type of Label] none [May be Defined in Vocabulary] yes [Description]

Output: Signature and attribution information as defined by the Digital Signature effort


Input: [Name] type [Required] false [Attribute Constraints] Must not occur with the 'typeexpr' attribute. [Default Value] none [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. [Type]

Output: URI

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


Input: [Name] typeexpr [Required] false [Attribute Constraints] Must not occur with the 'type' attribute. [Default Value] none [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'. [Type]

Output: value expression

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. [Default Value] None [Valid Values] Any URI. [Description] A URI to be passed to the external service. See below for details. [Type]

Output: URI

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. [Default Value] None [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'. [Type]

Output: Value expression

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


Input: [Name] id [Required] false [Attribute Constraints] Must not occur with the 'idlocation' attribute. [Default Value] none [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. [Type]

Output: ID

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


Input: [Name] idlocation [Required] false [Attribute Constraints] Must not occur with the 'id' attribute. [Default Value] none [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. [Type]

Output: Location expression

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


Input: [Name] namelist [Required] false [Attribute Constraints] Must not occur with the element. [Default Value] none [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. [Type]

Output: List of location expressions

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


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

Output: boolean

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


Input: [Module] Measuring [Type] class [Definition] A sensing device is a device that implements sensing. [Term Name]

Output: SensingDevice


Input: [Module] Measuring [Type] class [Definition] 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. [Term Name]

Output: SensorDataSheet


Input: [Module] Measuring [Type] property [Definition] 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. [Term Name]

Output: observes


Input: [Module] MeasuringCapability [Type] class [Definition] The closeness of agreement between the value of an observation and the true value of the observed quality. [Term Name]

Output: Accuracy


Input: [Module] MeasuringCapability [Type] class [Definition] 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. [Term Name]

Output: DetectionLimit


Input: [Module] MeasuringCapability [Type] class [Definition] A, continuous or incremental, change in the reported values of observations over time for an unchanging quality. [Term Name]

Output: Drift


Input: [Module] MeasuringCapability [Type] class [Definition] The smallest possible time between one observation and the next. [Term Name]

Output: Frequency


Input: [Module] MeasuringCapability [Type] class [Definition] The time between a request for an observation and the sensor providing a result. [Term Name]

Output: Latency


Input: [Module] MeasuringCapability [Type] class [Definition] 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. [Term Name]

Output: MeasurementCapability


Input: [Module] MeasuringCapability [Type] class [Definition] An identifiable and observable characteristic of a sensor's observations or ability to make observations. [Term Name]

Output: MeasurementProperty


Input: [Module] MeasuringCapability [Type] class [Definition] 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.) [Term Name]

Output: MeasurementRange


Input: [Module] MeasuringCapability [Type] class [Definition] 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. [Term Name]

Output: Precision


Input: [Module] MeasuringCapability [Type] class [Definition] The smallest difference in the value of a quality being observed that would result in perceptably different values of observation results. [Term Name]

Output: Resolution


Input: [Module] MeasuringCapability [Type] class [Definition] The time between a (step) change inthe value of an observed quality and a sensor (possibly with specified error) 'settling' on an observed value. [Term Name]

Output: ResponseTime


Input: [Module] MeasuringCapability [Type] class [Definition] 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. [Term Name]

Output: Selectivity


Input: [Module] MeasuringCapability [Type] class [Definition] Sensitivity is the quotient of the change in a result of sensor and the corresponding change in a value of a quality being observed. [Term Name]

Output: Sensitivity


Input: [Module] MeasuringCapability [Type] property [Definition] Relation from a Sensor to a MeasurementCapability describing the measurement properties of the sensor. [Term Name]

Output: hasMeasurementCapability


Input: [Module] MeasuringCapability [Type] property [Definition] Relation from a MeasurementCapability to a MeasurementProperty. For example, to an accuracy (see notes at MeasurementCapability). [Term Name]

Output: hasMeasurementProperty


Input: [Module] Skeleton [Term Name] FeatureOfInterest [Definition] A feature is an abstraction of real world phenomena (thing, person, event, etc). [Type]

Output: class


Input: [Module] Skeleton [Term Name] Observation [Definition] 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. [Type]

Output: class


Input: [Module] Skeleton [Term Name] Property [Definition] 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. [Type]

Output: class


Input: [Module] Skeleton [Term Name] Sensing [Definition] Sensing is a process that results in the estimation, or calculation, of the value of a phenomenon. [Type]

Output: class


Input: [Module] Skeleton [Term Name] Sensor [Definition] 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. [Type]

Output: class


Input: [Module] Skeleton [Term Name] SensorInput [Definition] 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. [Type]

Output: class


Input: [Module] Skeleton [Term Name] SensorOutput [Definition] A sensor outputs a piece of information (an observed value), the value itself being represented by an ObservationValue. [Type]

Output: class


Input: [Module] Skeleton [Term Name] Stimulus [Definition] 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. [Type]

Output: class


Input: [Module] Skeleton [Term Name] detects [Definition] 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. [Type]

Output: property


Input: [Module] Skeleton [Term Name] featureOfInterest [Definition] 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. [Type]

Output: property


Input: [Module] Skeleton [Term Name] forProperty [Definition] 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). [Type]

Output: property


Input: [Module] Skeleton [Term Name] hasProperty [Definition] A relation between a FeatureOfInterest and a Property of that feature. [Type]

Output: property


Input: [Module] Skeleton [Term Name] implementedBy [Definition] 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. [Type]

Output: property


Input: [Module] Skeleton [Term Name] implements [Definition] 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. [Type]

Output: property


Input: [Module] Skeleton [Term Name] isPropertyOf [Definition] Relation between a FeatureOfInterest and a Property (a Quality observable by a sensor) of that feature. [Type]

Output: property


Input: [Module] Skeleton [Term Name] isProxyFor [Definition] 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. [Type]

Output: property


Input: [Module] Skeleton [Term Name] observationResult [Definition] 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. [Type]

Output: property


Input: [Module] Skeleton [Term Name] observedBy [Type]

Output: property


Input: [Module] Skeleton [Term Name] observedProperty [Definition] 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. [Type]

Output: property


Input: [Module] Skeleton [Term Name] ofFeature [Definition] 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). [Type]

Output: property


Input: [Module] Skeleton [Term Name] sensingMethodUsed [Definition] 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] [Type]

Output: property


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

Output: pollstart

Low-level Web NFC API for Trusted Applications


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

Output: pollstop

Low-level Web NFC API for Trusted Applications


Input: [event handler] ontagfound [event type] NFCTagEvent with tag property set to the new NFCTag object. [short description] detect a new NFCTag [event name]

Output: tagfound

Low-level Web NFC API for Trusted Applications


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

Output: taglost

Low-level Web NFC API for Trusted Applications


Input: [event handler] onpeerfound [event type] NFCPeerEvent with peer property set to the new NFCPeer object. [short description] detect a new NFCPeer [event name]

Output: peerfound

Low-level Web NFC API for Trusted Applications


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

Output: peerlost

Low-level Web NFC API for Trusted Applications


Input: [Primary Feature Tested] acyclic [Eclipse COSMOS Result] Invalid [Microsoft Result] Invalid Invalid InvalidCyclesWithAcyclicReferences (row 2) acyclic\InValidCycle.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if an instance of an acyclic type CT references itself.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] acyclic [Eclipse COSMOS Result] Invalid [Microsoft Result] Invalid Invalid InvalidCyclesWithAcyclicReferences (row 3) acyclic\InValidCycleAbstract.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if instances of an element type CT derived from the abstract acyclic element type CT' form a cycle.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] acyclic [Eclipse COSMOS Result] Invalid [Microsoft Result] Invalid Invalid InvalidCyclesWithAcyclicReferences (row 4) acyclic\InValidCycleAnonymous.xml Revision 1.2 CVS Log [Test Case Description] A model is invalid if instances of the acyclic anonymous type CT form a cycle

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] acyclic [Eclipse COSMOS Result] Invalid [Microsoft Result] Invalid Invalid InvalidCyclesWithAcyclicReferences (row 5) acyclic\InValidCycleByExtension.xml Revision 1.3 CVS Log [Test Case Description] A model is invalid if instances of an acyclic element type CT (or derived types by restriction) create a cycle

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] acyclic [Eclipse COSMOS Result] Invalid [Microsoft Result] Invalid Invalid InvalidCyclesWithAcyclicReferences (row 6) acyclic\InValidCycleByRestriction.xml Revision 1.3 CVS Log [Test Case Description] A model is invalid if instances of an acyclic element type CT (or derived types by restriction) create a cycle

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] acyclic [Eclipse COSMOS Result] Invalid [Microsoft Result] Invalid Invalid InvalidDerivationWithAcyclicAttribute (row 7) acyclic\InValidDerivation.xml Revision 1.14 CVS Log [Test Case Description] A model is invalid if it has a reference type R1 with sml:acyclic=?true? and another reference type R2 derived from R1 such that sml:acyclic=?false?

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] acyclic [Eclipse COSMOS Result] Valid [Microsoft Result] Valid Valid ValidateAcyclicDefinition (row 8) acyclic\ValidateDefinition.xml Revision 1.10 CVS Log [Test Case Description] This test returns a warning if the sml:acyclic attribute is defined on an element declaration

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] acyclic [Eclipse COSMOS Result] Valid [Microsoft Result] Valid Valid ValidCyclesWithAcyclicReference2 (row 9) acyclic\ValidCycle.xml Revision 1.2 CVS Log [Test Case Description] Let R1 be a reference type with sml:acyclic=?false?. Then a model is valid if it has inter-document cycles using instances of R1

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] acyclic [Eclipse COSMOS Result] Valid [Microsoft Result] Valid Valid InvalidCyclesWithAcyclicReferences (row 10) acyclic\ValidCycleNoReference.xml Revision 1.3 CVS Log [Test Case Description] A model is valid if an element instance with sml:acyclic="true" forms a cycle but is not declared to be an SML reference (despite having a valid sml:uri scheme)

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] acyclic [Eclipse COSMOS Result] Valid [Microsoft Result] Valid Valid InvalidCyclesWithAcyclicReferences (row 11) acyclic\ValidCycleNullReference.xml Revision 1.3 CVS Log [Test Case Description] A model is valid if an element instance with sml:acyclic="true" forms a cycle but is declared as a null SML reference (despite having a valid sml:uri scheme)

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] acyclic [Eclipse COSMOS Result] Valid [Microsoft Result] Valid Valid ValidCycles3 (row 12) acyclic\ValidCycleVariation.xml Revision 1.3 CVS Log [Test Case Description] This test verifies that it is valid to create cycles within documents, as long as instances of acyclic references do not create cycles.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] acyclic [Eclipse COSMOS Result] Valid [Microsoft Result] Valid Valid ValidDerivationWithAcyclicAttribute (row 13) acyclic\ValidDerivation.xml Revision 1.13 CVS Log [Test Case Description] A model is valid if it has a reference type R1 with sml:acyclic=?false? and another reference type R2 derived from R1 such that sml:acyclic=?true?

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] acyclic [Eclipse COSMOS Result] Valid [Microsoft Result] Valid Valid ValidCyclesWithAcyclicReference1 (row 14) acyclic\ValidMultipleAcyclics.xml Revision 1.2 CVS Log [Test Case Description] Let R1 and R2 be two reference types with sml:acyclic=?true?. Then a model is valid if it has inter-document cycles using instances of both R1 and R2

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] acyclic [Eclipse COSMOS Result] Valid [Microsoft Result] Valid Valid ValidUnresolvedReference (row 15) acyclic\ValidUnresolvedReference.xml Revision 1.3 CVS Log [Test Case Description] A model is valid if an element instance with sml:acyclic="true" references an unresolved document.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] Base64 [Eclipse COSMOS Result] Invalid [Microsoft Result] Invalid Invalid Base64DTDEntity (row 16) base64\Base64DTDEntity.xml Revision 1.3 CVS Log [Test Case Description] This test verifies that the code returns success when a document that is a child of the base64Data element is encoded in Base64 format. The encoded document is an XML document with DTD definition. The DTD has entity definitions that are used in the XML.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] Base64 [Eclipse COSMOS Result] Invalid [Microsoft Result] Invalid Invalid Base64DTDInvalidXML (row 17) base64\Base64DTDInvalidXML.xml Revision 1.3 CVS Log [Test Case Description] The encoded document is an XML document with DTD definition. The XML sturcture is invalid according to the DTD, but since DTD validation is not done by the SML/SML-IF validator, the SML validator should report success.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] Base64 [Eclipse COSMOS Result] Invalid [Microsoft Result] Invalid Invalid Base64DTDMissingEntities (row 18) base64\Base64DTDMissingEntities.xml Revision 1.2 CVS Log [Test Case Description] The encoded document is an XML document with DTD definition. The XML uses entities that are not defined in the DTD. The validation should fail because DTD is processed with fatal failure.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] Base64 [Eclipse COSMOS Result] Valid [Microsoft Result] Valid Valid Base64EncodedDoc (row 19) base64\Base64EncodedDoc.xml Revision 1.6 CVS Log [Test Case Description] An instance document is base64 encoded.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] Base64 [Eclipse COSMOS Result] Valid [Microsoft Result] Valid Valid Base64EncodedDocs (row 20) base64\Base64EncodedDocs.xml Revision 1.4 CVS Log [Test Case Description] Let R1 and R2 be two reference types with sml:acyclic=?true?. Then a model is valid if it has inter-document cycles that using instances of both R1 and R2

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


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

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] Base64 [Eclipse COSMOS Result] 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

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] Base64 [Eclipse COSMOS Result] 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

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] Base64 [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] Base64 [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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}.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


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

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] idConstraint [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] locator [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] aliases [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] aliases [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] aliases [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] validation [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] locator [Eclipse COSMOS Result] 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

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] rules [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] rules [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] validation [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] Embedded [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlifBaseUri [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlifBaseUri [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlifBaseUri [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlifBaseUri [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] validation [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] xmlBase [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] xmlBase [Eclipse COSMOS Result] 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

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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"

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] smlref [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] xmlBase [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] xmlBase [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] xmlBase [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] xmlBase [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] rules [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] locid [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] locid [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] locid [Eclipse COSMOS Result] 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).

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] locid [Eclipse COSMOS Result] 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).

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] locid [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] ruleBindings [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] ruleBindings [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] ruleBindings [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] ruleBindings [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] ruleBindings [Eclipse COSMOS Result] 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

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] rules [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] rules [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] rules [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] rules [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] validation [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] ruleBindings [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] targetElement [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] targetElement [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] targetElement [Eclipse COSMOS Result] 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}.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] targetElement [Eclipse COSMOS Result] 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)

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] targetElement [Eclipse COSMOS Result] 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.

Output: Invalid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] targetElement [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] targetElement [Eclipse COSMOS Result] 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.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)


Input: [Primary Feature Tested] targetElement [Eclipse COSMOS Result] 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}.

Output: Valid

W3C SML Working Group Implementation Results by Test Case

Expected Result (primary feature supported)