See also: IRC log
JK: discusses issue 001 - incomplete response
should be noted, when connection failed no response note can be taken,
... item was discussed in last conference
... talks about an incomplete HTTP-response
SAZ: possible scenario: client sends request,
which is incomplete. Then a client might also recieve an incomplete
response
... How does EARL handle incomplete responses (eg because of a server
timeout)?
JK: Issue 003 was closed as NO during last conference.
<drooks> i think last week we said that issue 001 could be represented in HTTP RDF through the absence of an expected response class
JK: It is out of scope of the vocabulary
SAZ: Thinks it is META-Information on requests
and responses
... would recommend it at least as optional information
JK: If we would take up response times - which element to take (eg from DC)
SAZ: There could be use cases where recording of timestamps might be useful in HTTP in RDF
<scribe> ACTION: SAZ: get feedback from working group on timestamp issues [recorded in http://www.w3.org/2007/05/23-er-minutes.html#action01]
SAZ: takes up Issue-017
JK: if default character encoding cannot be
used, we wanted to use DATA URI
... inclusion of DTD can be solved through combination of seperate
properties, which are combined
SAZ: We need a different concept for the
body
... Maybe different classes according to different content types
<scribe> ACTION: JK: draft a concept for the solution of problem with body property (Issue 14,15 & 17) [recorded in http://www.w3.org/2007/05/23-er-minutes.html#action02]
SAZ: we should try to get message headers as literal values
JK: we record the response code, but some persons might want to know the actual meaning
SAZ: Literal vs. predifined value consideration
is also an performace issue
... keep on discussing the advantages/disadvantages of literal values and
predifined values on the mailing list
<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2007May/0015.html
JK: Thinks this approach is valuable, maybe also for other properties
RESOLUTION: tentativly accepted solution provided by SAZ