W3C home > Mailing lists > Public > public-w3process@w3.org > December 2013

Re: w3process-ISSUE-74 (NeXtSteps?): Must specs describe next steps? [Document life cycle (ch 7)]

From: Charles McCathie Nevile <chaals@yandex-team.ru>
Date: Thu, 12 Dec 2013 15:33:11 +0400
To: public-w3process@w3.org, "Revising W3C Process Community Group Issue Tracker" <sysbot+tracker@w3.org>
Message-ID: <op.w7y81ld0y3oazb@dhcp-219-197-wifi.yandex.net>
On Thu, 12 Dec 2013 14:21:49 +0400, Revising W3C Process Community Group  
Issue Tracker <sysbot+tracker@w3.org> wrote:

> w3process-ISSUE-74 (NeXtSteps?): Must specs describe next steps?  
> [Document life cycle (ch 7)]
>
> http://www.w3.org/community/w3process/track/issues/74
>
> Raised by: Ian Jacobs
> On product: Document life cycle (ch 7)
>
> In http://www.w3.org/mid/CFE36B99-1937-41DD-999B-7F9A6B4C22ED@w3.org Ian  
> explains:
>
>   Because of the patent policy, it is important that readers know
>   whether a group expects a document to become a Recommendation or not.
>   Also, when a group has been chartered to produce a Recommendation
>   but then plans change, it is important that a document state the
>   new expectation.
>  The draft says that the status section "should include expectations
>   about next steps, and". I don't think that's strong enough as
>   stated.  I think this should be a MUST to send clear signals relevant
>   to the patent policy.

I would be very happy to upgrade this requirement to a MUST. I think it's  
a really important part of the status information, and I often get  
frustrated when I can't find it.

cheers

-- 
Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
       chaals@yandex-team.ru         Find more at http://yandex.com
Received on Thursday, 12 December 2013 11:33:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:35:09 UTC
http://lists.w3.org/Archives/Public/public-w3process/2013Dec/0052.html
lists.w3.org
crawl=CC-MAIN-2019-26
10573
application/http; msgtype=response
sha1:4GI65F5JONZQN34R2NJ3TXCZFJYMU3TF
<urn:uuid:cae53f2f-7a5f-4b2d-8cdc-fe72a03084eb>
2019-06-16T04:46:03Z
128.30.52.41
application/xhtml+xml
sha1:SEWDVB4WACWY25E3VGUX7XCEWVHPRFOW
<urn:uuid:47529cc4-f028-4ec3-8377-81951fbb3a23>
http://lists.w3.org/Archives/Public/public-w3process/2013Dec/0052.html
response
<urn:uuid:66c318ee-18cf-4c78-8480-79a391db42bf>
isPartOf: CC-MAIN-2019-26
publisher: Common Crawl
description: Wide crawl of the web for June 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-143-92-167.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/