See also: IRC log
everyone to complete action items from FTF
we should be working on schema and update soon
Shadi will update soon with resolutions from FTF
ET TF has started!
all tool info will be entered in structured form in database
SAZ: what to do about some tools that could be
deleted? We'll bring up at tomorrow's ETTF meeting.
... will contact Jim re his ER tools.
SAZ: Eric P suggested we extend schema to describe delivery unit. JK has drafted something...
JK: Has reviewed HTTP protocol. Created classes
for each method.
... Content type and length property names are upper case, would like lower
case.
SAZ: How classes and properties chosen?
JK: description of logic - seemed straightforward.
(discussion of delivery unit)
(should we call it delivery unit or web resource?)
JL: we should make properties lower case
SAZ: From FTF we decided that EARL can have multiple HTTP requests/respones that define what we're testing. Should not be a single resource.
JK: Glossary seems to be out of date with real usage.
SZ: A delivery unit is a series of requests/responses. This seems to be different from glossary.
<JohannesK> thread on www-di about DUs starting with <http://lists.w3.org/Archives/Public/www-di/2005Aug/0001.html>
SAZ: We should not confine our definition of
delivery unit to single HTTP request.
... Can use Dublin Core "has part".
... question - use namespaces to differentiate?
JL: We need a way to capture headers.
SAZ: We should remove the EARL HTTP request/response because just wrappers.
<scribe> ACTION: JK will research issue of request/response and delivery unit and send to list. [recorded in http://www.w3.org/2005/11/23-er-minutes.html#action01]
JK: description of namespace difficulties
SAZ: we need more discussion - bring up on next call