ISSUE-137: Feedback on mobileOK test pseudo-code format?

Feedback on mobileOK test pseudo-code format?

State:

CLOSED

Product:

mobileOK Basic tests

Raised by:

Sean Owen

Opened on:

2006-09-06

Description:

Another issue worth discussion is the pseudocode presented in the mobileOK test
document.

We want to describe each test clear and unambiguously. Pseudocode seems
appropriate for that reason, especially for tests that are meant to be
translated into machine-executable tests. Yet, some of the pseudocode is more
high-level than in other places, and it\'s not entirely clear that the form is
effective.

1. Would a simple paragraph of English prose be better?
2. Would a flowchart be easier to read?
3. Or if pseudocode is the best format, what, if any, changes should be made to
the style, format and level of specificity?

Related Actions Items:

No related actions

Related emails:

1. [minutes] Summary of our Gijon F2F (from dom@w3.org on 2006-10-04)
2. ISSUE-137: Feedback on mobileOK test pseudo-code format? (from dean+cgi@w3.org on 2006-09-06)

Related notes:

Display change log