action-374 test cases distribution

Hi all,

I went through the rfc 2119 list, and below are some items that need at 
least a clarification or a test case.

I put names people in the list below. If you don't want you name here or 
have questions please let me know. I will keep the action item open and 
come back to it on the 7 January call. That is, please be prepared to 
give an update on "your" test cases during that call. If that's too 
early for you please let me know.

For some of the below MUST / MUST NOT statements the actual test suite 
might do. For others you may want to create negative or positive tests, 
e.g. no. 29 / 35 / 41.

- I clarified no. 16 "mutal exclusive attributes", now coveredy by the 
schema after closing issue-59.

- No. 26 "Values of attributes which corresponds to data categories with 
a predefined set of values MUST be matched case-insensitively." We had 
discussed this before, see this thread
I think we would need a test case for this or several ones, e.g. ITS 2.0 
implementations should process HTML, e.g. "span" like
<span ... its-loc-note-type="aLerT">...
identical to
<span ... its-loc-note-type="alert">
Thoughts and volunteers?

- No. 28 " Inline global rules MUST be specified inside script which has 
type attribute with the value application/its+xml. The script element 
itself SHOULD be child of head element. Comments MUST NOT be used inside 
global rules. Each script element MUST NOT contain more than one rules 
element.": covered by 
, I think

- No. 29 " Any node selected by the terminology data category with the 
termConfidence attribute specified MUST be contained in an element with 
the annotatorsRef (or in HTML its-annotators-ref) attribute specified 
for the Terminology data category. See for more information.": Philip

- No. 31 " An optional domainMapping attribute that contains a comma 
separated list of mappings between values in the content and consumer 
tool specific values. The left part of the pair corresponds to the 
source content and is unique within the mapping and case-insensitive. 
The right part of the mapping belongs to the consumer tool. Several left 
parts can map to a single right part. The values in the left or the 
right part of the mapping may contain spaces; in that case they MUST be 
delimited by quotation marks, that is pairs of APOSTROPHE (U+0027) or 
QUOTATION MARK (U+0022).": Ankit

- No. 35 " Any node selected by the disambiguation data category with 
the disambigConfidence attribute specified MUST be contained in an 
element with the annotatorsRef (or in HTML its-annotators-ref) attribute 
specified for the disambiguation data category. ": Tadej

- No. 36 "Implementations MUST NOT combine lists of language ranges from 
multiple rules or local attributes.": Not needed IMO

- No. 38 " A required idValue attribute. It contains an XPath expression 
which constructs a string corresponding to the identifier of the node to 
which this rule applies. The identifier MUST be unique at least within 
the document. If the attribute xml:id is present or id in HTML for the 
selected node, the value of the xml:id attribute or id in HTML MUST take 
precedence over the idValue value.": Yves

- No. 41 " Any node selected by the MT Confidence data category MUST be 
contained in an element with the annotatorsRef (or in HTML, 
its-annotators-ref) attribute specified for the MT Confidence data 
category. For more information, see. ": Ankit

- No 43 + 44 " A storageEncoding attribute. It contains the name of the 
character set encoding used to calculate the number of bytes of the 
selected text. The name MUST be one of the names or aliases listed in 
the IANA Character Sets registry . The default value is UTF-8.": Karl

- We have various tests related to quality: 45, 46, 47, 48. I put Arle 
and Phil here. Phil had a question about these during the Monday call. 
Here is proposal how one might test these statements.

No. 45 "T he values listed in the following table are allowed for 
locQualityIssueType. The values a tool implementing the data category 
produces for the attribute MUST match one of the values provided in this 
table and MUST be semantically accurate. If a tool can map its internal 
values to these types it MUST do so and MUST NOT use the value other, 
which is reserved strictly for values that cannot be mapped to these 
values.": a test might be negative, e.g.:
- 1) have a manual annotated ITS 2.0 file with the correct error type 
like "terminology"
- 2) have a "fake" output of a tool with the wrong error type
- say in the test description that a tool should consume 1), but raise 
an error about the mismatch between 1) and 2)

No. 46 " 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.": again a negative test: 
having mistyping in an input file, then 1) a correct annotion 2) an 
incorrect annotation as "type", and say that 2) should not be processed 
by the tool.

- No. 47, 48: negative tests like 45 / 46.



Received on Tuesday, 18 December 2012 14:32:29 UTC