Input: [Value] characters [Description] The text contains characters that are garbled or incorrect or that are not used in the language in which the content appears. [Example] A text ought to have a '•' but instead has a '¥' sign. A German text erroneously uses û, ô, and â instead of the appropriate 'ü', 'ö', and 'ä'. A Japanese text has been garbled and appears with Devanagari characters. [Scope] S or T [Notes]

Output: Characters ought to be used in cases of garbling or systematic use of inappropriate characters, not for spelling issues where individual characters are replaced with incorrect one.

Internationalization Tag Set (ITS) Version 2.0


Input: [Value] numbers [Description] Numbers are inconsistent between source and target. [Example] A source text states that an object is 120 cm long, but the target text says that it is 129 cm. long. [Scope] S or T [Notes]

Output: Some tools may correct for differences in units of measurement to reduce false positives (e.g., a tool might adjust for differences in values between inches and centimeters to avoid flagging numbers that seem to be different but are in fact equivalent).

Internationalization Tag Set (ITS) Version 2.0


Input: [Value] pattern-problem [Description] The text fails to match a pattern that defines allowable content (or matches one that defines non-allowable content). [Example] The tool disallows the regular expression pattern ['"”’][\.,] but the translated text contains "A leading “expert”, a political hack, claimed otherwise." A tool uses a regular expression to ensure that the content of an element is an IRI and flags what appears to be a malformed IRI. [Scope] S or T [Notes]

Output: Defining what is or is not an allowable pattern is up to the processing application and is beyond the scope of this specification. Best practice would be to use the Comment attribute to specify the pattern that led to the issue.

Internationalization Tag Set (ITS) Version 2.0


Input: [Value] internationalization [Description] There is an issue related to the internationalization of content. [Example] A line of programming code has embedded language-specific strings. A user interface element leaves no room for text expansion. A form allows only for U.S.-style postal addresses and expects five digit U.S. ZIP codes. [Scope] S or T [Notes]

Output: There are many kinds of internationalization issues. This value is therefore very heterogeneous in what it can refer to.

Internationalization Tag Set (ITS) Version 2.0


Input: [Value] length [Description] There is a significant difference in source and target length. [Example] The translation of a segment is five times as long as the source. [Scope] S or T [Notes]

Output: What constitutes a "significant" difference in length is determined by the model referred to in the locQualityIssueProfileRef.

Internationalization Tag Set (ITS) Version 2.0


Input: [Value] non-conformance [Description] The content is deemed to show poor statistical conformance to a reference corpus. Higher severity values reflect poorer conformance. [Example] The sentence "The harbour connected which to printer is busy or configared not properly." would have poor conformance. [Scope] S or T [Notes]

Output: Non-conformance is determined through the use of multiple statistical measures of similarity to a corpus of known-good content. For example, in a system that uses classification techniques the poor conformance might be a function of combined incorrect terminology, wrong spelling and bad grammar, or other features as determined by the system.

Internationalization Tag Set (ITS) Version 2.0


Input: [Value] uncategorized [Description] The issue either has not been categorized or cannot be categorized. [Example] A new version of a tool returns information on an issue that has not been previously checked and that is not yet classified. A text is defective in ways that defy categorization, such as the appearance of nonsense garbled text of unknown origin (e.g., a translation shows an unintelligible result and/or appears unrelated to the source material). [Scope] S or T [Notes]

Output: This value has the following uses: A tool can use it to pass through quality data from another tool in cases where the issues from the other tool are not classified (for example, a localization quality assurance tool interfaces with a third-party grammar checker). A tool’s issues are not yet assigned to values, and, until an updated assignment is made, they may be listed as uncategorized. In this case it is recommended that issues be assigned to appropriate values as soon as possible since uncategorized does not foster interoperability. uncategorized can be used where a portion of text is defective in a way that defies assignment to a value in either the originating system or in any other ITS localization quality markup to indicate that it is uncategorizable.

Internationalization Tag Set (ITS) Version 2.0


Input: [Value] other [Description] Any issue that cannot be assigned to any values listed above. [Scope] S or T [Notes]

Output: This value allows for the inclusion of any issues not included in the previously listed values. It is encouraged not to use this value for any tool- or model-specific issues that can be mapped to the values listed above. In addition, this value is not synonymous with uncategorized in that uncategorized issues may be assigned to another precise value, while other issues cannot. If a system has an "miscellaneous" or "other" value, it is better to map this to this value even if the specific instance of the issue might be mapped to another value.

Internationalization Tag Set (ITS) Version 2.0


Input: [Module] System [Term Name] System [Type] class [Definition]

Output: System is a unit of abstraction for pieces of infrastructure (and we largely care that they are) for sensing. A system has components, its subsystems, which are other systems.


Input: [Module] System [Term Name] hasSubSystem [Type] property [Definition]

Output: Haspart relation between a system and its parts.


Input: [Module] Process [Term Name] Input [Type] class [Definition]

Output: Any information that is provided to a process for its use [MMI OntDev]


Input: [Module] Process [Term Name] Output [Type] class [Definition]

Output: Any information that is reported from a process. [MMI OntDev]


Input: [Module] Process [Term Name] Process [Type] class [Definition]

Output: A process has an output and possibly inputs and, for a composite process, describes the temporal and dataflow dependencies and relationships amongst its parts. [SSN XG]


Input: [Module] Process [Term Name] isProducedBy [Type] property [Definition]

Output: Relation between a producer and a produced entity: for example, between a sensor and the produced output.


Input: [Description] Alignment of event codes and content items [Default Value] bit-packed [EXI Option]

Output: alignment

EXI Options in Options Field


Input: [Description] EXI compression is used to achieve better compactness [Default Value] false [EXI Option]

Output: compression

EXI Options in Options Field


Input: [Description] Strict interpretation of schemas is used to achieve better compactness [Default Value] false [EXI Option]

Output: strict

EXI Options in Options Field


Input: [Description] Body is encoded as an EXI fragment instead of an EXI document [Default Value] false [EXI Option]

Output: fragment

EXI Options in Options Field


Input: [Description] Specifies whether comments, pis, etc. are preserved [Default Value] all false [EXI Option]

Output: preserve

EXI Options in Options Field


Input: [Description] Identify the schema information, if any, used to encode the body [Default Value] none [EXI Option]

Output: schemaID

EXI Options in Options Field


Input: [Description] Identify pluggable CODECs used to encode body [Default Value] none [EXI Option]

Output: codecMap

EXI Options in Options Field


Input: [Description] Specifies the block size used for EXI compression [Default Value] 1,000,000 [EXI Option]

Output: blockSize

EXI Options in Options Field


Input: [Description] User defined headers may be added [Default Value] none [EXI Option]

Output: [user defined]

EXI Options in Options Field


Input: [Semantics] The Party is a single individual [Comment] Must be supported. [Identifier]

Output: Individual

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.4.2: Terms for the attribute “scope” of the entity Role


Input: [Semantics] The Party represents a defined group with multiple individual members [Comment] Must be supported. [Identifier]

Output: Group

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] All the collective individuals within a context [Comment] For example, may be used to indicate all the users of a specific social network the party is a member of. Note that “group” scope is also assumed. [Identifier]

Output: All

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] All the first-level connections of the Party [Comment] For example, may be used to indicate all “friends” of the Party. Note that “group” scope is also assumed. [Identifier]

Output: AllConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] All the second-level connections of the Party [Comment] For example, may be used to indicate all “friends of friends” of the Party. Note that “group” scope is also assumed. [Identifier]

Output: All2ndConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] All the group connections of the Party [Comment] For example, may be used to indicate all groups that the Party is a member of. Note that “group” scope is also assumed. [Identifier]

Output: AllGroups

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [EXI Option] alignment [Default Value] bit-packed [Description]

Output: Alignment of event codes and content items

EXI Options in Options Field


Input: [EXI Option] compression [Default Value] false [Description]

Output: EXI compression is used to achieve better compactness

EXI Options in Options Field


Input: [EXI Option] strict [Default Value] false [Description]

Output: Strict interpretation of schemas is used to achieve better compactness

EXI Options in Options Field


