JT
JR
MMP
WL
MK
GR
CMN
HS
ACTION ITEMS:
MK: New 3.2 "at minimum" text.
CMN: New 3.2 "advanced" text.
CMN: New subtext to 3.3.
MINUTES
Face2Face Planning:
Phone participants: WL, PJ (may join in either afternoon for Lotus evaluation), HS (will join for certain subjects)
AGENDA
Monday, 18 June 2001
9:00 - 10:30 ATAG "wombat" (minimum requirements, overall structure)
10:45 - 12:30 ATAG "wombat" (continued)
1:30 - 3:00 Techniques
3:30 - 5:00 Techniques / Evaluation techniques
Tuesday, 19 June 2001
9:00 - 10:30 ATAG and EARL
10:45 - 12:30 Evaluation techniques
1:30 - 3:00 Existing tool evaluations
3:30 - 5:00 Working Group planning and next steps.
JT: Any other suggestions?
JR: Would like to specifically discuss 4.1, 4.2.
JT: If anyhting else comes up, send them to CMN to put on the agenda.
Discussion of JR's new techniques
CMN, JR, MK: Big discussion of whether we need an explanatory "requires" statement.
JT: Is everyone happy with a point by point discussion of whether each subtext should have a "requires" sentence (at face to face).
All: Yes.
3.2 Separate structure from presentation
MK: Could we list relevant tags (make two categories)
JR: Should they be in the techniques?
CMN: Would like to see how this would work for Domino or Maya.
GR: It'sjust the way the tool acts, not what the user sees.
JT: what might an Advanced Implementation do?
MK: Might have a tidying conversion process that adds strucutre.
GR: What about Javascript? Could it be considered presentation?
MK: what about languages that require presentation markup to be used.
CMN: it is important to have good presentration but it is important to have good strucutes underlying.
CMN: proposes that an advanced implementation will look at the document strucutre and provide information tailored to the document.
CMN: Will take action item to propose "3.2 advanced implementation"
MK: will send proposed "3.2 at minimum" text.
3.3
CMN: Wants to remove first sentence.from the subtext.
JR: We should keep the example from the first sentence.
GR: Wants to add "automatically inserted place holder text" to the subtext.
CMN: Action item to propose new subtext to 3.3.
3.4
MK: Does the Homesite sytem for storing bits of code meet 3.4?
CMN: Yes.
JR: No.