W3C home > Mailing lists > Public > www-xkms@w3.org > August 2003

Ian Jacobs' IRC notes on the 13/Aug Teleconf

From: Jose Kahan <jose.kahan@w3.org>
Date: Wed, 13 Aug 2003 18:47:03 +0200
To: www-xkms@w3.org
Cc: ij@w3.org
Message-ID: <20030813164703.GA10318@inrialpes.fr>


You'll find here belowe Ian's IRC notes. The links he quoted
are in them, cited in context.

Ian, Thanks for your help!


<Ian> IJ jots down some topics:
<Ian>  - Test suite expectations
<Ian>  - Evaluation tools?
<Ian>  - Existing implementation reports
<Ian>  - Transitions doc
<Ian>  - Other exit criteria

<Ian> Issues responded to, all closed.

<Ian> 1) Document expectations about new or evolving implementations.
<Ian> (as well as current)
<Ian> 2) Level of detail of these evaluations.

<Ian> SOAP
<Ian> The SOAP folks did a per-feature evaluation

<Ian> Summarizing:
<Ian> 1) Identify features
<Ian> 2) Identify which ones implemented
<Ian> 3) Identify at-risk features
<Ian> 4) Revise table to show all have been implemented twice.

<Ian> (matrix)
<Ian> http://www.w3.org/2001/sw/WebOnt/rqim.html

<Ian> Test suites?
<Ian> Link between tests and documentation of which features have been implemented.
<Ian> [Talk to QA folks]
<Ian> In any case, discuss how testing handled.
<Ian> interop events?
<Ian> Other things to boost interop case?
<Ian> http://www.w3.org/2003/05/Transitions
<jose> a document mapping the requirement documents and the actual changes to those requirements if they happened
<Ian> http://www.w3.org/2003/06/09-dom-core-issues/issues.html

<Ian> Summarizing:
<Ian> 1) IDentify features
<Ian> 2) Identify features at risk
<Ian> 3) Two complete implementations or two implementations of each feature?
<Ian> (or identify "core" features that every implementation must do)
<Ian> 4) Follow the transitions doc
Received on Wednesday, 13 August 2003 12:47:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:41 UTC