Input: [EXI Option] fragment [Default Value] false [Description]

Output: Body is encoded as an EXI fragment instead of an EXI document

EXI Options in Options Field


Input: [EXI Option] preserve [Default Value] all false [Description]

Output: Specifies whether comments, pis, etc. are preserved

EXI Options in Options Field


Input: [EXI Option] schemaID [Default Value] none [Description]

Output: Identify the schema information, if any, used to encode the body

EXI Options in Options Field


Input: [EXI Option] codecMap [Default Value] none [Description]

Output: Identify pluggable CODECs used to encode body

EXI Options in Options Field


Input: [EXI Option] blockSize [Default Value] 1,000,000 [Description]

Output: Specifies the block size used for EXI compression

EXI Options in Options Field


Input: [EXI Option] [user defined] [Default Value] none [Description]

Output: User defined headers may be added

EXI Options in Options Field


Input: [attribute] archive [function]

Output: For example, when defining an applet you could reference a space-separated list of jar files.


Input: [attribute] content-length [function]

Output: This is similar to meta data, in that this can be used by the object handler as a hint to the physical size of the object data that is to be processed.


Input: [attribute] data [function]

Output: This URI points to the object data to be processed. This can be an absolute URI (http://www.example.com/datafiles/myinstance.mpg), or a relative URI (myinstance.mpg). If you use a relative URI, then you will need to use the xml:base attribute to define the base location of the object data. This attribute should only refer to the data to be processed.


Input: [attribute] declare [function]

Output: This is used to delay the processing of the object data until such time that it is referred to by another element that requires the object data to be processed. In other words, the object data should be downloaded but should not be processed. For example, if an a element is coded to refer to the object element and the a element is activated, then the object data would be processed.


Input: [attribute] standby [function]

Output: The author can provide a text string that should be displayed while the object data is being downloaded and processed.


Input: [attribute] type [function]

Output: Defining the mime type of the object data will assist the object handler in determining whether the object data can be processed by the user agent or if an external application needs to be launched to process the object data.


Input: [attribute] xml:base [function]

Output: Use this attribute to define the base location of the object data. For example: http://www.example.com/datafiles/. This attribute should not be used for any other purpose.


Input: [function] For example, when defining an applet you could reference a space-separated list of jar files. [attribute]

Output: archive


Input: [function] This is similar to meta data, in that this can be used by the object handler as a hint to the physical size of the object data that is to be processed. [attribute]

Output: content-length


Input: [function] This URI points to the object data to be processed. This can be an absolute URI (http://www.example.com/datafiles/myinstance.mpg), or a relative URI (myinstance.mpg). If you use a relative URI, then you will need to use the xml:base attribute to define the base location of the object data. This attribute should only refer to the data to be processed. [attribute]

Output: data


Input: [function] This is used to delay the processing of the object data until such time that it is referred to by another element that requires the object data to be processed. In other words, the object data should be downloaded but should not be processed. For example, if an a element is coded to refer to the object element and the a element is activated, then the object data would be processed. [attribute]

Output: declare


Input: [function] The author can provide a text string that should be displayed while the object data is being downloaded and processed. [attribute]

Output: standby


Input: [function] Defining the mime type of the object data will assist the object handler in determining whether the object data can be processed by the user agent or if an external application needs to be launched to process the object data. [attribute]

Output: type


Input: [function] Use this attribute to define the base location of the object data. For example: http://www.example.com/datafiles/. This attribute should not be used for any other purpose. [attribute]

Output: xml:base


Input: [Module] System [Term Name] System [Definition] System is a unit of abstraction for pieces of infrastructure (and we largely care that they are) for sensing. A system has components, its subsystems, which are other systems. [Type]

Output: class


Input: [Module] System [Term Name] hasSubSystem [Definition] Haspart relation between a system and its parts. [Type]

Output: property


Input: [Module] Process [Term Name] Input [Definition] Any information that is provided to a process for its use [MMI OntDev] [Type]

Output: class


Input: [Module] Process [Term Name] Output [Definition] Any information that is reported from a process. [MMI OntDev] [Type]

Output: class


Input: [Module] Process [Term Name] Process [Definition] A process has an output and possibly inputs and, for a composite process, describes the temporal and dataflow dependencies and relationships amongst its parts. [SSN XG] [Type]

Output: class


Input: [Module] Process [Term Name] hasInput [Type]

Output: property


Input: [Module] Process [Term Name] hasOutput [Type]

Output: property


Input: [Module] Process [Term Name] isProducedBy [Definition] Relation between a producer and a produced entity: for example, between a sensor and the produced output. [Type]

Output: property


Input: [Status] Proposal [Summary] To promote the 'citation' property currently on MedicalScholarlyArticle up to CreativeWork. [Vocab] Moves citation up to CreativeWork [Topic]

Output: Citation Promotion

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Extension for describing accessibility properties of a CreativeWork. [Comments] Draft published to elicit feedback. [Topic]

Output: Accessibility

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Property to indicate that a single identity is being described. [Vocab] Essentially same meaning as owl:sameAs, but suggesting a distinct name to make it easier to talk about; also schema.org data is typically scruffier than OWL re http-range-14. [Comments] Draft published to elicit feedback. [Topic]

Output: sameThingAs

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal for a new Action type. [Vocab] See full entry and proposal for details. May2013 version builds on two previously published designs. [Comments] The schema.org team solicit comments on this draft via public-vocabs@w3.org. [Topic]

Output: Actions in Schema.org

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] "While schema.org already supports marking up offers to sell products (pre-transaction), it does not currently provide schema for the common kinds of confirmations and notifications around orders (post-transaction)". [Vocab] Adds classes OrderStatus, Order, DeliveryMethod plus associated properties. [Comments] Complements Actions proposal, but independent. [Topic]

Output: Orders in Schema.org

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] This proposal includes new types for describing reservations and tickets [Vocab] Adds classes Reservation, ReservationStatus, ProgramMembership, Flight, TrainTrip, TrainReservation, FoodEstablishmentReservation, FlightReservation, EventReservation, ReservationPackage, BusReservation, BusTrip, RentalCarReservation, RentalCar, Car, LodgingReservation plus associated properties. [Comments] Complements Actions proposal, but independent. [Topic]

Output: Reservations in Schema.org

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] This proposal adds a single new type, EmailMessage [Vocab] EmailMessage is a CreativeWork representing email messages, just as WebPage already represents Web pages. [Comments] No properties currently defined; proposals welcomed. [Topic]

Output: EmailMessage type

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Accepted [Summary] This proposal adds a single new type, WorkersUnion, addressing issue 17 in the WebSchemas tracker. [Vocab] "A Workers Union (...) is an organization that promotes the interests of its worker members by collectively bargaining with management, organizing, and political lobbying."" [Comments] One type, see draft schema. [Topic]

Output: Workers Union type

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Accepted; published in next version [Summary] Proposes modest changes and additions to support TV and radio (from EBU and BBC). [Vocab] Adds Series, Season, Episode under CreativeWork. Existing TVSeries, TVSeason, TVEpisode under Series/Season/Episode. Adds RadioSeries/RadioSeason/RadioEpisode alongside. Adds Programme/Clip for programmes other than episodes. Adds description of a service with Service/PublicationEvent for broadcast, streaming, VoD, etc. [Comments] See also background notes and [[1]]. Draft initially from EBU/BBC/NoTube discussions. Nearby vocab: see VideoObject, AudioObject; Movie. Event re scheduling. See also UserPlays, a kind of UserInteraction. Comics and TV/Radio also share a concern for describing fictional characters and narratives. [Topic]

Output: TV and Radio proposal

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Some initial discussions. [Summary] Several parties are working towards a Sports Vocabulary proposal. See query from Paul Kelly (SportsML), Microdata + Sports Stats post describing earlier ESPN/Google collaboration, and the Sports Ontology used by BBC, Press Association and others. See also sports-schema-collab mailing list. [Vocab] Several sources including a full draft from the ESPN+Google work. Needs summary here. [Comments] March 2nd - posted writeup of the ESPN/Google Microdata vocabulary; next is discussion on finding common basic sports vocab for schema.org. [Topic]

