W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > October 2001

Re: 2001-09-28#9 - proposal for obsoleting test cases

From: Jeremy Carroll <jjc@hplb.hpl.hp.com>
Date: Fri, 12 Oct 2001 10:02:32 +0100
Message-ID: <3BC6B1A8.16375F6C@hplb.hpl.hp.com>
To: Art Barstow <barstow@w3.org>
CC: jan.grant@bris.ac.uk, brian_mcbride@hp.com, w3c-rdfcore-wg@w3.org

> However, it's not on the agenda for the Oct 12 meeting:
>  http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2001Oct/0173.html
> Jan, Brian - what's up?
Jan gave regrets for this week too.

> > Personally I would find latest.zip more useful if it did not include
> > unapproved TCs.
> I think it would be fine to have two zip's: latest_All.zip (everthing
> including those TCs not approved] and latest_Approved.zip (only
> Approved TCs).


> > There is a maintenance issue here - is it realistic to update latest.zip on
> > every change.
> I don't think it's necessary to update the zip upon *every* change
> especially given the current rate of new test cases or the rate of
> approval.  A couple of times/week should be fine (perhaps automated
> if I can determine how to run cron over AFS).

> > As a test case user I would like to have a single URL that I go to to check
> > conformance with the latest WG decisions. Obviously that can link to other
> > URLs. Also a time lag is acceptable.
> I'm not following you here ...

Ideally in my ARP test package I would have a single well-known URL
(e.g. the manifest file) that I go to. If everything works from there
with no other hard coded w3c URLs then that's real cool.
From a time point of view, publications delays are inevitable, and a
couple of weeks is really no worse than a couple of hours.

Received on Friday, 12 October 2001 04:57:50 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:52 UTC