See also: IRC log
uri: uri property confirmed
JK: bodyContentBase64 or bodyBase64 or bodyContent with definition: always base64
SAZ: bodyContent
CV: +1
JK: +1
resolution: bodyContent in 2.4
SAZ: more detailed description of bodyContent in 2.4
JK: bodyContent replaces body property
SAZ: add pointer to RFC2616 in 2.2
SAZ. be more consistent in pointing to relevant RFCs
JK: change bodyContent to body (Literal)
... add body to lists in 2.1.1 and 2.2.1
CV: add section about uses of namespaces
SAZ: put it as subsection into introduction
... unprefixed means HTTP namespace, otherwise use prefix
JK: add prefix for 3.1
... add RFC 2068 to references section
SAZ: update example
CV: add small examples for each class to relevant section
JK: one for Request, one for Response, one for Field
CV: and one for extension
JK: additionalHeader example will use Field
class, so put both into one example
... change section numbers (5.1 -> 6.1 etc.)
SAZ: CV to have an eye on editing
CV: could it become a WD?
SAZ: let the group decide; perhaps we should make it WD and then publish it
JK: find proper namespace URIs for the three used namespaces
SAZ: I'll do that
JK: I like it
... the proposal models what we talked about at the F2F
SAZ: use owl:oneOf so that Testable is either TestRequirement or TestCase
SAZ: pointers are ways to point to locations
<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2006Jul/0045
shane: is there documentation on that?
SAZ: we have to discuss the pointers next week to add it to schema