Output: Sports

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Discussing Proposals [Summary] Proposal from Marvel (see examples). [Vocab] Adds PeriodicalSeries (under Intangible(?)), PeriodicalIssue (under CreativeWork), Comic Issue (under PeriodicalIssue), GraphicNovel (under Book). Approx 6-9 properties for each of these classes. [Comments] Generally well received and specified, but some detailed discussion re fine-grain detail of comics (imprint, page count etc.). Can those properties be shared with Book/numberOfPages, or ScholarlyArticle? Should PeriodicalSeries be intangible? [Topic]

Output: Comics and Serials

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Hopefully Final Proposal - please review [Summary] Proposes some modifications to Event based on deployment experience. [Vocab] Adds eventStatus, previousStartDate, previousEndDate; eventCategory; makes startDate/endDate repeatable. Encourages use of 'url' from Thing. [Comments] Fairly modest proposals based on implementor feedback. May2013 update addresses the last open issue on repeating events. [Topic]

Output: Event schema update

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] The historical-data.org site proposes some extensions to schema.org to address historical and genealogical (family history) scenarios. [Vocab] Adds HistoricalRecord, HistoricalEvent (subclass of Event), overrides attendees, subEvents, superEvent to point to HistoricalEvent. [Comments] There is an associated implementation, github repository, and blog. [Topic]

Output: Historical Data proposal

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A schema extension for describing biological databases, Sagace. [Vocab] Adds a class 'BiologicalDatabaseEntry' as a kind of CreativeWork, introducing 'entryID', 'isEntryOf', 'taxonID'. Adds 'BiologicalDatabase' also subclass of CreativeWork, with no special properties. Both also use 'breadcrumb' from WebPage. [Comments] Others have also mentioned interest in adding some notion of species. [Topic]

Output: Biological Databases

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal resolving current problems handling breadcrumbs. [Vocab] Adds Breadcrumb type with child property and supposes to use this class on breadcrumb property of a WebPage. An important schema, but needs attention. See discussion on using literal values. [Topic]

Output: Breadcrumbs

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal extending schema.org for describing online discussion forums and message boards. [Vocab] Adds attachmentURL, contributorType, discussionState, interestedUsers, postCount, postType, votedHelpful. [Comments] Addition candidate [Topic]

Output: Discussion

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal extending schema.org for describing Innovation and related concepts. Discussion found here: [2] [Vocab] Covers concepts and terms such as Need, Benefit, Usage, Disruption, Innovator, Innovation, Embodiment, to name a few. See [3] for complete list of terms. [Comments] Addition candidate [Topic]

Output: Innovation

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Topic]

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] How far along [Summary] Summary of contribution. [Vocab] Overview of new terms [Comments] Comments on status, particularly regarding integration, overlaps and open issues. [Topic]

Output: Proposal name

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Identifier] Individual [Comment] Must be supported. [Semantics]

Output: The Party is a single individual

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Group [Comment] Must be supported. [Semantics]

Output: The Party represents a defined group with multiple individual members

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] All [Comment] For example, may be used to indicate all the users of a specific social network the party is a member of. Note that “group” scope is also assumed. [Semantics]

Output: All the collective individuals within a context

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] AllConnections [Comment] For example, may be used to indicate all “friends” of the Party. Note that “group” scope is also assumed. [Semantics]

Output: All the first-level connections of the Party

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] All2ndConnections [Comment] For example, may be used to indicate all “friends of friends” of the Party. Note that “group” scope is also assumed. [Semantics]

Output: All the second-level connections of the Party

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] AllGroups [Comment] For example, may be used to indicate all groups that the Party is a member of. Note that “group” scope is also assumed. [Semantics]

Output: All the group connections of the Party

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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: [Property] type [Type] xs:string [Value]

Output: The name of the event.

XPath Expressions Module - W3C XForms Group Wiki (Public)


Input: [Property] bubbles [Type] xs:boolean [Value]

Output: Indicates whether or not an event is a bubbling event. If the event can bubble the value is true, else the value is false.

XPath Expressions Module - W3C XForms Group Wiki (Public)


Input: [Property] cancelable [Type] xs:boolean [Value]

Output: Indicates whether or not an event can have its default action prevented. If the default action can be prevented the value is true, else the value is false.

XPath Expressions Module - W3C XForms Group Wiki (Public)


Input: [Property] targetid [Type] xs:string? [Value]

Output: The id of the target to which the event was originally dispatched. If the target does not have an id an empty sequence is returned.

XPath Expressions Module - W3C XForms Group Wiki (Public)


Input: [Property] current-targetid [Type] xs:string? [Value]

Output: The id of the target whose EventListeners are currently being processed. If that target does not have an id an empty sequence is returned.

XPath Expressions Module - W3C XForms Group Wiki (Public)


Input: [Property] event-phase [Type] xs:string [Value]

Output: The current event phase: capture, target, or bubbling (When the event arrives at the target, the value is 'target'. Values capture and bubbling are as described in XML events)

XPath Expressions Module - W3C XForms Group Wiki (Public)


Input: [Property] time-stamp [Type] xs:integer? [Value]

Output: The time (in milliseconds relative to the epoch) at which the event was created. Due to the fact that some systems may not provide this information the value of timeStamp may be not available for all events. When not available, an empty sequence will be returned. Examples of epoch time are the time of the system start or 0:0:0 UTC 1st January 1970.

XPath Expressions Module - W3C XForms Group Wiki (Public)


Input: [Value for 'clear-side'] auto [Meaning] Depends on type of float (level-2 behavior) [Value for 'wrap-flow']

Output: auto

List of CSS features required for paged media


Input: [Value for 'clear-side'] left [Meaning] Only wrap text around the right side [Value for 'wrap-flow']

Output: right

List of CSS features required for paged media


Input: [Value for 'clear-side'] right [Meaning] Only wrap text around the left side [Value for 'wrap-flow']

Output: left

List of CSS features required for paged media


Input: [Value for 'clear-side'] top [Meaning] In vertical text, only wrap text around the top side; otherwise same as auto. [Value for 'wrap-flow']

Output: bottom

List of CSS features required for paged media


Input: [Value for 'clear-side'] bottom [Meaning] In vertical text, only wrap text around the bottom side; otherwise same as auto. [Value for 'wrap-flow']

Output: top

List of CSS features required for paged media


Input: [Value for 'clear-side'] start [Meaning] Left or right, depending on 'direction' of containing block [Value for 'wrap-flow']

Output: end

List of CSS features required for paged media


Input: [Value for 'clear-side'] end [Meaning] Left or right, depending on 'direction' of containing block [Value for 'wrap-flow']

Output: start

List of CSS features required for paged media


Input: [Value for 'clear-side'] none [Meaning] Text flows on both sides [Value for 'wrap-flow']

Output: both

List of CSS features required for paged media


Input: [Value for 'clear-side'] both [Meaning] No text on either side [Value for 'wrap-flow']

List of CSS features required for paged media


Input: [Value for 'clear-side'] minimum [Meaning] Text on the side with the most space (not yet well defined) [Value for 'wrap-flow']

Output: maximum

List of CSS features required for paged media


Input: [Value for 'clear-side'] maximum [Meaning] Text on the side with the least space (not yet well defined) [Value for 'wrap-flow']

Output: minimum

List of CSS features required for paged media


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


Input: [Section] 2.0 Agreement scenarios [Explanation] propID uniquely identifies any privacy proposal [Feature/Operation]

Output: propID


Input: [Section] 3.1 Data transport [Explanation] agents and services must be able to locate a proposal in this location [Feature/Operation]

Output: the HTML LINK tag


Input: [Explanation] agents and services must be able to locate a proposal in this location [Feature/Operation]

Output: the HTTP extension mechanism


Input: [Explanation] a proposal must be able to be located at an external URI [Feature/Operation]

Output: propURI


Input: [Section] 4.1.2 XML/RDF encoding [Explanation] proposals and data syntax are readily processed or presented to the user. The RDF data model was used to structure the required grammar/syntax but applications need not support RDF if they do not want to take advantage of the RDF data model. [Feature/Operation]

Output: XML parsing


