See also: IRC log
saz: background info on HTTP request/response
... recalls that these were to be published as working notes
... anything missing?
JK: cookies issue
... seems to be no other issues - send spec to list
... will be able to edit as working group note. Carlos will help.
SAZ: any objections as publish as note?
resolution: HTTP request/response spec to be published as working group note.
resoultion: JK will edit
saz: cookies - publish as note in spec. Will discuss later. JK will send message to list to discuss.
JK: namespace issue still unresolved?
saz: do we want a temp namespace? (for now then switch to formal)
discussion of namespace, temp namespace was helpful in short term
JK: used several namespaces in spec
saz: will look what other groups are using but would like to use temp for now
<chaals> [I think it is a *terrible* idea to change namespaces. It is just an opaque string, and changing it just requires everyone to handle a bunch of extra stuff for no identifiable purpose]
<scribe> ACTION: saz will look into namespace for HTTP request/response stuff and talk to JK [recorded in http://www.w3.org/2006/01/18-er-minutes.html#action01]
saz: dc:location topic from CI - remove location (since using request/response)?
discussion of dc:location
<chaals> [Location in the current spec isn't used in the same way as request/response, but I don't thik it is remotely necessary as currently used anyway so support removing it]
saz: define our own earl:location?
discussion of perhaps using something like earl:uri
resolution: use earl:uri instead of dc:location
ci: concerns over testcase element in earl
draft (message sent to list)
... testrequirement element is OK but is more like testcase then testrequirement
saz: seems more like an editorial problem
ci: important that we have common view of what
... does group agree with suggestions from message posted to list?
jj: agrees with ci's post to list, wording is clearer
<CarlosI> IMO a requirement is a documented need of what a particular product should be or do (what you expect from the product) and test are process used to ensure products are designed and produced to meet those requirements (the way you test whether you have what you expected or not).
discussion of ci's proposal
<chaals> [I think the words are much more flexible and harder to pin down in english usage than Carlos' idea of them, but I like the wording proposals anyway...)
<JohannesK> 1. test (actual test that is performed)
discussion of what the actual tests are - something specific like HTML test suite or something more general like a WCAG guideline SC
saz: review of evidence class
... good discussion and we should take to list more more consideration
... is this a showstopper (hold off publication of EARL spec)?
ci: draft is still OK but needs to be resolved before final status
saz: after discussion on list we will bring up on next weeks call
<scribe> ACTION: saz will send to mailing list [recorded in http://www.w3.org/2006/01/18-er-minutes.html#action02]
<shadi> * Chaals make proposal for schema to describe how to add a Collection as evidence
<shadi> * jim write up proposal for "earl:snippet" locator type
<shadi> saz: sign up and book hotels soon!