W3C home > Mailing lists > Public > public-webarch-comments@w3.org > February 2004

Fwd: Auto: public-webarch-comments@w3.org autoreply

From: Martin Duerst <duerst@w3.org>
Date: Fri, 27 Feb 2004 18:22:23 -0500
Message-Id: <4.2.0.58.J.20040227182126.05550460@localhost>
To: sysreq@w3.org
Cc: public-webarch-comments@w3.org

Dear system team,

Would it be possible to set this mailing list so that it only
returns this message every so often (every week or month)?
With many comments, it gets annoying.

Regards,  Martin.

>X-Original-To: duerst@homer.w3.org
>Delivered-To: duerst@homer.w3.org
>Delivered-To: duerst@w3.org
>To: duerst@w3.org
>X-Loop: postmaster@w3.org
>From: W3C Postmaster <postmaster@w3.org>
>Auto-Submitted: auto-replied
>Subject: Auto: public-webarch-comments@w3.org autoreply
>Date: Fri, 27 Feb 2004 16:58:49 -0500 (EST)
>X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on homer.w3.org
>X-Spam-Level:
>X-Spam-Status: No, hits=-4.6 required=3.6 tests=AWL,BAYES_00 autolearn=ham
>         version=2.63
>
>Thank you for your comments about Architecture of the World Web
>Web[1]. The TAG will do its best to address your comments in a timely
>fashion and respond to substantive issues that you raise. For more
>information, consult the TAG home page[2].
>
>[1] http://www.w3.org/TR/webarch/
>[2] http://www.w3.org/2001/tag/
>
>----------------------------------------------------------------------
> >From owner-public-webarch-comments@dr-nick.w3.org  Fri Feb 27 16:58:49 2004
>Return-Path: <owner-public-webarch-comments@dr-nick.w3.org>
>X-Original-To: public-webarch-comments@w3.org
>Delivered-To: public-webarch-comments@w3.org
>Received: from enoshima (homer.w3.org [18.29.0.30])
>         by dr-nick.w3.org (Postfix) with ESMTP
>         id 1D0643F474D; Fri, 27 Feb 2004 16:58:48 -0500 (EST)
>Message-Id: <4.2.0.58.J.20040227165437.054608e0@localhost>
>X-Sender: duerst@localhost
>X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J
>Date: Fri, 27 Feb 2004 16:58:39 -0500
>To: "Ian B. Jacobs" <ij@w3.org>
>From: Martin Duerst <duerst@w3.org>
>Subject: Re: Please don't point to as yet empty Issues
>Cc: public-webarch-comments@w3.org
>In-Reply-To: <1077911446.1075.1079.camel@seabright>
>References: <4.2.0.58.J.20040227130201.080bef10@localhost>
>  <4.2.0.58.J.20040227130201.080bef10@localhost>
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"; format=flowed
>
>Hello Ian,
>
>I can accept the TAG's decision to refer to issues rather than
>findings if the findings are still in draft stage. But that
>addresses only a detail of my comment.
>
>To be even more general than in my original comment, the way
>issues (and also findings) are cited is frustrating, because
>it might be very important, it might be very interesting,
>or there might be very little, or not terribly interesting
>or related to the topic. About the only text used is
>things like "see also ...". There needs to be more help
>for the reader to decide whether she wants to follow the
>link (and more help for somebody who has the spec printed out).
>
>Regards,  Martin.
>
>
>At 14:50 04/02/27 -0500, Ian B. Jacobs wrote:
> >On Fri, 2004-02-27 at 13:08, Martin Duerst wrote:
> > > This is a specific example of a somewhat more general problem,
> > > namely the way Issues (and Findings) are referenced in WebArch,
> > > giving virtually no information about how these relate to the
> > > text.
> > >
> > > Section 2.6 points to issue DerivedResources-43. When I'm finally
> > > there (not easy because I'm starting from a print copy,
> > > http://www.w3.org/2001/tag/issues.html?type=1#DerivedResources-43),
> > > the only thing I see is 'raised' and 'accepted'. So why should I
> > > go there in the first place? And how can the authors guarantee
> > > that this issue will indeed be relevant?
> > >
> > > I propose to not point to issues that don't have reached a
> > > certain maturity (in which case pointing to the finding is
> > > probably better).
> >
> >Hi Martin,
> >
> >Section 1.1.2 states:
> >
> >   "Since the findings evolve independently, this document also includes
> >references to approved TAG findings. For other TAG issues covered by
> >this document but without an approved finding, references are to entries
> >in the TAG issues list."
> >
> >The TAG explicitly resolved to not refer to draft findings.
> >
> >  _ Ian
> >--
> >Ian Jacobs (ij@w3.org)   http://www.w3.org/People/Jacobs
> >Tel:                     +1 718 260-9447
Received on Saturday, 28 February 2004 06:07:16 EST

This archive was generated by hypermail pre-2.1.9 : Saturday, 28 February 2004 06:07:22 EST