Input: [Section] 4.4 Data References [Explanation] agents must be able to understand that syntax of solicited information [Feature/Operation]

Output: data reference syntax


Input: [Section] Base 3.0 Abstract Elements [Explanation] methods of references data exchanged through mechanisms other than P3P [Feature/Operation]

Output: abstract elements


Input: [Section] Harmonized Vocab [Explanation] see the harmonized vocubarly for requirements; they must be followed otherwise the implementation abuses consensus on adequate levels of privacy disclosure [Feature/Operation]

Output: harmonized vocabulary


Input: [Event name] loadstart [Dispatched when...]

Output: The user agent begins looking for media data, as part of the resource selection algorithm.


Input: [Event name] progress [Dispatched when...]

Output: The user agent is fetching media data.


Input: [Event name] suspend [Dispatched when...]

Output: The user agent is intentionally not currently fetching media data, but does not have the entire media resource downloaded.


Input: [Event name] abort [Dispatched when...]

Output: The user agent stops fetching the media data before it is completely downloaded, but not due to an error.


Input: [Event name] error [Dispatched when...]

Output: An error occurs while fetching the media data.


Input: [Event name] emptied [Dispatched when...]

Output: A media element whose networkState was previously not in the NETWORK_EMPTY state has just switched to that state (either because of a fatal error during load that's about to be reported, or because the load() method was invoked while the resource selection algorithm was already running).


Input: [Event name] stalled [Dispatched when...]

Output: The user agent is trying to fetch media data, but data is unexpectedly not forthcoming.


Input: [Event name] play [Dispatched when...]

Output: Playback has begun. Fired after the play() method has returned, or when the autoplay attribute has caused playback to begin.


Input: [Event name] pause [Dispatched when...]

Output: Playback has been paused. Fired after the pause() method has returned.


Input: [Event name] loadedmetadata [Dispatched when...]

Output: The user agent has just determined the duration and dimensions of the media resource


Input: [Event name] loadeddata [Dispatched when...]

Output: The user agent can render the media data at the current playback position for the first time.


Input: [Event name] waiting [Dispatched when...]

Output: Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course.


Input: [Event name] playing [Dispatched when...]

Output: Playback has started.


Input: [Event name] canplay [Dispatched when...]

Output: The user agent can resume playback of the media data, but estimates that if playback were to be started now, the media resource could not be rendered at the current playback rate up to its end without having to stop for further buffering of content.


Input: [Event name] canplaythrough [Dispatched when...]

Output: The user agent estimates that if playback were to be started now, the media resource could be rendered at the current playback rate all the way to its end without having to stop for further buffering.


Input: [Event name] seeking [Dispatched when...]

Output: The seeking IDL attribute changed to true and the seek operation is taking long enough that the user agent has time to fire the event.


Input: [Event name] seeked [Dispatched when...]

Output: The seeking IDL attribute changed to false.


Input: [Event name] timeupdate [Dispatched when...]

Output: The current playback position changed as part of normal playback or in an especially interesting way, for example discontinuously.


Input: [Event name] ended [Dispatched when...]

Output: Playback has stopped because the end of the media resource was reached.


Input: [Event name] ratechange [Dispatched when...]

Output: Either the defaultPlaybackRate or the playbackRate attribute has just been updated.


Input: [Event name] durationchange [Dispatched when...]

Output: The duration attribute has just been updated.


Input: [Event name] volumechange [Dispatched when...]

Output: Either the volume attribute or the muted attribute has changed. Fired after the relevant attribute's setter has returned.


Input: [Description] An incorrect term or a term from the wrong domain was used or terms are used inconsistently. [Example] The localization had “Pen Drive” when corporate terminology specified that “USB Stick” was to be used. The localized text inconsistently used "Start" and "Begin". A text renders the Hungarian term recsegőhid as “buzzer bridge” in English (a literal translation), but the term to be used in English is “wedge block,” as specified in a terminology list supplied to the translator. [Scope] S or T [Notes] This value is not intended for simple typographical errors or word choice not related to defined terminologies. For example, a mistyping of “pin” as “pen” or the use of “imply” instead of “infer” (mistaking two commonly confused words) would not count as terminology issues and is best categorized as either spelling errors or mistranslations, depending on the nature of the issue. Terminology refers only to cases where incorrect choices about terms (either formal or commonly defined in a domain) are involved. [Value]

Output: terminology

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The content of the target mistranslates the content of the source. [Example] The English source reads "An ape succeeded in grasping a banana lying outside its cage with the help of a stick" but the Italian translation reads "l'ape riuscì a prendere la banana posta tuori dall sua gabbia aiutandosi con un bastone" ("A bee succeeded...") [Scope] T [Notes] Issues related to translation of specific terms related to the domain or task-specific language are to be categorized as terminology issues. [Value]

Output: mistranslation

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] Necessary text has been omitted from the localization or source. [Example] One or more segments found in the source that have been intended for translation are missing in the target. After an alignment, a verification tool flags the pairs of aligned segments where the target has no corresponding source because of incorrect segmentation or some alignment issue. In such case the 'omission' type may apply to the source entry. [Scope] S or T [Notes] This value is not to be used for missing whitespace or formatting codes, but instead has to be reserved for linguistic content. [Value]

Output: omission

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] Content that has been intended for translation is left untranslated. [Example] The source segment reads "The Professor said to Smith that he would hear from his lawyer" but the Hungarian localization reads "A professzor azt mondta Smithnek, hogy he would hear from his lawyer." [Scope] T [Notes] omission takes precedence over untranslated. Omissions are distinct in that they address cases where text is not present, while untranslated addresses cases where text has been carried from the source untranslated. [Value]

Output: untranslated

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The translated text contains inappropriate additions. [Example] The translated text contains a note from the translator to himself to look up a term; the note ought to have been deleted but was not. [Scope] T [Value]

Output: addition

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] Content has been duplicated improperly. [Example] A section of the target text was inadvertently copied twice in a copy and paste operation. [Scope] T [Value]

Output: duplication

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The text is inconsistent with itself or is translated inconsistently (NB: not for use with terminology inconsistency). [Example] The text states that an event happened in 1912 in one location but in another states that it happened in 1812. The translated text uses different wording for multiple instances of a single regulatory notice that occurs in multiple locations in a series of manuals. [Scope] S or T [Value]

Output: inconsistency

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The text contains a grammatical error (including errors of syntax and morphology). [Example] The text reads "The guidelines says that users should use a static grounding strap." [Scope] S or T [Value]

Output: grammar

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The text is legally problematic (e.g., it is specific to the wrong legal system). [Example] The localized text is intended for use in Thailand but includes U.S. regulatory notices. A text translated into German contains comparative advertising claims that are not allowed by German law. [Scope] S or T [Value]

Output: legal

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The text is written in the wrong linguistic register of uses slang or other language variants inappropriate to the text. [Example] A financial text in U.S. English refers to dollars as "bucks". [Scope] S or T [Value]

Output: register

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The localization contains content that does not apply to the locale for which it was prepared. [Example] A text translated for the Japanese market contains call center numbers in Texas and refers to special offers available only in the U.S. [Scope] S or T [Notes] Legally inappropriate material is to be classified as legal. [Value]

Output: locale-specific-content

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] Text violates norms for the intended locale. [Example] A text localized into German has dates in mm/dd/yyyy format instead of DD.MM.YYYY. A text for the Irish market uses American-style foot and inch measurements instead of centimeters. A text intended for a U.S.-based audience uses U.K. spellings such as “centre” and “colour.” [Scope] S or T [Notes] This value can be used for spelling errors only if they relate specifically to locale expectations (e.g., a text consistently uses British instead of U.S. spellings for a text intended for the U.S.). If these errors are not systematic (e.g., a text uses U.S. spellings but has a single instance of “centre”), they are instead to be counted as spelling errors. [Value]

Output: locale-violation

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The text contains stylistic errors. [Example] Company style guidelines dictate that all individuals be referred to as Mr. or Ms. with a family name, but the text refers to “Jack Smith”. [Scope] S or T [Value]

