Testing IRIs

[ overview | existing tests | axes | mailing list ]

Nearby: editing page

Overview

Status: The IRI specification is now an IETF Proposed Standard and is published as RFC 3987. We are now working on testing.

Existing Tests and Materials

• Early IRI test (HTML <img src="...">; display of IRIs; very long IDNs)
• Resource identifier tests at /International/test
• Bidi examples page; script to generate these examples (these examples were not designed as tests, but can be used as tests)
• mod_fileiri tests and useful words in various scripts/encodings
• URI testing (relative->absolute, reg-names with percent-encoding), can be used as the base for similar IRI test
• Jeremy's proposals for basic test

Axes

(from Character Model for the World Wide Web 1.0: Resource Identifiers Candidate Recommendation Exit Criteria)

For each of these axes, there should be at least two implementations passing the applicable tests.

1. use of IRIs in several document formats;
2. use of IRIs in several locations in the same document format;
   • HTML:
     • plain links: <a href='IRI' />
     • header links: <link href='IRI'/> (stylesheet, what else?)
     • Form/query-part (also dependent on accept-charset):
       1. action attribute in <form>, in particular query part (question: what happens with the query part there in the first place?)
       2. value attribute in a form field (e.g. hidden fields)
       3. form field input by the user into fields (use e.g. copy-paste)
       4. input in address/location bar
       5. query part in e.g. an href attribute
   • SVG
3. use of non-ASCII characters in different parts of an IRI (e.g. domain name part, path part);
4. use of IRIs in documents with various widely used character encodings and with characters from various scripts;
5. use of document-specific escapes in IRIs;
6. use of IRIs with various URI schemes;
7. setup of various servers for IRIs;
8. the translation of IRIs into URIs.

Mailing List

The mailing list for public discussion of IRIs, including testing, is [email protected], with a public archive. To subscribe, send mail to [email protected] with subscribe as the subject.