W3C home > Mailing lists > Public > www-webont-wg@w3.org > July 2003

Re: Agenda and Logistics July 24 telecon -- CR vote expected

From: Jeremy Carroll <jjc@hplb.hpl.hp.com>
Date: Wed, 23 Jul 2003 08:39:57 +0100
Message-ID: <3F1E3BCD.4010601@hplb.hpl.hp.com>
To: Jim Hendler <hendler@cs.umd.edu>
CC: webont <www-webont-wg@w3.org>

Jim Hendler wrote:

> 3.0 Proposal to Request Candidate Recommendation Status
> Proposal and rationale:
> http://lists.w3.org/Archives/Public/www-webont-wg/2003Jul/0210.html
> Draft CE Director's request:
> http://www.w3.org/2001/sw/WebOnt/rqim.html

Two points, intended as suggestions for discussion under this agendum.


Is this also a resolution to publish CR documents - or do we have another 
round in which the editors prepare CR drafts and the WG has a chance to 
review them before a publish vote?
In any case we probably could do with a round the table summary from the 
editors as to the current status of the documents.

Offlist Jim quoted the following:
In the Call for Implementations, the Working Group MAY identify specific 
features of the technical report as being "features at risk." General 
statements such as "We plan to remove any unimplemented feature" are not 
acceptable; the Working Group MUST precisely identify any features at risk. 
Thus, in response to a Call for Implementations, reviewers can indicate 
whether they would formally object to the removal of the identified 
features. After gathering implementation experience, the Working Group MAY 
remove features from the technical report that were identified as being "at 
risk" and request that the Director Call for Review of a Proposed 
Recommendation. If the Working Group makes other substantive changes to the 
technical report, the Director MUST return it to the Working Group for 
further work.

Given Charles' reservations about passing all the tests we should determine 
   and document which features are at risk.
For this task, it would be useful to know which tests have noone claiming 
victory at the moment.
We should clarify in our call for implementations that there may be 
substantive changes in individual tests when implementors indicate that the 
tests do not conform to S&AS.

Received on Wednesday, 23 July 2003 03:41:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:04:47 UTC