Output: style

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The text contains characters that are garbled or incorrect or that are not used in the language in which the content appears. [Example] A text ought to have a '•' but instead has a '¥' sign. A German text erroneously uses û, ô, and â instead of the appropriate 'ü', 'ö', and 'ä'. A Japanese text has been garbled and appears with Devanagari characters. [Scope] S or T [Notes] Characters ought to be used in cases of garbling or systematic use of inappropriate characters, not for spelling issues where individual characters are replaced with incorrect one. [Value]

Output: characters

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The text contains a misspelling. [Example] A German text misspells the word "Zustellung" as "Zustlelung". [Scope] S or T [Value]

Output: misspelling

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The text has typographical errors such as omitted/incorrect punctuation, incorrect capitalization, etc. [Example] An English text has the following sentence: "The man whom, we saw, was in the Military and carried it's insignias". [Scope] S or T [Value]

Output: typographical

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The text is formatted incorrectly. [Example] Warnings in the text are supposed to be set in italic face, but instead appear in bold face. Margins of the text are narrower than specified. [Scope] S or T [Value]

Output: formatting

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The source and target text contain different named entities (dates, times, place names, individual names, etc.) [Example] The name "Thaddeus Cahill" appears in an English source but is rendered as "Tamaš Cahill" in the Czech version. The date "February 9, 2007" appears in the source but the translated text has "2. September 2007". [Scope] S or T [Value]

Output: inconsistent-entities

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] Numbers are inconsistent between source and target. [Example] A source text states that an object is 120 cm long, but the target text says that it is 129 cm. long. [Scope] S or T [Notes] Some tools may correct for differences in units of measurement to reduce false positives (e.g., a tool might adjust for differences in values between inches and centimeters to avoid flagging numbers that seem to be different but are in fact equivalent). [Value]

Output: numbers

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] There is an issue related to markup or a mismatch in markup between source and target. [Example] The source segment has five markup tags but the target has only two. An opening tag in the text is missing a closing tag. [Scope] S or T [Value]

Output: markup

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The text fails to match a pattern that defines allowable content (or matches one that defines non-allowable content). [Example] The tool disallows the regular expression pattern ['"”’][\.,] but the translated text contains "A leading “expert”, a political hack, claimed otherwise." A tool uses a regular expression to ensure that the content of an element is an IRI and flags what appears to be a malformed IRI. [Scope] S or T [Notes] Defining what is or is not an allowable pattern is up to the processing application and is beyond the scope of this specification. Best practice would be to use the Comment attribute to specify the pattern that led to the issue. [Value]

Output: pattern-problem

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] There is a mismatch in whitespace between source and target content or the text violates specific rules related to the use of whitespace. [Example] A source segment starts with six space characters but the corresponding target segment has two non-breaking spaces at the start. The text uses a run of 12 space characters instead of a tab character to align numbers in a table. Two space characters appear after a period even though only a single space is to be used. [Scope] S or T [Value]

Output: whitespace

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] There is an issue related to the internationalization of content. [Example] A line of programming code has embedded language-specific strings. A user interface element leaves no room for text expansion. A form allows only for U.S.-style postal addresses and expects five digit U.S. ZIP codes. [Scope] S or T [Notes] There are many kinds of internationalization issues. This value is therefore very heterogeneous in what it can refer to. [Value]

Output: internationalization

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] There is a significant difference in source and target length. [Example] The translation of a segment is five times as long as the source. [Scope] S or T [Notes] What constitutes a "significant" difference in length is determined by the model referred to in the locQualityIssueProfileRef. [Value]

Output: length

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The content is deemed to show poor statistical conformance to a reference corpus. Higher severity values reflect poorer conformance. [Example] The sentence "The harbour connected which to printer is busy or configared not properly." would have poor conformance. [Scope] S or T [Notes] Non-conformance is determined through the use of multiple statistical measures of similarity to a corpus of known-good content. For example, in a system that uses classification techniques the poor conformance might be a function of combined incorrect terminology, wrong spelling and bad grammar, or other features as determined by the system. [Value]

Output: non-conformance

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] The issue either has not been categorized or cannot be categorized. [Example] A new version of a tool returns information on an issue that has not been previously checked and that is not yet classified. A text is defective in ways that defy categorization, such as the appearance of nonsense garbled text of unknown origin (e.g., a translation shows an unintelligible result and/or appears unrelated to the source material). [Scope] S or T [Notes] This value has the following uses: A tool can use it to pass through quality data from another tool in cases where the issues from the other tool are not classified (for example, a localization quality assurance tool interfaces with a third-party grammar checker). A tool’s issues are not yet assigned to values, and, until an updated assignment is made, they may be listed as uncategorized. In this case it is recommended that issues be assigned to appropriate values as soon as possible since uncategorized does not foster interoperability. uncategorized can be used where a portion of text is defective in a way that defies assignment to a value in either the originating system or in any other ITS localization quality markup to indicate that it is uncategorizable. [Value]

Output: uncategorized

Internationalization Tag Set (ITS) Version 2.0


Input: [Description] Any issue that cannot be assigned to any values listed above. [Scope] S or T [Notes] This value allows for the inclusion of any issues not included in the previously listed values. It is encouraged not to use this value for any tool- or model-specific issues that can be mapped to the values listed above. In addition, this value is not synonymous with uncategorized in that uncategorized issues may be assigned to another precise value, while other issues cannot. If a system has an "miscellaneous" or "other" value, it is better to map this to this value even if the specific instance of the issue might be mapped to another value. [Value]

Output: other

Internationalization Tag Set (ITS) Version 2.0


Input: [Property] break-after [Values] auto | always | avoid | left | right | page | column | region | avoid-page | avoid-column | avoid-region [Applies to] block-level elements [Inh.] no [Percentages] N/A [Media] visual [Initial]

Output: auto


Input: [Property] break-before [Values] auto | always | avoid | left | right | page | column | region | avoid-page | avoid-column | avoid-region [Applies to] block-level elements [Inh.] no [Percentages] N/A [Media] visual [Initial]

Output: auto


Input: [Property] break-inside [Values] auto | avoid | avoid-page | avoid-column | avoid-region [Applies to] block-level elements [Inh.] no [Percentages] N/A [Media] visual [Initial]

Output: auto


Input: [Property] flow-from [Values] | none | inherit [Applies to] Non-replaced block containers. This might be expanded in future versions of the specification to allow other types of containers to receive flow content. [Inh.] no [Percentages] N/A [Media] visual [Initial]


Input: [Property] flow-into [Values] none | [element|content]? [Applies to] All elements, but not pseudo-elements such as ::first-line, ::first-letter, ::before or ::after. [Inh.] no [Percentages] N/A [Media] visual [Initial]


Input: [Property] region-fragment [Values] auto | break [Applies to] CSS Regions [Inh.] no [Percentages] N/A [Media] visual [Initial]

Output: auto


Input: [Term Name] Deployment [Type] class [Definition] The ongoing Process of Entities (for the purposes of this ontology, mainly sensors) deployed for a particular purpose. For example, a particular Sensor deployed on a Platform, or a whole network of Sensors deployed for an observation campaign. The deployment may have sub processes, such as installation, maintenance, addition, and decomissioning and removal. [Module]

Output: Deployment


Input: [Term Name] DeploymentRelatedProcess [Type] class [Definition] Place to group all the various Processes related to Deployment. For example, as well as Deplyment, installation, maintenance, deployment of further sensors and the like would all be classified under DeploymentRelatedProcess. [Module]

Output: Deployment


Input: [Term Name] deployedOnPlatform [Type] property [Definition] Relation between a deployment and the platform on which the system was deployed. [Module]

Output: Deployment


Input: [Term Name] deployedSystem [Type] property [Definition] Relation between a deployment and the deployed system. [Module]

Output: Deployment


Input: [Term Name] deploymentProcessPart [Type] property [Definition] Has part relation between a deployment process and its constituent processes. [Module]

Output: Deployment


Input: [Term Name] hasDeployment [Type] property [Definition] Relation between a System and a Deployment, recording that the System/Sensor was deployed in that Deployment. [Module]

Output: Deployment


