Input: [User group] Authoring tool developers [Web experience] high [HTML knowledge] high [Disability knowledge] low [Web accessibility knowledge] low [Frequency of use *] daily for a month or so, then a couple times per month [Category]

Output: Tool developers


Input: [User group] User agent developers [Web experience] high [HTML knowledge] high [Disability knowledge] low [Web accessibility knowledge] low [Frequency of use *] daily for a month or so, then a couple times per month [Category]

Output: Tool developers


Input: [User group] Assistive technology developers [Web experience] low-high [HTML knowledge] often low [Disability knowledge] usually high in one area [Web accessibility knowledge] low-high [Frequency of use *] daily for a month or so, then a couple times per month [Category]

Output: Tool developers


Input: [User group] Web evaluation tool developers [Web experience] high [HTML knowledge] high [Disability knowledge] low-high [Web accessibility knowledge] high [Frequency of use *] several times per week in spurts [Category]

Output: Tool developers


Input: [User group] IT/ICT manager, CIO (or similar management role) [Web experience] high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Managers and assistants


Input: [User group] assistant to IT/ICT manager or CIO [Web experience] medium-high [HTML knowledge] mostly low, some medium [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts [Category]

Output: Managers and assistants


Input: [User group] product manager (most likely to "feel the heat" for accessibility) [Web experience] mostly high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day at first, then seldom [Category]

Output: Managers and assistants


Input: [User group] project manager (e.g., managing one aspect of a Web application) [Web experience] mostly high [HTML knowledge] mostly high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day at first, then seldom [Category]

Output: Managers and assistants


Input: [User group] other managers, decision makers, influencers, people who pay for accessibilty [Web experience] low - high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day at first, then seldom [Category]

Output: Managers and assistants


Input: [User group] design shop sales/account manager who could/has been asked to include Web accessibility in contract [Web experience] medium-high [HTML knowledge] low-high (mostly medium) [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Related to contracts


Input: [User group] person setting up contract with outside Web design "shop" [Web experience] high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Related to contracts


Input: [User group] person with disability [Web experience] low-high [HTML knowledge] low-high [Disability knowledge] med-high [Web accessibility knowledge] low-high [Frequency of use *] probably only a few times (since not much there for non-webbie) [Category]

Output: Disability focused


Input: [User group] disability organization members, disability rights advocate [Web experience] low - high [HTML knowledge] mostly low, some up to high [Disability knowledge] high [Web accessibility knowledge] low-high (many low) [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Disability focused


Input: [User group] rehabilitation specialist [Web experience] low - high [HTML knowledge] mostly low [Disability knowledge] high [Web accessibility knowledge] low - medium [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Disability focused


Input: [User group] disabilities specialist/liaison/coordinator, e.g., in university or corporate human resources (HR) [Web experience] low - high [HTML knowledge] mostly low [Disability knowledge] medium-high [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts [Category]

Output: Disability focused


Input: [User group] national or international standards developer [Web experience] low-high [HTML knowledge] low-high [Disability knowledge] low-high [Web accessibility knowledge] low-high [Frequency of use *] daily in spurts [Category]

Output: Other


Input: [User group] legislator, government policy maker (or assistant to) [Web experience] medium-high [HTML knowledge] mostly low, some high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Other


Input: [User group] policy maker for specific organization [Web experience] low - high [HTML knowledge] mostly low, some high [Disability knowledge] low - high [Web accessibility knowledge] low - high [Frequency of use *] several times per day in a one time spurt [Category]

Output: Other


Input: [User group] educator (including accessibility in courses) [Web experience] medium-high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Other


Input: [User group] reporter, journalist [Web experience] high [HTML knowledge] low-medium [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a spurt [Category]

Output: Other


Input: [User group] internal public relations or marketing [Web experience] mostly high [HTML knowledge] mostly low [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Other


Input: [User group] researcher, or student doing paper on accessibility [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] low [Frequency of use *] several times per day for a week [Category]

Output: Other


Input: [User group] W3C Team member (non WAI) [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low-medium [Frequency of use *] daily for a week or so, then a couple times per month [Category]

Output: Other


Input: [User group] WAI WG member [Web experience] high [HTML knowledge] mostly high [Disability knowledge] medium-high [Web accessibility knowledge] medium-high [Frequency of use *] several times per day - weekly [Category]

Output: Other


Input: [User group] Web accessibility specialist (consultant, evaluator, trainer) [Web experience] usually high [HTML knowledge] medium-high [Disability knowledge] medium-high [Web accessibility knowledge] medium-high [Frequency of use *] often a couple time per week [Category]

Output: Other


Input: [Category] Web developers and content providers [User group] Web accessibility manager/coordinator, liaison between accessibility group and technical development group [Web experience] high [HTML knowledge] high [Disability knowledge] low - high [Web accessibility knowledge] medium-high [Frequency of use *]

Output: daily for a month or so, then a couple times per month


Input: [Category] Web developers and content providers [User group] Web "coder"/technical developer [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: daily for a month or so, then a couple times per month


Input: [Category] Web developers and content providers [User group] Web interaction designer, usability specialist, application designer [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: daily for a month or so, then a couple times per month


Input: [Category] Web developers and content providers [User group] Web graphic designer [Web experience] high [HTML knowledge] usually high, can be low [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: daily for a week or so, then once per month or so


Input: [Category] Web developers and content providers [User group] Webmaster in small "shop" who performs multiple duties [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: daily for a month or so, then a couple times per month


Input: [Category] Web developers and content providers [User group] Web content provider (non-technical, maybe does not input content directly) [Web experience] low - high [HTML knowledge] low [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: daily for a week or so, then once per month or less


Input: [Category] Web developers and content providers [User group] Internet or intranet site manager [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: daily for a week or so, then once per month or so


Input: [Category] Tool developers [User group] Authoring tool developers [Web experience] high [HTML knowledge] high [Disability knowledge] low [Web accessibility knowledge] low [Frequency of use *]

Output: daily for a month or so, then a couple times per month


Input: [Category] Tool developers [User group] User agent developers [Web experience] high [HTML knowledge] high [Disability knowledge] low [Web accessibility knowledge] low [Frequency of use *]

Output: daily for a month or so, then a couple times per month


Input: [Category] Tool developers [User group] Assistive technology developers [Web experience] low-high [HTML knowledge] often low [Disability knowledge] usually high in one area [Web accessibility knowledge] low-high [Frequency of use *]

Output: daily for a month or so, then a couple times per month


Input: [Category] Tool developers [User group] Web evaluation tool developers [Web experience] high [HTML knowledge] high [Disability knowledge] low-high [Web accessibility knowledge] high [Frequency of use *]

Output: several times per week in spurts


Input: [Category] Managers and assistants [User group] IT/ICT manager, CIO (or similar management role) [Web experience] high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Managers and assistants [User group] assistant to IT/ICT manager or CIO [Web experience] medium-high [HTML knowledge] mostly low, some medium [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts


Input: [Category] Managers and assistants [User group] product manager (most likely to "feel the heat" for accessibility) [Web experience] mostly high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day at first, then seldom


Input: [Category] Managers and assistants [User group] project manager (e.g., managing one aspect of a Web application) [Web experience] mostly high [HTML knowledge] mostly high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day at first, then seldom


Input: [Category] Managers and assistants [User group] other managers, decision makers, influencers, people who pay for accessibilty [Web experience] low - high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day at first, then seldom


Input: [Category] Related to contracts [User group] design shop sales/account manager who could/has been asked to include Web accessibility in contract [Web experience] medium-high [HTML knowledge] low-high (mostly medium) [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Related to contracts [User group] person setting up contract with outside Web design "shop" [Web experience] high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Disability focused [User group] person with disability [Web experience] low-high [HTML knowledge] low-high [Disability knowledge] med-high [Web accessibility knowledge] low-high [Frequency of use *]

Output: probably only a few times (since not much there for non-webbie)


Input: [Category] Disability focused [User group] disability organization members, disability rights advocate [Web experience] low - high [HTML knowledge] mostly low, some up to high [Disability knowledge] high [Web accessibility knowledge] low-high (many low) [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Disability focused [User group] rehabilitation specialist [Web experience] low - high [HTML knowledge] mostly low [Disability knowledge] high [Web accessibility knowledge] low - medium [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Disability focused [User group] disabilities specialist/liaison/coordinator, e.g., in university or corporate human resources (HR) [Web experience] low - high [HTML knowledge] mostly low [Disability knowledge] medium-high [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts


Input: [Category] Other [User group] national or international standards developer [Web experience] low-high [HTML knowledge] low-high [Disability knowledge] low-high [Web accessibility knowledge] low-high [Frequency of use *]

Output: daily in spurts


Input: [Category] Other [User group] legislator, government policy maker (or assistant to) [Web experience] medium-high [HTML knowledge] mostly low, some high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Other [User group] policy maker for specific organization [Web experience] low - high [HTML knowledge] mostly low, some high [Disability knowledge] low - high [Web accessibility knowledge] low - high [Frequency of use *]

Output: several times per day in a one time spurt


Input: [Category] Other [User group] educator (including accessibility in courses) [Web experience] medium-high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Other [User group] reporter, journalist [Web experience] high [HTML knowledge] low-medium [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a spurt


Input: [Category] Other [User group] internal public relations or marketing [Web experience] mostly high [HTML knowledge] mostly low [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Other [User group] researcher, or student doing paper on accessibility [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] low [Frequency of use *]

Output: several times per day for a week


Input: [Category] Other [User group] W3C Team member (non WAI) [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low-medium [Frequency of use *]

Output: daily for a week or so, then a couple times per month


Input: [Category] Other [User group] WAI WG member [Web experience] high [HTML knowledge] mostly high [Disability knowledge] medium-high [Web accessibility knowledge] medium-high [Frequency of use *]

Output: several times per day - weekly


Input: [Category] Other [User group] Web accessibility specialist (consultant, evaluator, trainer) [Web experience] usually high [HTML knowledge] medium-high [Disability knowledge] medium-high [Web accessibility knowledge] medium-high [Frequency of use *]

Output: often a couple time per week


Input: [1] Description [2] Example [3] Scope [4] Notes [0]

Output: Value

Internationalization Tag Set (ITS) Version 2.0


Input: [1] An incorrect term or a term from the wrong domain was used or terms are used inconsistently. [2] The localization had â€œPen Driveâ€ when corporate terminology specified that â€œUSB Stickâ€ was to be used. The localization text inconsistently used "Start" and "Begin". A text renders the Hungarian term recsegÅ‘Ã©k as â€œbuzzer bridgeâ€ in English to translate (a literal translation), but the term used in English should be â€œwedge block,â€ as specified in a terminology list supplied to the translator. [3] S or T [4] This value MUST NOT be used 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 should be 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. [0]

Output: terminology

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The content of the target mistranslates the content of the source. [2] 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...") [3] T [4] Issues related to translation of specific terms related to the domain or task-specific language should be categorized as terminology issues. [0]

Output: mistranslation

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Necessary text has been omitted from the localization or source. [2] One or more segments found in the source that should have been translated are missing in the target. [3] S or T [4] This type should not be used for missing whitespace or formatting codes, but instead should be reserved for linguistic content. [0]

Output: omission

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Content that should have been translated was left untranslated. [2] The source segment reads "The Professor said to Smith that he would hear from his lawyer" but the Hungarian localization reads "A professzor azt modta Smithnek, hogy he would hear from his lawyer." [3] T [4] 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. [0]

Output: untranslated

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The translated text contains inappropriate additions. [2] The translated text contains a note from the translator to himself to look up a term; the note should have been deleted but was not. [3] T [0]

Output: addition

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Content has been duplicated improperly. [2] A section of the target text was inadvertently copied twice in a copy and paste operation. [3] T [0]

Output: duplication

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text is inconsistent with itself (NB: not for use with terminology inconsistency). [2] The text states that an event happened in 1912 in one location but in another states that it happened in 1812. [3] S or T [0]

Output: inconsistency

Internationalization Tag Set (ITS) Version 2.0


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

Output: grammar

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text is legally problematic (e.g., it is specific to the wrong legal system). [2] 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. [3] S or T [0]

Output: legal

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text is written in the wrong linguistic register of uses slang or other language variants inappropriate to the text. [2] A financia financial text in U.S. English refers to dollars as "bucks". [3] S or T [0]

Output: register

Internationalization Tag Set (ITS) Version 2.0


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

Output: locale-specific-content

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Text violates norms for the intended locale. [2] A text localized into German has dates in YYYY-MM-DD format instead of in 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.â€ [3] S or T [4] This category should be used for spelling errors only if they relate specifically to locale expectations (e.g., a text consitently 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 should instead be counted as spelling errors. [0]

Output: locale-violation

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text contains stylistic errors. [2] Company style guidelines dictates that all individuals be referred to as Mr. or Ms. with a family name, but the text refers to â€œJack Smithâ€. [3] S or T [0]

Output: style

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text contains characters that are garbled or incorrect or that are not used in the language in which the content appears. [2] A text should have a 'â€¢' but instead has a 'Â¥' sign. A text translated into German omits the umlauts over 'Ã¼', 'Ã¶', and 'Ã¤'. [3] S or T [0]

Output: characters

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text contains a misspelling. [2] A German text misspells the word "Zustellung" as "ZustellÃ¼ng". [3] S or T [0]

Output: misspelling

Internationalization Tag Set (ITS) Version 2.0


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

Output: typographical

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text is formatted incorrectly. [2] 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. [3] S or T [0]

Output: formatting

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The source and target text contain different named entities (dates, times, place names, individual names, etc.) [2] 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". [3] S or T [0]

Output: inconsistent-entities

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Numbers are inconsistent between source and target. [2] A source text states that an object is 120 cm long, but the target text says it is 129 cm. long. [3] S or T [4] Some tools may correct for differences in units of measurement to reduce false positives. [0]

Output: numbers

Internationalization Tag Set (ITS) Version 2.0


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

Output: markup

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text fails to match a pattern that defines allowable content (or matches one that defines non-allowable content). [2] The tool disallows the regular expression pattern ['"â€â€™][\.,] but the translated text contains "A leading â€œexpertâ€, a political hack, claimed otherwise." [3] S or T [0]

Output: pattern-problem

Internationalization Tag Set (ITS) Version 2.0


Input: [1] There is a mismatch in whitespace between source and target content. content or the text violates specific rules related to the use of whitespace.. [2] 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 period should be used. [3] S or T [0]

Output: whitespace

Internationalization Tag Set (ITS) Version 2.0


Input: [1] There is an issue related to the internationalization of content. [2] 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. [3] S or T [4] There are many kinds of internationalization issues. This category is therefore very heterogeneous in what it can refer to. [0]

Output: internationalization

Internationalization Tag Set (ITS) Version 2.0


Input: [1] There is a significant difference in source and target length. [2] The translation of a segment is five times as long as the source. [3] T or S [4] What constitutes a "significant" difference in length is determined by the model referred to in the locQualityIssueProfileRef . [0]

Output: length

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The issue has not been categorized. [2] A new version of a tool returns information on an issue that has not been previously checked and that is not yet classified. [3] S or T [4] This category has two 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 categories, 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 categories as soon as possible since uncategorized does not foster interoperability. [0]

Output: uncategorized

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Any issue that cannot be assigned to any values listed above. [3] S or T [4] This category allows for the inclusion of any issues not included in the previously listed values. This value MUST NOT be used 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" category, it MUST be mapped to this value even if the specific instance of the issue might be mapped to another category. [0]

Output: other

Internationalization Tag Set (ITS) Version 2.0


Input: 77,000 USD

Output: For-profit organization that has annual gross revenue, as measured by the most recent audited statement, of greater than or equal to 1,000,000,000 USD.

Organization Type in Upper Middle Income Country (World Bank category)


Input: 68,500 USD

Output: For-profit organization that has annual gross revenue, as measured by the most recent audited statement, of greater than or equal to 50,000,000 USD and less than 1,000,000,000 USD.

Organization Type in Upper Middle Income Country (World Bank category)


Input: 34,250 USD

Output: Introductory Industry Membership, available for two years to a for-profit organization that has annual gross revenue, as measured by the most recent audited statement, of greater than or equal to 50,000,000 USD. Participation limited to one Interest Group

Organization Type in Upper Middle Income Country (World Bank category)


Input: 7,900 USD

Output: For-profit organization that has annual gross revenue, as measured by the most recent audited statement, of greater than or equal to 30,000,000 USD and less than 50,000,000 USD.

Organization Type in Upper Middle Income Country (World Bank category)


Input: 2,250 USD

Output: Enterprises and non-profits with 10 or fewer employees, who are not also membership organizations, revenues less than 3,000,000 USD and have never been a W3C Member. This fee only valid for the first two years of W3C Membership.

Organization Type in Upper Middle Income Country (World Bank category)


Input: 3,810 USD

Output: All other organizations, including non-profit organizations and government agencies.

Organization Type in Upper Middle Income Country (World Bank category)


Input: [Postal.] Name. [Type] PersonName. [Short display name] Name [Category]

Output: Physical Contact Information, Demographic and SocioEconomic Data


Input: [Postal.] Street [Type] Text [Short display name] Street Address [Category]

Output: Physical Contact Information


Input: [Postal.] City [Type] Text [Short display name] City [Category]

Output: Physical Contact Information


Input: [Postal.] StateProv [Type] Text [Short display name] State or Province [Category]

Output: Physical Contact Information


Input: [Postal.] PostalCode [Type] Text [Short display name] Postal Code [Category]

Output: Demographic and SocioEconomic Data


Input: [Postal.] CountryCode [Type] Country [Short display name] Country Code [Category]

Output: Demographic and SocioEconomic Data


Input: [Postal.] Country [Type] Text [Short display name] Country Name [Category]

Output: Demographic and SocioEconomic Data


Input: [Postal.] Formatted [Type] Text [Short display name] Formatted Postal Address [Category]

Output: Demographic and SocioEconomic Data


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

Output: alignment

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)

Table 5-1. EXI Options in Options Document


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

Output: compression

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


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

Output: strict

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


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

Output: fragment

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [Description] Specifies whether the support for the preservation of comments, pis, etc. is each enabled [Default Value] all false [EXI Option]

Output: preserve

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [Description] Enables self-contained elements [Default Value] false [EXI Option]

Output: selfContained

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


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

Output: schemaId

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [Description] Specify alternate datatype representations for typed values in the EXI body [Default Value] no default value [EXI Option]

Output: datatypeRepresentationMap

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


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

Output: blockSize

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [Description] Specifies the maximum string length of value content items to be considered for addition to the string table. [Default Value] unbounded [EXI Option]

Output: valueMaxLength

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [Description] Specifies the total capacity of value partitions in a string table [Default Value] unbounded [EXI Option]

Output: valuePartitionCapacity

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [Description] User defined meta-data may be added [Default Value] no default value [EXI Option]

Output: [user defined meta-data]

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [Keyword] hidden [State] Hidden [Control type] n/a [Data type]

Output: An arbitrary string


Input: [Keyword] text [State] Text [Control type] A text field [Data type]

Output: Text with no line breaks


Input: [Keyword] search [State] Search [Control type] Search field [Data type]

Output: Text with no line breaks


Input: [Keyword] tel [State] Telephone [Control type] A text field [Data type]

Output: Text with no line breaks


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

Output: An absolute URL


Input: [Keyword] email [State] E-mail [Control type] A text field [Data type]

Output: An e-mail address or list of e-mail addresses


Input: [Keyword] password [State] Password [Control type] A text field that obscures data entry [Data type]

Output: Text with no line breaks (sensitive information)


Input: [Keyword] date [State] Date [Control type] A date control [Data type]

Output: A date (year, month, day) with no time zone


Input: [Keyword] time [State] Time [Control type] A time control [Data type]

Output: A time (hour, minute, seconds, fractional seconds) with no time zone


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

Output: A numerical value


Input: [Keyword] range [State] Range [Control type] A slider control or similar [Data type]

Output: A numerical value, with the extra semantic that the exact value is not important


Input: [Keyword] color [State] Color [Control type] A color well [Data type]

Output: An sRGB color with 8-bit red, green, and blue components


Input: [Keyword] checkbox [State] Checkbox [Control type] A checkbox [Data type]

Output: A set of zero or more values from a predefined list


Input: [Keyword] radio [State] Radio Button [Control type] A radio button [Data type]

Output: An enumerated value


Input: [Keyword] file [State] File Upload [Control type] A label and a button [Data type]

Output: Zero or more files each with a MIME type and optionally a file name


Input: [Keyword] submit [State] Submit Button [Control type] A button [Data type]

Output: An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission


Input: [Keyword] image [State] Image Button [Control type] Either a clickable image, or a button [Data type]

Output: A coordinate, relative to a particular image's size, with the extra semantic that it must be the last value selected and initiates form submission


Input: [Keyword] reset [State] Reset Button [Control type] A button [Data type]


Input: [Keyword] button [State] Button [Control type] A button [Data type]


Input: [WSML keyword] wsml#variant [WSML keyword_2] wsml#goal [3] Used to define a WSML goal. [1]

Output: Used as predicate to indicate the WSML variant applied.

Table 10.1: WSML vocabulary extending RDFS for WSML triple syntax


Input: [WSML keyword] wsml#ontology [WSML keyword_2] wsml#ooMediator [3] Used to define a WSML ooMediator [1]

Output: Used to define a WSML ontology.


Input: [WSML keyword] wsml#hasConcept [WSML keyword_2] wsml#ggMediator [3] Used to define a WSML ggMediator [1]

Output: Used to type a WSML concept and to bind it to an ontology.


Input: [WSML keyword] wsml#attribute [WSML keyword_2] wsml#wgMediator [3] Used to define a WSML wgMediator [1]

Output: Used to define a WSML attribute


Input: [WSML keyword] wsml#ofType [WSML keyword_2] wsml#wwMediator [3] Used to define a WSML wwMediator [1]

Output: Used as predicate to define constraining attributes and parameters.


Input: [WSML keyword] wsml#hasAttribute [WSML keyword_2] wsml#webService [3] Used to define a WSML webService [1]

Output: Used as predicate to bind an attribute to a concept.


Input: [WSML keyword] wsml#transitiveAttribute [WSML keyword_2] wsml#useInterface [3] Used as predicate to bind an interface to a Web service. [1]

Output: Used to indicate the transitivity of an attribute.


Input: [WSML keyword] wsml#symmetricAttribute [WSML keyword_2] wsml#useCapability [3] Used as predicate to bind a capability to a Web service or goal. [1]

Output: Used to indicate the symmetry of an attribute.


Input: [WSML keyword] wsml#reflexiveAttribute [WSML keyword_2] wsml#sharedVariables [3] Used as predicate to bind a shared variable to a capability. [1]

Output: Used to indicate the reflexivity of an attribute.


Input: [WSML keyword] wsml#inverseOf [WSML keyword_2] wsml#precondition [3] Used to type a precondition and to bind it to a capability. [1]

Output: Used to indicate the inverse relationship of two attributes.


Input: [WSML keyword] wsml#minCardinality [WSML keyword_2] wsml#assumption [3] Used to type an assumption and to bind it to a capability. [1]

Output: Used as predicate to defined the minimal cardinality of an attribute.


Input: [WSML keyword] wsml#maxCardinality [WSML keyword_2] wsml#postcondition [3] Used to type a postcondition and to bind it to a capability. [1]

Output: Used as predicate to defined the maximal cardinality of an attribute.


Input: [WSML keyword] wsml#hasInstance [WSML keyword_2] wsml#effect [3] Used to type an effect and to bind it to a capability. [1]

Output: Used to type an instance and to bind it to a concept.


Input: [WSML keyword] wsml#hasRelation [WSML keyword_2] wsml#choreography [3] Used to type a choreography and to bind it to an interface. [1]

Output: Used to type a relation and to bind it to an ontology.


Input: [WSML keyword] wsml#arity [WSML keyword_2] wsml#orchestration [3] Used to type an orchestration and to bind it to an interface. [1]

Output: Used to define the arity of a WSML relation.


Input: [WSML keyword] wsml#param [WSML keyword_2] wsml#nfp [3] Used to type non-functional properties. [1]

Output: Used to type parameters of WSML relations.


Input: [WSML keyword] wsml#subRelationOf [WSML keyword_2] wsml#importsOntology [3] Used to define the import of an external ontology. [1]

Output: Used as predicate to define sub-relations.


Input: [WSML keyword] wsml#hasRelationInstance [WSML keyword_2] wsml#usesMediator [3] Used to define the use of a mediator. [1]

Output: Used to type a relation instance and to bind it to an ontology.


Input: [WSML keyword] wsml#hasAxiom [1]

Output: Used to type an axiom and to bind it to an ontology.


Input: [Details] Using valid HTML means having an HTML code that follows one of the DTDs of the HTML specification. Your best choice is valid XHTML strict markup: XHTML means that the code will benefit from all the XML power, and strict ensures your site won't mix presentation markup with the structure. [Rationale] Valid HTML code is a first step toward more compatibility with browsers and better rendering on the latest ones. Using only strict HTML (that is, the Strict HTML DTD) makes the site easier to maintain and evolve. [Test tool] The W3C HTML Validator is one of the many options available. The LogValidator is especially helpful in maintaining a valid Web site. [Requirement]

Output: Use valid (X)HTML

Buy standards compliant Web sites — W3C QA


Input: [Details] Avoid any presentational markup and keep all the layout features in well-defined CSS style sheets. [Rationale] Linked style sheets allow presentation to be decoupled completely from the page structure of your site, and lets you quickly change its layout and rendering. It also guarantees that everybody can adjust the rendering to their needs and tastes. [Test tool] The CSS Validator detects any non-compliant use of the CSS technologies. [Requirement]

Output: Use extensively valid CSS

Buy standards compliant Web sites — W3C QA


Input: [Details] Make sure that each page of your site is accessible with a stable address (URL) and that the HTTP caching properties are set correctly. Make sure if you migrate to a new site version that the URLs are either kept as is or at least redirected to the new ones. [Rationale] HTTP is a very powerful protocol and you get most of its power with stable URLs and an efficient caching system: bookmarks and links don't break, network access is faster, users are happy! [Test tool] The W3C Link Checker can provide some help. Besides, the advices given in the Common HTTP Implementation Problems Note can help assess what needs to be respected. [Requirement]

Output: Use HTTP properly

Buy standards compliant Web sites — W3C QA


Input: [Details] Use PNG for raster images, and SVG for all others. [Rationale] PNG is a much more capable format than other binary formats for raster images because it provides better compression, more options, and it's free. The best format you should require is SVG: it's scalable, XML-based, very light, and has a lot of capabilities, for example, animation using SMIL, which is supported on cell phones, etc. [Test tool] N/A [Requirement]

Output: Use SVG and PNG for graphics

Buy standards compliant Web sites — W3C QA


Input: [Details] Details. [Rationale] Making a site accessible benefits all of your users, and broadens your current audience. This requirement may be required by law in some countries. [Test tool] See Evaluation Tools for Web Content Accessibility. [Requirement]

Output: Use techniques to make your content accessible

Buy standards compliant Web sites — W3C QA


Input: [Details] Use the DOM API combined with Ecmascript (but don't make the use of scripts mandatory to navigate in the site!). [Rationale] DOM and Ecmascript (the common standard behind Javascript and JScript) are the best way to go to get interoperable scripts to create animations in your Web site. But do not forget your users that don't have these scripting capacities enabled. [Test tool] N/A [Requirement]

Output: Use standards scripting languages

Buy standards compliant Web sites — W3C QA


Input: [0] Value [1] Description [2] Example [3] Scope [4]

Output: Notes

Internationalization Tag Set (ITS) Version 2.0


Input: [0] terminology [1] An incorrect term or a term from the wrong domain was used or terms are used inconsistently. [2] The localization had â€œPen Driveâ€ when corporate terminology specified that â€œUSB Stickâ€ was to be used. The localization text inconsistently used "Start" and "Begin". A text renders the Hungarian term recsegÅ‘Ã©k as â€œbuzzer bridgeâ€ in English to translate (a literal translation), but the term used in English should be â€œwedge block,â€ as specified in a terminology list supplied to the translator. [3] S or T [4]

Output: This value MUST NOT be used 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 should be 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.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] mistranslation [1] The content of the target mistranslates the content of the source. [2] 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...") [3] T [4]

Output: Issues related to translation of specific terms related to the domain or task-specific language should be categorized as terminology issues.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] omission [1] Necessary text has been omitted from the localization or source. [2] One or more segments found in the source that should have been translated are missing in the target. [3] S or T [4]

Output: This type should not be used for missing whitespace or formatting codes, but instead should be reserved for linguistic content.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] untranslated [1] Content that should have been translated was left untranslated. [2] The source segment reads "The Professor said to Smith that he would hear from his lawyer" but the Hungarian localization reads "A professzor azt modta Smithnek, hogy he would hear from his lawyer." [3] T [4]

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

Internationalization Tag Set (ITS) Version 2.0


Input: [0] locale-specific-content [1] The localization contains content that does not apply to the locale for which it was prepared. [2] A text translated for the Japanese market contains call center numbers in Texas and refers to special offers available only in the U.S. [3] S or T [4]

Output: Legally inappropriate material should be classified as legal .

Internationalization Tag Set (ITS) Version 2.0


Input: [0] locale-violation [1] Text violates norms for the intended locale. [2] A text localized into German has dates in YYYY-MM-DD format instead of in 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.â€ [3] S or T [4]

Output: This category should be used for spelling errors only if they relate specifically to locale expectations (e.g., a text consitently 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 should instead be counted as spelling errors.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] numbers [1] Numbers are inconsistent between source and target. [2] A source text states that an object is 120 cm long, but the target text says it is 129 cm. long. [3] S or T [4]

Output: Some tools may correct for differences in units of measurement to reduce false positives.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] internationalization [1] There is an issue related to the internationalization of content. [2] 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. [3] S or T [4]

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

Internationalization Tag Set (ITS) Version 2.0


Input: [0] length [1] There is a significant difference in source and target length. [2] The translation of a segment is five times as long as the source. [3] T or S [4]

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: [0] uncategorized [1] The issue has not been categorized. [2] A new version of a tool returns information on an issue that has not been previously checked and that is not yet classified. [3] S or T [4]

Output: This category has two 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 categories, 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 categories as soon as possible since uncategorized does not foster interoperability.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] other [1] Any issue that cannot be assigned to any values listed above. [3] S or T [4]

Output: This category allows for the inclusion of any issues not included in the previously listed values. This value MUST NOT be used 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" category, it MUST be mapped to this value even if the specific instance of the issue might be mapped to another category.

Internationalization Tag Set (ITS) Version 2.0


Input: [Part] EventClass [Applies] Globally [Description] Specifies a class of events that span a simulation or simulations. [Type]

Output: Element

SRML - Simulation Reference Markup Language


Input: [Part] Events [Applies] Items [Description] Specifies a collection of events scheduled or posted for an item. [Type]

Output: Element

SRML - Simulation Reference Markup Language


Input: [Part] EventSink [Applies] Globally [Description] Specifies a name and filter for events to be received by an item simulation. [Type]

Output: Element

SRML - Simulation Reference Markup Language


Input: [Part] Item [Applies] Globally [Description] Specifies an item. This is implied by elements in a domain-specific schema and need not be specified. [Type]

Output: Element

SRML - Simulation Reference Markup Language


Input: [Part] ItemClass [Applies] Globally [Description] Specifies a class of items, which all have a similar structure and behavior. [Type]

Output: Element

SRML - Simulation Reference Markup Language


Input: [Part] ItemClasses [Applies] Globally [Description] Specifies a group of item classes. [Type]

Output: Element

SRML - Simulation Reference Markup Language


Input: [Part] ItemEvent [Applies] Events [Description] Specifies the information about an event that has been scheduled or posted to an item. [Type]

Output: Element

SRML - Simulation Reference Markup Language


Input: [Part] JavaScript or text/javascript [Applies] Script Language or Type [Description] Specifies that the script language for an item is JavaScript. [Type]

Output: Value

SRML - Simulation Reference Markup Language


Input: [Part] Link [Applies] Items [Description] Specifies a link (object reference) to another Item. [Type]

Output: Element

SRML - Simulation Reference Markup Language


Input: [Part] Links [Applies] Items [Description] Specifies a collection of individual links. [Type]

Output: Element

SRML - Simulation Reference Markup Language


Input: [Part] LocationFixed [Applies] Items [Description] Specifies that an item is fixed within its location. This makes the item directly accessible to the location through either its ID or its Name whichever takes precedence. If two items have the same ID or name, the last one will become the item that is directly accessible. For example, if "itemname" is location fixed, then it can be accessed through location.itemname. [Type]

Output: Attribute

SRML - Simulation Reference Markup Language


Input: [Part] Name [Applies] Items, ItemClasses [Description] Designates the name for the Item or ItemClass. Name is required for an ItemClass, but not for an Item. [Type]

Output: Attribute

SRML - Simulation Reference Markup Language


Input: [Part] Parameter [Applies] ItemEvent [Description] Specifies an individual event parameter. [Type]

Output: Element

SRML - Simulation Reference Markup Language


Input: [Part] Quantity [Applies] Items [Description] Specifies the number of items to be constructed at the enclosing location. [Type]

Output: Attribute

SRML - Simulation Reference Markup Language


Input: [Part] Script [Applies] Items, ItemClasses [Description] Specifies the script, which defines the state and behavior for items. [Type]

Output: Attribute

SRML - Simulation Reference Markup Language


Input: [Part] Simulation [Applies] Globally [Description] Specifies an individual simulation. [Type]

Output: Element

SRML - Simulation Reference Markup Language


Input: [Part] Simulations [Applies] Globally [Description] Specifies a group of simulations. [Type]

Output: Element

SRML - Simulation Reference Markup Language


Input: [Part] Source [Applies] Globally [Description] Specifies the location of a document or object class that provides an external source of structure and/or behavior for an item. [Type]

Output: Attribute

SRML - Simulation Reference Markup Language


Input: [Part] SuperClasses [Applies] ItemClass [Description] Specifies an ordered sequence of ItemClasses or EventClasses that provide default structure and behavior for the ItemClass or EventClass respectively. Entries specified to the left of other entries have higher priority. [Type]

Output: Attribute

SRML - Simulation Reference Markup Language


Input: [Part] Target [Applies] Link [Description] Specifies the target object of the link. [Type]

Output: Attribute

SRML - Simulation Reference Markup Language


Input: [Part] Type [Applies] Script [Description] Specifies the language that the script uses. The Language attribute is also allowed; however, only one needs to be specified. [Type]

Output: Attribute

SRML - Simulation Reference Markup Language


Input: [Part] VBScript or text/vbscript [Applies] Script Language or Type [Description] Specifies that the script language is VBScript. [Type]

Output: Value

SRML - Simulation Reference Markup Language


Input: [WSML keyword] wsml#variant [1] Used as predicate to indicate the WSML variant applied. [WSML keyword_2] wsml#goal [3]

Output: Used to define a WSML goal.


Input: [WSML keyword] wsml#ontology [1] Used to define a WSML ontology. [WSML keyword_2] wsml#ooMediator [3]

Output: Used to define a WSML ooMediator


Input: [WSML keyword] wsml#hasConcept [1] Used to type a WSML concept and to bind it to an ontology. [WSML keyword_2] wsml#ggMediator [3]

Output: Used to define a WSML ggMediator


Input: [WSML keyword] wsml#attribute [1] Used to define a WSML attribute [WSML keyword_2] wsml#wgMediator [3]

Output: Used to define a WSML wgMediator


Input: [WSML keyword] wsml#ofType [1] Used as predicate to define constraining attributes and parameters. [WSML keyword_2] wsml#wwMediator [3]

Output: Used to define a WSML wwMediator


Input: [WSML keyword] wsml#hasAttribute [1] Used as predicate to bind an attribute to a concept. [WSML keyword_2] wsml#webService [3]

Output: Used to define a WSML webService


Input: [WSML keyword] wsml#transitiveAttribute [1] Used to indicate the transitivity of an attribute. [WSML keyword_2] wsml#useInterface [3]

Output: Used as predicate to bind an interface to a Web service.


Input: [WSML keyword] wsml#symmetricAttribute [1] Used to indicate the symmetry of an attribute. [WSML keyword_2] wsml#useCapability [3]

Output: Used as predicate to bind a capability to a Web service or goal.


Input: [WSML keyword] wsml#reflexiveAttribute [1] Used to indicate the reflexivity of an attribute. [WSML keyword_2] wsml#sharedVariables [3]

Output: Used as predicate to bind a shared variable to a capability.


Input: [WSML keyword] wsml#inverseOf [1] Used to indicate the inverse relationship of two attributes. [WSML keyword_2] wsml#precondition [3]

Output: Used to type a precondition and to bind it to a capability.


Input: [WSML keyword] wsml#minCardinality [1] Used as predicate to defined the minimal cardinality of an attribute. [WSML keyword_2] wsml#assumption [3]

Output: Used to type an assumption and to bind it to a capability.


Input: [WSML keyword] wsml#maxCardinality [1] Used as predicate to defined the maximal cardinality of an attribute. [WSML keyword_2] wsml#postcondition [3]

Output: Used to type a postcondition and to bind it to a capability.


Input: [WSML keyword] wsml#hasInstance [1] Used to type an instance and to bind it to a concept. [WSML keyword_2] wsml#effect [3]

Output: Used to type an effect and to bind it to a capability.


Input: [WSML keyword] wsml#hasRelation [1] Used to type a relation and to bind it to an ontology. [WSML keyword_2] wsml#choreography [3]

Output: Used to type a choreography and to bind it to an interface.


Input: [WSML keyword] wsml#arity [1] Used to define the arity of a WSML relation. [WSML keyword_2] wsml#orchestration [3]

Output: Used to type an orchestration and to bind it to an interface.


Input: [WSML keyword] wsml#param [1] Used to type parameters of WSML relations. [WSML keyword_2] wsml#nfp [3]

Output: Used to type non-functional properties.


Input: [WSML keyword] wsml#subRelationOf [1] Used as predicate to define sub-relations. [WSML keyword_2] wsml#importsOntology [3]

Output: Used to define the import of an external ontology.


Input: [WSML keyword] wsml#hasRelationInstance [1] Used to type a relation instance and to bind it to an ontology. [WSML keyword_2] wsml#usesMediator [3]

Output: Used to define the use of a mediator.


Input: [0] Value [2] Example [3] Scope [4] Notes [1]

Output: Description

Internationalization Tag Set (ITS) Version 2.0


Input: [0] terminology [2] The localization had â€œPen Driveâ€ when corporate terminology specified that â€œUSB Stickâ€ was to be used. The localization text inconsistently used "Start" and "Begin". A text renders the Hungarian term recsegÅ‘Ã©k as â€œbuzzer bridgeâ€ in English to translate (a literal translation), but the term used in English should be â€œwedge block,â€ as specified in a terminology list supplied to the translator. [3] S or T [4] This value MUST NOT be used 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 should be 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. [1]

Output: An incorrect term or a term from the wrong domain was used or terms are used inconsistently.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] mistranslation [2] 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...") [3] T [4] Issues related to translation of specific terms related to the domain or task-specific language should be categorized as terminology issues. [1]

Output: The content of the target mistranslates the content of the source.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] omission [2] One or more segments found in the source that should have been translated are missing in the target. [3] S or T [4] This type should not be used for missing whitespace or formatting codes, but instead should be reserved for linguistic content. [1]

Output: Necessary text has been omitted from the localization or source.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] untranslated [2] The source segment reads "The Professor said to Smith that he would hear from his lawyer" but the Hungarian localization reads "A professzor azt modta Smithnek, hogy he would hear from his lawyer." [3] T [4] 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. [1]

Output: Content that should have been translated was left untranslated.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] addition [2] The translated text contains a note from the translator to himself to look up a term; the note should have been deleted but was not. [3] T [1]

Output: The translated text contains inappropriate additions.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] duplication [2] A section of the target text was inadvertently copied twice in a copy and paste operation. [3] T [1]

Output: Content has been duplicated improperly.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] inconsistency [2] The text states that an event happened in 1912 in one location but in another states that it happened in 1812. [3] S or T [1]

Output: The text is inconsistent with itself (NB: not for use with terminology inconsistency).

Internationalization Tag Set (ITS) Version 2.0


Input: [0] grammar [2] The text reads "The guidelines says that users should use a static grounding strap." [3] S or T [1]

Output: The text contains a grammatical error (including errors of syntax and morphology).

Internationalization Tag Set (ITS) Version 2.0


Input: [0] legal [2] 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. [3] S or T [1]

Output: The text is legally problematic (e.g., it is specific to the wrong legal system).

Internationalization Tag Set (ITS) Version 2.0


Input: [0] register [2] A financia financial text in U.S. English refers to dollars as "bucks". [3] S or T [1]

Output: The text is written in the wrong linguistic register of uses slang or other language variants inappropriate to the text.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] locale-specific-content [2] A text translated for the Japanese market contains call center numbers in Texas and refers to special offers available only in the U.S. [3] S or T [4] Legally inappropriate material should be classified as legal . [1]

Output: The localization contains content that does not apply to the locale for which it was prepared.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] locale-violation [2] A text localized into German has dates in YYYY-MM-DD format instead of in 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.â€ [3] S or T [4] This category should be used for spelling errors only if they relate specifically to locale expectations (e.g., a text consitently 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 should instead be counted as spelling errors. [1]

Output: Text violates norms for the intended locale.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] style [2] Company style guidelines dictates that all individuals be referred to as Mr. or Ms. with a family name, but the text refers to â€œJack Smithâ€. [3] S or T [1]

Output: The text contains stylistic errors.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] characters [2] A text should have a 'â€¢' but instead has a 'Â¥' sign. A text translated into German omits the umlauts over 'Ã¼', 'Ã¶', and 'Ã¤'. [3] S or T [1]

Output: The text contains characters that are garbled or incorrect or that are not used in the language in which the content appears.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] misspelling [2] A German text misspells the word "Zustellung" as "ZustellÃ¼ng". [3] S or T [1]

Output: The text contains a misspelling.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] typographical [2] An English text has the following sentence: "The man whom, we saw, was in the Military and carried it's insignias". [3] S or T [1]

Output: The text has typographical errors such as omitted/incorrect punctuation, incorrect capitalization, etc.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] formatting [2] 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. [3] S or T [1]

Output: The text is formatted incorrectly.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] inconsistent-entities [2] 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". [3] S or T [1]

Output: The source and target text contain different named entities (dates, times, place names, individual names, etc.)

Internationalization Tag Set (ITS) Version 2.0


Input: [0] numbers [2] A source text states that an object is 120 cm long, but the target text says it is 129 cm. long. [3] S or T [4] Some tools may correct for differences in units of measurement to reduce false positives. [1]

Output: Numbers are inconsistent between source and target.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] markup [2] The source segment has five markup tags but the target has only two. An opening tag in the text is missing a closing tag. [3] S or T [1]

Output: There is an issue related to markup or a mismatch in markup between source and target.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] pattern-problem [2] The tool disallows the regular expression pattern ['"â€â€™][\.,] but the translated text contains "A leading â€œexpertâ€, a political hack, claimed otherwise." [3] S or T [1]

Output: The text fails to match a pattern that defines allowable content (or matches one that defines non-allowable content).

Internationalization Tag Set (ITS) Version 2.0


Input: [0] whitespace [2] 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 period should be used. [3] S or T [1]

Output: There is a mismatch in whitespace between source and target content. content or the text violates specific rules related to the use of whitespace..

Internationalization Tag Set (ITS) Version 2.0


Input: [0] internationalization [2] 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. [3] S or T [4] There are many kinds of internationalization issues. This category is therefore very heterogeneous in what it can refer to. [1]

Output: There is an issue related to the internationalization of content.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] length [2] The translation of a segment is five times as long as the source. [3] T or S [4] What constitutes a "significant" difference in length is determined by the model referred to in the locQualityIssueProfileRef . [1]

Output: There is a significant difference in source and target length.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] uncategorized [2] A new version of a tool returns information on an issue that has not been previously checked and that is not yet classified. [3] S or T [4] This category has two 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 categories, 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 categories as soon as possible since uncategorized does not foster interoperability. [1]

Output: The issue has not been categorized.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] other [3] S or T [4] This category allows for the inclusion of any issues not included in the previously listed values. This value MUST NOT be used 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" category, it MUST be mapped to this value even if the specific instance of the issue might be mapped to another category. [1]

Output: Any issue that cannot be assigned to any values listed above.

Internationalization Tag Set (ITS) Version 2.0


Input: [Range] Participant [Kind] Thing [Property]

Output: hasParticipant


Input: [Range] Input [Kind] Parameter [Property]

Output: hasInput


Input: [Range] Output [Kind] Parameter [Property]

Output: hasOutput


Input: [Range] Local [Kind] Parameter [Property]

Output: hasLocal


Input: [Range] Condition [Kind] Expression [Property]

Output: hasPrecondition


Input: [Range] Result [Kind] (see below) [Property]

Output: hasResult


Input: [Requirement] Use valid (X)HTML [Details] Using valid HTML means having an HTML code that follows one of the DTDs of the HTML specification. Your best choice is valid XHTML strict markup: XHTML means that the code will benefit from all the XML power, and strict ensures your site won't mix presentation markup with the structure. [Rationale] Valid HTML code is a first step toward more compatibility with browsers and better rendering on the latest ones. Using only strict HTML (that is, the Strict HTML DTD) makes the site easier to maintain and evolve. [Test tool]

Output: The W3C HTML Validator is one of the many options available. The LogValidator is especially helpful in maintaining a valid Web site.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use extensively valid CSS [Details] Avoid any presentational markup and keep all the layout features in well-defined CSS style sheets. [Rationale] Linked style sheets allow presentation to be decoupled completely from the page structure of your site, and lets you quickly change its layout and rendering. It also guarantees that everybody can adjust the rendering to their needs and tastes. [Test tool]

Output: The CSS Validator detects any non-compliant use of the CSS technologies.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use HTTP properly [Details] Make sure that each page of your site is accessible with a stable address (URL) and that the HTTP caching properties are set correctly. Make sure if you migrate to a new site version that the URLs are either kept as is or at least redirected to the new ones. [Rationale] HTTP is a very powerful protocol and you get most of its power with stable URLs and an efficient caching system: bookmarks and links don't break, network access is faster, users are happy! [Test tool]

Output: The W3C Link Checker can provide some help. Besides, the advices given in the Common HTTP Implementation Problems Note can help assess what needs to be respected.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use SVG and PNG for graphics [Details] Use PNG for raster images, and SVG for all others. [Rationale] PNG is a much more capable format than other binary formats for raster images because it provides better compression, more options, and it's free. The best format you should require is SVG: it's scalable, XML-based, very light, and has a lot of capabilities, for example, animation using SMIL, which is supported on cell phones, etc. [Test tool]

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use techniques to make your content accessible [Details] Details. [Rationale] Making a site accessible benefits all of your users, and broadens your current audience. This requirement may be required by law in some countries. [Test tool]

Output: See Evaluation Tools for Web Content Accessibility.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use standards scripting languages [Details] Use the DOM API combined with Ecmascript (but don't make the use of scripts mandatory to navigate in the site!). [Rationale] DOM and Ecmascript (the common standard behind Javascript and JScript) are the best way to go to get interoperable scripts to create animations in your Web site. But do not forget your users that don't have these scripting capacities enabled. [Test tool]

Buy standards compliant Web sites — W3C QA


Input: [Definition] Character data [Attribute Type]

Output: CDATA

Modularization of XHTML - XHTML Abstract Modules


Input: [Definition] A document-unique identifier [Attribute Type]

Output: ID

Modularization of XHTML - XHTML Abstract Modules


Input: [Definition] A reference to a document-unique identifier [Attribute Type]

Output: IDREF

Modularization of XHTML - XHTML Abstract Modules


Input: [Definition] A space-separated list of references to document-unique identifiers [Attribute Type]

Output: IDREFS

Modularization of XHTML - XHTML Abstract Modules


Input: [Definition] A name with the same character constraints as ID above [Attribute Type]

Output: NAME

Modularization of XHTML - XHTML Abstract Modules


Input: [Definition] A name composed of CDATA characters but no whitespace [Attribute Type]

Output: NMTOKEN

Modularization of XHTML - XHTML Abstract Modules


Input: [Definition] Multiple names composed of CDATA characters separated by whitespace [Attribute Type]

Output: NMTOKENS

Modularization of XHTML - XHTML Abstract Modules


Input: [Definition] Processed character data [Attribute Type]

Output: PCDATA

Modularization of XHTML - XHTML Abstract Modules


Input: [Keyword] hidden [State] Hidden [Data type] An arbitrary string [Control type]


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

Output: A text field


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

Output: Search field


Input: [Keyword] tel [State] Telephone [Data type] Text with no line breaks [Control type]

Output: A text field


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

Output: A text field


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

Output: A text field


Input: [Keyword] password [State] Password [Data type] Text with no line breaks (sensitive information) [Control type]

Output: A text field that obscures data entry


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

Output: A date control


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

Output: A time control


Input: [Keyword] number [State] Number [Data type] A numerical value [Control type]

Output: A text field or spinner control


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

Output: A slider control or similar


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

Output: A color well


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

Output: A checkbox


Input: [Keyword] radio [State] Radio Button [Data type] An enumerated value [Control type]

Output: A radio button


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

Output: A label and a button


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

Output: A button


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

Output: Either a clickable image, or a button


Input: [Keyword] reset [State] Reset Button [Data type] n/a [Control type]

Output: A button


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

Output: A button


Input: [Requirement] Use valid (X)HTML [Rationale] Valid HTML code is a first step toward more compatibility with browsers and better rendering on the latest ones. Using only strict HTML (that is, the Strict HTML DTD) makes the site easier to maintain and evolve. [Test tool] The W3C HTML Validator is one of the many options available. The LogValidator is especially helpful in maintaining a valid Web site. [Details]

Output: Using valid HTML means having an HTML code that follows one of the DTDs of the HTML specification. Your best choice is valid XHTML strict markup: XHTML means that the code will benefit from all the XML power, and strict ensures your site won't mix presentation markup with the structure.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use extensively valid CSS [Rationale] Linked style sheets allow presentation to be decoupled completely from the page structure of your site, and lets you quickly change its layout and rendering. It also guarantees that everybody can adjust the rendering to their needs and tastes. [Test tool] The CSS Validator detects any non-compliant use of the CSS technologies. [Details]

Output: Avoid any presentational markup and keep all the layout features in well-defined CSS style sheets.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use HTTP properly [Rationale] HTTP is a very powerful protocol and you get most of its power with stable URLs and an efficient caching system: bookmarks and links don't break, network access is faster, users are happy! [Test tool] The W3C Link Checker can provide some help. Besides, the advices given in the Common HTTP Implementation Problems Note can help assess what needs to be respected. [Details]

Output: Make sure that each page of your site is accessible with a stable address (URL) and that the HTTP caching properties are set correctly. Make sure if you migrate to a new site version that the URLs are either kept as is or at least redirected to the new ones.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use SVG and PNG for graphics [Rationale] PNG is a much more capable format than other binary formats for raster images because it provides better compression, more options, and it's free. The best format you should require is SVG: it's scalable, XML-based, very light, and has a lot of capabilities, for example, animation using SMIL, which is supported on cell phones, etc. [Test tool] N/A [Details]

Output: Use PNG for raster images, and SVG for all others.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use techniques to make your content accessible [Rationale] Making a site accessible benefits all of your users, and broadens your current audience. This requirement may be required by law in some countries. [Test tool] See Evaluation Tools for Web Content Accessibility. [Details]

Output: Details.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use standards scripting languages [Rationale] DOM and Ecmascript (the common standard behind Javascript and JScript) are the best way to go to get interoperable scripts to create animations in your Web site. But do not forget your users that don't have these scripting capacities enabled. [Test tool] N/A [Details]

Output: Use the DOM API combined with Ecmascript (but don't make the use of scripts mandatory to navigate in the site!).

Buy standards compliant Web sites — W3C QA


Input: [Attribute Type] CDATA [Definition]

Output: Character data

Building XHTML Modules - Defining Abstract Modules


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier

Building XHTML Modules - Defining Abstract Modules


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier

Building XHTML Modules - Defining Abstract Modules


Input: [Attribute Type] NAME [Definition]

Output: A name with the same character constraints as ID above

Building XHTML Modules - Defining Abstract Modules


Input: [Attribute Type] NMTOKEN [Definition]

Output: A name composed of CDATA characters but no whitespace

Building XHTML Modules - Defining Abstract Modules


Input: [Attribute Type] NMTOKENS [Definition]

Output: Multiple names composed of CDATA characters separated by whitespace

Building XHTML Modules - Defining Abstract Modules


Input: [Attribute Type] PCDATA [Definition]

Output: Processed character data

Building XHTML Modules - Defining Abstract Modules


Input: [Postal.] Name. [Category] Physical Contact Information, Demographic and SocioEconomic Data [Type] PersonName. [Short display name]

Output: Name


Input: [Postal.] Street [Category] Physical Contact Information [Type] Text [Short display name]

Output: Street Address


Input: [Postal.] City [Category] Physical Contact Information [Type] Text [Short display name]

Output: City


Input: [Postal.] StateProv [Category] Physical Contact Information [Type] Text [Short display name]

Output: State or Province


Input: [Postal.] PostalCode [Category] Demographic and SocioEconomic Data [Type] Text [Short display name]

Output: Postal Code


Input: [Postal.] CountryCode [Category] Demographic and SocioEconomic Data [Type] Country [Short display name]

Output: Country Code


Input: [Postal.] Country [Category] Demographic and SocioEconomic Data [Type] Text [Short display name]

Output: Country Name


Input: [Postal.] Formatted [Category] Demographic and SocioEconomic Data [Type] Text [Short display name]

Output: Formatted Postal Address


Input: [Name] clip-path [Value] | [ || ] | none [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] as specified [Media] visual [Animatable] as specified for [CSS-SHAPES], otherwise no [Computed value] as specified, but with values made absolute [Initial]


Input: [Name] clip-rule [Value] nonzero | evenodd [Applies to] Applies to SVG graphics elements [Inh.] yes [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: nonzero


Input: [Name] mask-image [Value] # [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified, but with URIs made absolute [Initial]


Input: [Name] mask-mode [Value] # [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: auto


Input: [Name] mask-repeat [Value] # [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] Consists of: two keywords, one per dimension [Initial]

Output: no-repeat


Input: [Name] mask-position [Value] # [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] refer to size of mask painting area minus size of mask layer image; see text background-position [CSS3BG] [Media] visual [Animatable] as repeatable list of simple list of length, percentage, or calc [Computed value] Consisting of: two keywords representing the origin and two offsets from that origin, each given as an absolute length (if given a ), otherwise as a percentage. [Initial]

Output: center


Input: [Name] mask-clip [Value] [ | no-clip ]# [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: border-box


Input: [Name] mask-origin [Value] # [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: border-box


Input: [Name] mask-size [Value] # [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] as repeatable list of simple list of length, percentage, or calc (This means keyword values are not animatable.) [Computed value] as specified, but with lengths made absolute [Initial]

Output: auto


Input: [Name] mask-composite [Value] # [Applies to] All elements. In SVG, it applies to container elements without the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: add


Input: [Name] mask [Value] # [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] see individual properties [Media] visual [Animatable] see individual properties [Computed value] see individual properties [Initial]

Output: see individual properties


Input: [Name] mask-border-source [Value] none | [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] none or the image with its URI made absolute [Initial]


Input: [Name] mask-border-mode [Value] luminance | alpha [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: alpha


Input: [Name] mask-border-slice [Value] [ | ]{1,4} fill? [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] refer to size of the mask border image [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: 0


Input: [Name] mask-border-width [Value] [ | | | auto ]{1,4} [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] relative to width/height of the mask border image area [Media] visual [Animatable] no [Computed value] all s made absolute, otherwise as specified [Initial]

Output: auto


Input: [Name] mask-border-outset [Value] [ | ]{1,4} [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] all s made absolute, otherwise as specified [Initial]

Output: 0


Input: [Name] mask-border-repeat [Value] [ stretch | repeat | round | space ]{1,2} [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: stretch


Input: [Name] mask-border [Value] <‘mask-border-source’> || <‘mask-border-slice’> [ / <‘mask-border-width’>? [ / <‘mask-border-outset’> ]? ]? || <‘mask-border-repeat’> || <‘mask-border-mode’> [Applies to] See individual properties [Inh.] no [%ages] n/a [Media] visual [Animatable] See individual properties [Computed value] See individual properties [Initial]

Output: See individual properties


Input: [Name] mask-type [Value] luminance | alpha [Applies to] mask elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: luminance


Input: [Name] clip [Value] | auto [Applies to] Absolutely positioned elements. In SVG, it applies to elements which establish a new viewport, elements and mask elements. [Inh.] no [%ages] n/a [Media] visual [Animatable] as rectangle [Computed value] as specified [Initial]

Output: auto


Input: [Definition] Character data [Attribute Type]

Output: CDATA

Building XHTML Modules - Defining Abstract Modules


Input: [Definition] A document-unique identifier [Attribute Type]

Output: ID

Building XHTML Modules - Defining Abstract Modules


Input: [Definition] A reference to a document-unique identifier [Attribute Type]

Output: IDREF

Building XHTML Modules - Defining Abstract Modules


Input: [Definition] A name with the same character constraints as ID above [Attribute Type]

Output: NAME

Building XHTML Modules - Defining Abstract Modules


Input: [Definition] A name composed of CDATA characters but no whitespace [Attribute Type]

Output: NMTOKEN

Building XHTML Modules - Defining Abstract Modules


Input: [Definition] Multiple names composed of CDATA characters separated by whitespace [Attribute Type]

Output: NMTOKENS

Building XHTML Modules - Defining Abstract Modules


Input: [Definition] Processed character data [Attribute Type]

Output: PCDATA

Building XHTML Modules - Defining Abstract Modules


Input: [Property] hasParticipant [Kind] Thing [Range]

Output: Participant


Input: [Property] hasInput [Kind] Parameter [Range]

Output: Input


Input: [Property] hasOutput [Kind] Parameter [Range]

Output: Output


Input: [Property] hasLocal [Kind] Parameter [Range]

Output: Local


Input: [Property] hasPrecondition [Kind] Expression [Range]

Output: Condition


Input: [Property] hasResult [Kind] (see below) [Range]

Output: Result


Input: [Definition] Character data [Attribute Type]

Output: CDATA

XHTML™ Modularization 1.1 - Second Edition


Input: [Definition] A document-unique identifier [Attribute Type]

Output: ID

XHTML™ Modularization 1.1 - Second Edition


Input: [Definition] A reference to a document-unique identifier [Attribute Type]

Output: IDREF

XHTML™ Modularization 1.1 - Second Edition


Input: [Definition] A space-separated list of references to document-unique identifiers [Attribute Type]

Output: IDREFS

XHTML™ Modularization 1.1 - Second Edition


Input: [Definition] A name with the same character constraints as ID above [Attribute Type]

Output: NAME

XHTML™ Modularization 1.1 - Second Edition


Input: [Definition] A name composed of only name tokens as defined in XML 1.0 [XML] [Attribute Type]

Output: NMTOKEN

XHTML™ Modularization 1.1 - Second Edition


Input: [Definition] One or more white space separated NMTOKEN values [Attribute Type]

Output: NMTOKENS

XHTML™ Modularization 1.1 - Second Edition


Input: [Model Aspect] End-point basics [Linked Data Platform (LDP)]

Output: A LDP server exposes at least one URI to a container-type resource. A client can learn about the container and its contents (members), by simply fetching the container. If only the non-member information is needed, a client can request only that. If a client needs to know if it can create things in this container, then usual HTTP methods can be used such as HEAD or OPTIONS to learn about which verbs are permitted on the request URI. Need: It might be useful to define a common property for external vocabularies to use to indicate the end-point, take for example: Alternative: LDP provides no new facilities for web clients to acquire URLs to Containers. Web clients might use out of band knowledge, home resources, POWDER, emailing a friend a link, or any other mechanism deemed appropriate by the application's needs. It is possible for a server to expose a single Container as a home resource, which web clients GET and examine to locate other resources (including other Containers). It is also possible for that same home resource to be serialized and provided to a client as a document. LDP assumes that each client is able to obtain whatever URLs it needs through non-LDP means, and restricts itself to an interaction model for Containers and their members.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Container basics [Linked Data Platform (LDP)]

Output: A container has a URI where you can start interacting with the container, at the most basic level you can GET a list of members, and for containers with many members it is likely the response is broken into pages. Through HTTP HEAD/OPTIONS introspection, a client can learn which HTTP verbs are permitted on this. Since LDP containers are described using RDF constructs, a LDP server may allow clients to POST the representation of the container to create it. Need: How are the acceptable content-types communicated via HTTP headers? Alternative: Before asking 'how' acceptable content-types are communicated, we need to agree that doing so is required (should it be in-scope for LDP - part of ISSUE-21 perhaps). In the simplest case, once the client "knows" it is dealing with a conformant LDP Container it does know (at least) that Turtle is supported. If communicating supported content-types is in-scope, then a syntax needs to be defined (either new, or re-used). Potential re-use choices might include (and these are not necessarily mutually exclusive, although to keep clients simple it would help to have at least one required method if it is in-scope): atom:accept predicate(s) on a container Link: <>; rel="self"; type="one acceptable media type value" Linking itself to a POWDER document - I don't see any POWDER syntax covering media types, but it might be possible to re-use atom:accept in this context. Aside: If we do place it in-scope, we have the same question about members, so it might be that we talk about this introspection at the LDPR level and let LDPCs "inherit" it from LDPRs. LDPRs might leave everything optional, and LDPC requires one particular method while allowing others, for example.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Creating container members (resources) [Linked Data Platform (LDP)]

Output: Any kind of resource can be listed in a container, and everything that is in a container is represented by a member. Members follow the standardized metadata model defined by RDF. If a client has POSTed a "media resource" (pretty much anything other than RDF) to a container URI, which has one of the media types that the container accepts, the server accepts this media resource and creates the resource, which will then represent this media resource when you list the container contents. The interesting aspect of this setup is that you POST one thing, its representation gets converted by the server to some appropriate storage and its membership added to the container. email: there is only one container, and what you POST determines whether it's self-contained or not. if the POSTed resource contains all data (... in XML), it's what we now call "composition". if the POSTed resource contains a link to "external content" ( in XML), it's what we now call "aggregation". Servers might try to be smart about populating additional data fields for the resource, for example creation date and who created it. They also might consider come properties to be "server managed", i.e. read-only from any client's point of view. ISSUE-11 questions how much the LDP spec constrains them.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Member (resource) identity [Linked Data Platform (LDP)]

Output: A container is a set of members and (perhaps) non-member properties, and thus contains a list of members (entries) representing each individual member. The model uses a URI to represent the identity of each member resource, which will be used for identification globally. The identification of the member as an entry, will be represented as using a simple RDF statement: rdfs:member . Note: some proposals on the mailing list for ISSUE-34 include the use of different membership predicates like ldp:owns or ldp:contains in place of rdfs:member. If accepted, those predicates might cover some of the ground for ISSUE-21 (affordances).

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Interacting with container members [Linked Data Platform (LDP)]

Output: Members are listed when GETting a container, and their data is exposed through regular RDF mechanisms. If members are editable, a client can introspect via HEAD/OPTIONs to see if PUT, PATCH or DELETE verbs are permitted. A server may provide some member data or just a reference to it in the response of a request for container information.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Interacting with containers (composition) [Linked Data Platform (LDP)]

Output: Bringing into existence: typically containers just exist, though some servers may allow creation of containers by POSTing a representation of a container to an already-existing container. Removing from existence (DELETEing): containers are like any other HTTP web resource, they have a URI which a server may accept a DELETE request on. The question becomes, what happens to the members when a container is DELETEd? Based on resolution for ISSUE-25, in order for the container to be deleted all its members must also be deleted. There have been proposals for another model of containers, which may or may not have this rule, see ISSUE-34. Removing a member from a container: simply update the container's membership by PATCHing it with a statement to remove the membership triple. The resource still exists, its ownership is unknown (or perhaps a concept of a "default" container?). Adding an existing member to a container: potentially not allowed (ISSUE-25 resolution) Moving a member from one container to another: potentially not allowed (ISSUE-25 resolution) Alternative: PATCH to remove a member is not allowed; the client must DELETE the member to remove it from the container.

Difference between revisions of "ISSUE-37" - Linked Data Platform