W3C

ERT WG

1 Feb 2006

See also: IRC log

Attendees

Present
Jim, Shadi, Nick, David, Chris, CarlosI
Regrets
Johannes, CarlosV
Chair
Shadi
Scribe
Nick

Contents


EARL 1.0 Schema - open issues

saz: testCase and testRequirement

carlosi: requirement != test

saz/carlosi: should we allow multiple requirements in one assertion?

<JibberJim> I think test case and requirement is a good thing, I agree with carlos's emails.

<drooks> it may take several test cases to prove a requirement... hence an assertion should be allowed to have multiple test cases

<JibberJim> Yes shadi, that's what I meant, and we allow both

Carlos, jim: requirement <--> testcase is a many-to-many thing

RESOLUTION: testCase and testRequirement are distinct and should be both included

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2006Jan/0048

saz: earl for streaming contents?

jim: EARL doesn't need to do anything. We already allow people to define their own pointers into contents

<JibberJim> Yes

saz: nice to speel that out + example for earl guide
... no meet next week; use mailinglist

<shadi> ci: about to propose additions to the schema

HTTP in RDF namespaces

saz: one namespace for http?

jim: yes

CarlosI: possible ambiguity re: extension headers

nrk: http:request-this, http:response-that
... two-level namespace

saz: that looks like what johannes suggests

provisional resolution as above, but wait for johannes before firming it up?

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.127 (CVS log)
$Date: 2006/02/01 16:30:17 $