Input: [Term Name] inDeployment [Type] property [Definition] Relation between a Platform and a Deployment, recording that the object was used as a platform for a system/sensor for a particular deployment: as in this PhysicalObject is acting as a Platform inDeployment Deployment. [Module]

Output: Deployment


Input: [Term Name] Platform [Type] class [Definition] An Entity to which other Entities can be attached - particuarly Sensors and other Platforms. For example, a post might act as the Platform, a bouy might act as a Platform, or a fish might act as a Platform for an attached sensor. [Module]

Output: PlatformSite


Input: [Term Name] attachedSystem [Type] property [Definition] Relation between a Platform and any Systems (e.g., Sensors) that are attached to the Platform. [Module]

Output: PlatformSite


Input: [Term Name] onPlatform [Type] property [Definition] Relation between a System (e.g., a Sensor) and a Platform. The relation locates the sensor relative to other described entities entities: i.e., the Sensor s1's location is Platform p1. More precise locations for sensors in space (relative to other entities, where attached to another entity, or in 3D space) are made using DOLCE's Regions (SpaceRegion). [Module]

Output: PlatformSite


Input: [Term Name] MaintenanceSchedule [Type] class [Definition] Schedule of maintenance for a system/sensor in the specified conditions. [Module]

Output: OperatingRestriction


Input: [Term Name] OperatingProperty [Type] class [Definition] An identifiable characteristic of the environmental and other conditions in which the sensor is intended to operate. May include power ranges, power sources, standard configurations, attachments and the like. [Module]

Output: OperatingRestriction


Input: [Term Name] OperatingRange [Type] class [Definition] The environmental conditions and characteristics of a system/sensor's normal operating environment. Can be used to specify for example the standard environmental conditions in which the sensor is expected to operate (a Condition with no OperatingProperty), or how the environmental and other operating properties relate: i.e., that the maintenance schedule or power requirements differ according to the conditions. [Module]

Output: OperatingRestriction


Input: [Term Name] SurvivalProperty [Type] class [Definition] An identifiable characteristic that represents the extent of the sensors useful life. Might include for example total battery life or number of recharges, or, for sensors that are used only a fixed number of times, the number of observations that can be made before the sensing capability is depleted. [Module]

Output: OperatingRestriction


Input: [Term Name] SurvivalRange [Type] class [Definition] The conditions a sensor can be exposed to without damage: i.e., the sensor continues to operate as defined using MeasurementCapability. If, however, the SurvivalRange is exceeded, the sensor is 'damaged' and MeasurementCapability specifications may no longer hold. [Module]

Output: OperatingRestriction


Input: [Term Name] SystemLifetime [Type] class [Definition] Total useful life of a sensor/system (expressed as total life since manufacture, time in use, number of operations, etc.). [Module]

Output: OperatingRestriction


Input: [Term Name] hasOperatingProperty [Type] property [Definition] Relation from an OperatingRange to a Property. For example, to a battery lifetime. [Module]

Output: OperatingRestriction


Input: [Term Name] hasOperatingRange [Type] property [Definition] Relation from a System to an OperatingRange describing the normal operating environment of the System. [Module]

Output: OperatingRestriction


Input: [Term Name] hasSurvivalProperty [Type] property [Definition] Relation from a SurvivalRange to a Property describing the survial range of a system. For example, to the temperature extreme that a system can withstand before being considered damaged. [Module]

Output: OperatingRestriction


Input: [Term Name] hasSurvivalRange [Type] property [Definition] A Relation from a System to a SurvivalRange. [Module]

Output: OperatingRestriction


Input: [media type] xml-stylesheet PI and link [text/html] recognized as HTML [application/xhtml+xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [application/xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [text/xml]

Output: recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


Input: [media type] link only [text/html] recognized as HTML [application/xhtml+xml] recognized as XML, linked style sheet was not recognized and document tree was rendered [application/xml] recognized as XML, linked style sheet was not recognized and document tree was rendered [text/xml]

Output: recognized as XML, linked style sheet was not recognized and document tree was rendered

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


Input: [media type] xml-stylesheet PI only [text/html] recognized as HTML, xml-stylesheet PI was not recognized [application/xhtml+xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [application/xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [text/xml]

Output: recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


Input: [media type] without xmlns [text/html] recognized as HTML [application/xhtml+xml] recognized as XML, parsing failed due to the omitted namespace declaration [application/xml] recognized as XML, parsing failed due to the omitted namespace declaration [text/xml]

Output: recognized as XML, parsing failed due to the omitted namespace declaration

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


Input: [media type] without DOCTYPE [text/html] recognized as HTML [application/xhtml+xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [application/xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [text/xml]

Output: recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


Input: [media type] without DOCTYPE and xmlns [text/html] recognized as HTML [application/xhtml+xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively and inline style (incorrectly) worked [application/xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively and inline style (incorrectly) worked [text/xml]

Output: recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively and inline style (incorrectly) worked

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


Input: [media type] Broken XHTML [text/html] recognized as HTML, well-formedness error was not detected [application/xhtml+xml] showed blank page [application/xml] showed blank page [text/xml]

Output: showed blank page

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


Input: [media type] HTML 4 [text/html] recognized as HTML [application/xhtml+xml] failed correctly while parsing the DTD [application/xml] failed correctly while parsing the DTD [text/xml]

Output: failed correctly while parsing the DTD

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


Input: [0] doctype [1] ro attribute [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] implementation [1] ro attribute [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] documentElement [1] ro attribute [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createElement [1] method [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createDocumentFragment [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createTextNode [1] method [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createComment [1] method [3] no [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createCDATASection [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createProcessingInstruction [1] method [3] no [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createAttribute [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createEntityReference [1] method [3] no [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementsByTagName [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] importNode [1] method [3] no [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createElementNS [1] method [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createAttributeNS [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementsByTagNameNS [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementById [1] method [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] The cells in [1] this table [2]

Output: should go


Input: [0] green when [1] you hover [2]

Output: the pointing


Input: [0] The rows in [1] this table [2]

Output: should go


Input: [0] dark green [1] when the [2]

Output: pointing device


Input: [0] is over the [1] five pixel [2]

Output: border spacing


Input: [0] Including here, [2]

Output: blank cells.


Input: [Data category] Translate [Local Usage] Yes [Global, rule-based selection] Yes No [Default Values] translate="yes" for elements, and translate="no" for attributes Textual content of element, including content of child elements, but excluding attributes [XML examples] local, global [HTML5 examples] local, global [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Localization Note [Local Usage] Yes [Global, rule-based selection] Yes Yes [Default Values] None Textual content of element, including content of child elements, but excluding attributes [XML examples] local, global [HTML5 examples] local, global [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Terminology [Local Usage] Yes [Global, rule-based selection] Yes Yes [Default Values] term="no" None [XML examples] local, global [HTML5 examples] local, global [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Directionality [Local Usage] Yes [Global, rule-based selection] Yes No [Default Values] dir="ltr" Textual content of element, including attributes and child elements [XML examples] local, global [HTML5 examples] tbd [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Ruby [Local Usage] Yes [Global, rule-based selection] Yes Yes [Default Values] None None [XML examples] local, global [HTML5 examples] tbd [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Language Information [Local Usage] No [Global, rule-based selection] Yes Yes [Default Values] None Textual content of element, including attributes and child elements [XML examples] global [HTML5 examples] global [Global adding of information]

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Elements Within Text [Local Usage] Yes [Global, rule-based selection] Yes No [Default Values] withinText="no" None [XML examples] local, global [HTML5 examples] local, global [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Domain [Local Usage] No [Global, rule-based selection] Yes Yes [Default Values] None Textual content of element, including attributes and child elements [XML examples] global [HTML5 examples] global [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Disambiguation [Local Usage] Yes [Global, rule-based selection] Yes Yes [Default Values] None None [XML examples] local [HTML5 examples] local, global [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Locale Filter [Local Usage] Yes [Global, rule-based selection] Yes No [Default Values] localeFilterList="*" Textual content of element, including attributes and child elements [XML examples] local, global [HTML5 examples] local, global [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Translation Agent Provenance [Local Usage] Yes [Global, rule-based selection] Yes Yes [Default Values] None Textual content of element, including child elements, but excluding attributes [XML examples] tbd [HTML5 examples] tbd [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] External Resource [Local Usage] No [Global, rule-based selection] Yes Yes [Default Values] None None [XML examples] global [HTML5 examples] global [Global adding of information]

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Target Pointer [Local Usage] No [Global, rule-based selection] Yes Yes [Default Values] None None [XML examples] global [HTML5 examples] global [Global adding of information]

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Id Value [Local Usage] No [Global, rule-based selection] Yes Yes [Default Values] None None [XML examples] global [HTML5 examples] global [Global adding of information]

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Preserve Space [Local Usage] Yes [Global, rule-based selection] Yes No [Default Values] default Textual content of element, including attributes and child elements [XML examples] local, global [HTML5 examples] n/a [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Localization Quality Issue [Local Usage] Yes [Global, rule-based selection] Yes Yes [Default Values] None Textual content of element, including child elements, but excluding attributes [XML examples] tbd [HTML5 examples] tbd [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Localization Quality Précis [Local Usage] Yes [Global, rule-based selection] Yes Yes [Default Values] None Textual content of element, including child elements, but excluding attributes [XML examples] tbd [HTML5 examples] tbd [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] MT Confidence [Local Usage] Yes [Global, rule-based selection] Yes No [Default Values] None Textual content of element, including child elements, but excluding attributes [XML examples] tbd [HTML5 examples] tbd [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Allowed Characters [Local Usage] Yes [Global, rule-based selection] Yes Yes [Default Values] None Textual content of element, including child elements, but excluding attributes [XML examples] tbd [HTML5 examples] tbd [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Storage Size [Local Usage] Yes [Global, rule-based selection] Yes Yes [Default Values] storageEncoding="UTF-8" None [XML examples] tbd [HTML5 examples] tbd [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Feature] The use of the role attribute with the value presentation [Indication]

Output: Probably a layout table


Input: [Feature] The use of the border attribute with the non-conforming value 0 [Indication]

Output: Probably a layout table


Input: [Feature] The use of the non-conforming cellspacing and cellpadding attributes with the value 0 [Indication]

Output: Probably a layout table


Input: [Feature] The use of caption, thead, or th elements [Indication]

Output: Probably a non-layout table


Input: [Feature] The use of the headers and scope attributes [Indication]

Output: Probably a non-layout table


Input: [Feature] The use of the border attribute with a value other than 0 [Indication]

Output: Probably a non-layout table


Input: [Feature] Explicit visible borders set using CSS [Indication]

Output: Probably a non-layout table


Input: [Feature] The use of the summary attribute [Indication]

Output: Not a good indicator (both layout and non-layout tables have historically been given this attribute)


Input: [Test Case] 8.1.a [Link To Spec] 8.1 [Normative for XForms Basic] false [Normative for XForms Full] false [Description]

Output: navindex and accesskey attributes


Input: [Test Case] 8.1.1.a [Link To Spec] 8.1.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: form control violates data binding restriction


Input: [Test Case] 8.1.1.b [Link To Spec] 8.1.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: non-relevant form control becoming relevant


Input: [Test Case] 8.1.1.c [Link To Spec] 8.1.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: relevant form control becoming non-relevant


Input: [Test Case] 8.1.2.a [Link To Spec] 8.1.2 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: incremental attribute for input element


Input: [Test Case] 8.1.2.b [Link To Spec] 8.1.2 [Normative for XForms Basic] false [Normative for XForms Full] true [Description]

Output: data binding restrictions for input element


Input: [Test Case] 8.1.2.c [Link To Spec] 8.1.2 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: input bound to different data node types


Input: [Test Case] 8.1.3.a [Link To Spec] 8.1.3 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: incremental attribute for secret element


Input: [Test Case] 8.1.3.b [Link To Spec] 8.1.3 [Normative for XForms Basic] false [Normative for XForms Full] true [Description]

Output: data binding restrictions for secret element


Input: [Test Case] 8.1.4.a [Link To Spec] 8.1.4 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: incremental attribute for textarea element


Input: [Test Case] 8.1.4.b [Link To Spec] 8.1.4 [Normative for XForms Basic] false [Normative for XForms Full] true [Description]

Output: data binding restrictions for textarea element


Input: [Test Case] 8.1.5.a [Link To Spec] 8.1.5 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: appearance attribute for output element has no affect


Input: [Test Case] 8.1.5.b [Link To Spec] 8.1.5 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: value attribute for output element


Input: [Test Case] 8.1.6.a [Link To Spec] 8.1.6 [Normative for XForms Basic] false [Normative for XForms Full] false [Description]

Output: mediatype attribute of upload element


Input: [Test Case] 8.1.6.b [Link To Spec] 8.1.6 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: incremental attribute of upload element


Input: [Test Case] 8.1.6.c [Link To Spec] 8.1.6 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: filename and mediatype element for upload element


Input: [Test Case] 8.1.6.d [Link To Spec] 8.1.6 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: data binding restrictions for upload element


Input: [Test Case] 8.1.6.e [Link To Spec] 8.1.6 [Normative for XForms Basic] false [Normative for XForms Full] true [Description]

Output: implementation for base64Binary, hexBinary, and anyURI of upload element


Input: [Test Case] 8.1.7.a [Link To Spec] 8.1.7 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: start attribute of range element


Input: [Test Case] 8.1.7.b [Link To Spec] 8.1.7 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: end attribute of range element


Input: [Test Case] 8.1.7.c [Link To Spec] 8.1.7 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: step attribute of range element


Input: [Test Case] 8.1.7.d [Link To Spec] 8.1.7 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: incremental attribute for range element


Input: [Test Case] 8.1.7.e [Link To Spec] 8.1.7 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: example of range element


Input: [Test Case] 8.1.7.f [Link To Spec] 8.1.7 [Normative for XForms Basic] false [Normative for XForms Full] true [Description]

Output: data binding restrictions for range element


Input: [Test Case] 8.1.7.g [Link To Spec] 8.1.7 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: data binding restrictions on range element for basic processors


Input: [Test Case] 8.1.8.a [Link To Spec] 8.1.8 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: trigger generates a DOMActivate event on the formcontrol


Input: [Test Case] 8.1.9.a [Link To Spec] 8.1.9 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: data binding restrictions for submit element


Input: [Test Case] 8.1.10.a [Link To Spec] 8.1.10 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: selection attribute of the select element


Input: [Test Case] 8.1.10.b [Link To Spec] 8.1.10 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: incremental attribute for select element


Input: [Test Case] 8.1.10.c [Link To Spec] 8.1.10 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: appearance attribute for select element


Input: [Test Case] 8.1.10.d [Link To Spec] 8.1.10 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: selection does not have a match, out-of-range condition


Input: [Test Case] 8.1.11.a [Link To Spec] 8.1.11 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: selection attribute of the select1 element


Input: [Test Case] 8.1.11.b [Link To Spec] 8.1.11 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: incremental attribute for the select1 element


Input: [Test Case] 8.1.11.c [Link To Spec] 8.1.11 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: appearance attribute for the select1 element


Input: [Test Case] 8.1.11.d [Link To Spec] 8.1.11 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: selection does not have a match, value out-of-rangecondition


Input: [Test Case] 8.2.1.a [Link To Spec] 8.2.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: choices element


Input: [Test Case] 8.2.2.a [Link To Spec] 8.2.2 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: item element


Input: [Test Case] 8.2.3.a [Link To Spec] 8.2.3 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: data binding restrictions for value element


Input: [Test Case] 8.2.3.b [Link To Spec] 8.2.3 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: ref attribute has precedence over inline content invalue element


Input: [Test Case] 8.3.1.a [Link To Spec] 8.3.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: filename element


Input: [Test Case] 8.3.2.a [Link To Spec] 8.3.2 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: mediatype element


Input: [Test Case] 8.3.3.a [Link To Spec] 8.3.3 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: linking attributes in label element


Input: [Test Case] 8.3.3.b [Link To Spec] 8.3.3 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: source precedence for label element


Input: [Test Case] 8.3.3.c [Link To Spec] 8.3.3 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: bind precedence for label element


Input: [Test Case] 8.3.4.a [Link To Spec] 8.3.4 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: linking attributes in help element


Input: [Test Case] 8.3.4.b [Link To Spec] 8.3.4 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: source attribute precedence for help element


Input: [Test Case] 8.3.4.c [Link To Spec] 8.3.4 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: bind attribute precedence for help element


Input: [Test Case] 8.3.5.a [Link To Spec] 8.3.5 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: linking attributes in hint element


Input: [Test Case] 8.3.5.b [Link To Spec] 8.3.5 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: src attribute precedence for hint element


Input: [Test Case] 8.3.5.c [Link To Spec] 8.3.5 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: bind attr precedence for hint element


Input: [Test Case] 8.3.6.a [Link To Spec] 8.3.6 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: valid external alert message


Input: [Test Case] 8.3.6.b [Link To Spec] 8.3.6 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: invalid external alert message


Input: [Test Case] 8.3.6.c [Link To Spec] 8.3.6 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: bind precedence for alert element


Input: [Section] Terminology [Feature/Operation] propID [Key Word] MUST

Output: propID uniquely identifies any privacy proposal

Explanation (or Implication if not supported)


Input: [Section] Data transport [Feature/Operation] the HTML LINK tag [Key Word] MUST

Output: agents and services must be able to locate a proposal in this location

Explanation (or Implication if not supported)


Input: [Feature/Operation] the HTTP extension mechanism [Key Word] MUST

Output: agents and services must be able to locate a proposal in this location

Explanation (or Implication if not supported)


Input: [Section] XML/RDF encoding [Feature/Operation] XML parsing [Key Word] MUST

Output: proposals and data syntax are readily processed or presented to the user. The RDF data model was used to structure the required grammar/syntax but applications need not support RDF if they do not want to take advantage of the RDF data model.

Explanation (or Implication if not supported)


Input: [Section] XML/RDF encoding [Feature/Operation] Full XML and XML-namespace support [Key Word] MUST

Output: implementations must support full XML and namespaces, not just that used here.

Explanation (or Implication if not supported)


Input: [Section] Data References [Feature/Operation] base data reference syntax [Key Word] MUST

Output: agents must be able to understand that syntax of solicited information

Explanation (or Implication if not supported)


Input: [Section] Harmonized Vocab [Feature/Operation] harmonized vocabulary [Key Word] MUST

Output: see the harmonized vocabulary [HARMV] for requirements; they must be followed otherwise the implementation abuses consensus on adequate levels of privacy disclosure

Explanation (or Implication if not supported)


Input: [Section] Reason Codes [Feature/Operation] (OK, SRY-, ERR-, SRY, ERR) [Key Word] MUST

Output: necessary for reaching agreement.

Explanation (or Implication if not supported)


Input: [Feature/Operation] propID repository [Key Word] SHOULD

Output: full proposals can be compactly represented, new negotiation and agreement are not necessary if an agreement already exists.

Explanation (or Implication if not supported)


Input: [Feature/Operation] data repository [Key Word] MAY

Output: frequently requested user profile information is stored and managed by the user.

Explanation (or Implication if not supported)


Input: [Section] Data Definitions [Feature/Operation] new schema instantiation [Key Word] MAY

Output: schemas other than the base set can be instantiated and supported by the agent.

Explanation (or Implication if not supported)


Input: [Section] Source Attribute [Feature/Operation] source attributes "matched-form" and "extension" [Key Word] MAY

Output: agents support multiple, extensible mechanisms by which information is solicited.

Explanation (or Implication if not supported)


Input: [Life Cycle Event] NewContextRequest [Component Implementation]

Output: (Standard) The component requests a new context from the IM. Example:


Input: [Life Cycle Event] NewContextResponse [Component Implementation]

Output: (Standard) The component starts a new context and assigns the new context id to it.


Input: [Life Cycle Event] PrepareRequest [Component Implementation]

Output: The component does not take any action on a PrepareRequest.


Input: [Life Cycle Event] PrepareResponse [Component Implementation]

Output: The component does not send a PrepareResponse.


Input: [Life Cycle Event] StartRequest [Component Implementation]

Output: The component starts processing of the document referenced by contentURL Example:


Input: [Life Cycle Event] StartResponse [Component Implementation]

Output: (Standard)


Input: [Life Cycle Event] DoneNotification [Component Implementation]

Output: Not used by the modality component.


Input: [Life Cycle Event] CancelRequest [Component Implementation]

Output: This component cannot cancel.


Input: [Life Cycle Event] CancelResponse [Component Implementation]

Output: The component does not send a CancelResponse.


Input: [Life Cycle Event] PauseRequest [Component Implementation]

Output: This component cannot pause.


Input: [Life Cycle Event] PauseResponse [Component Implementation]

Output: The component does not send a PauseResponse.


Input: [Life Cycle Event] ResumeRequest [Component Implementation]

Output: This component cannot resume.


Input: [Life Cycle Event] ResumeResponse [Component Implementation]

Output: The component does not send a ResumeResponse.


Input: [Life Cycle Event] ExtensionNotification (focus) [Component Implementation]

Output: The component sends an “ExtensionNotification” lifecycle event to the IM when an input field gets focus. The attribute “id” contains the elements ID within the HTML document. Example:


Input: [Life Cycle Event] ExtensionNotification (click) [Component Implementation]

Output: The component sends an “ExtensionNotification” lifecycle event to the IM when a button was clicked. The attribute “id” contains the buttons ID within the HTML document. Example:


Input: [Life Cycle Event] ExtensionNotification (change) [Component Implementation]

Output: The component sends an “ExtensionNotification” lifecycle event to the IM when the content of an input field was changed. This event will not be sent until the input field loses focus. The attribute “id” contains the input fields ID within the HTML document. Example:


Input: [Life Cycle Event] ExtensionNotification (setValue) [Component Implementation]

Output: The IM can send an “ExtensionNotification” lifecycle event to the modality component to set a value of an input field. The attribute “id” must contain ID of the HTML element. Example:


Input: [Life Cycle Event] ExtensionNotification (setFocus) [Component Implementation]

Output: The IM can send an “ExtensionNotification” lifecycle event to the modality component to set the focus of an input field. The attribute “id” must contain ID of the HTML element. Example:


Input: [Life Cycle Event] ClearContextRequest [Component Implementation]

Output: (Standard)


Input: [Life Cycle Event] clearContextResponse [Component Implementation]

Output: (Standard)


Input: [Life Cycle Event] StatusRequest [Component Implementation]

Output: The component does not take any action on a StatusRequest.


Input: [Life Cycle Event] StatusResponse [Component Implementation]

Output: The component does not take any action on a StatusRequest.


Input: [Section] Terminology [Feature/Operation] propID propID uniquely identifies any privacy proposal [Key Word]

Output: MUST


Input: [Section] Data transport [Feature/Operation] the HTML LINK tag agents and services must be able to locate a proposal in this location [Key Word]

Output: MUST


Input: [Feature/Operation] the HTTP extension mechanism agents and services must be able to locate a proposal in this location [Key Word]

Output: MUST


Input: [Section] XML/RDF encoding [Feature/Operation] XML parsing proposals and data syntax are readily processed or presented to the user. The RDF data model was used to structure the required grammar/syntax but applications need not support RDF if they do not want to take advantage of the RDF data model. [Key Word]

Output: MUST


Input: [Section] XML/RDF encoding [Feature/Operation] Full XML and XML-namespace support implementations must support full XML and namespaces, not just that used here. [Key Word]

Output: MUST


Input: [Section] Data References [Feature/Operation] base data reference syntax agents must be able to understand that syntax of solicited information [Key Word]

Output: MUST


Input: [Section] Harmonized Vocab [Feature/Operation] harmonized vocabulary see the harmonized vocabulary [HARMV] for requirements; they must be followed otherwise the implementation abuses consensus on adequate levels of privacy disclosure [Key Word]

Output: MUST


Input: [Section] Reason Codes [Feature/Operation] (OK, SRY-, ERR-, SRY, ERR) necessary for reaching agreement. [Key Word]

Output: MUST