- From: Charles McCathie Nevile <chaals@yandex-team.ru>
- Date: Mon, 17 Feb 2014 19:52:52 +0100
- To: "Ian Jacobs" <ij@w3.org>
- Cc: "public-w3process@w3.org Community Group" <public-w3process@w3.org>
On Mon, 17 Feb 2014 19:25:33 +0100, Ian Jacobs <ij@w3.org> wrote:
> Charles,
>
> Here is an analysis of the redundancy of information on Notes in the 5
> Feb 2014
> draft chapter 7 [1]. In particular:
>
> * Definition of Note (3x)
> * Examples (3x)
> * Used to stop work on Rec (2x)
> * No prior WD required (2x)
>
> In separate email I will propose changes.
Before you do, please look at the 14 feb draft (or the one I will push
tonight, but on notes they are the same), where I revised the text as
explained in the previous dicsussion on this topic.
cheers
> Ian
>
> [1] https://dvcs.w3.org/hg/AB/raw-file/acebbefd27bb/tr.html
>
> -----------------------------------
> Assertions in 7.1 W3C Technical Reports
>
> * EXISTENCE (not quite a definition)
>
> Groups may also publish documents as W3C Notes.
>
> * EXAMPLES:
>
> The two common purposes for Notes are
>
> - to document information that is not a formal technical
> specification, such as use cases motivating a specification and
> best practices for its use, and
> - to clarify the status of work that is abandoned, that there is no
> longer interest in completing it so it should not be assumed that
> will become a standard.
>
> * MAY HAVE PRIOR WD BUT NO PRIOR WD REQUIRED:
>
> Some W3C Notes are developed through successive Working Drafts,
> with an expectation that they will become Notes, while others are
> simply Published.
> * TRANSITION REQUIREMENTS
>
> There are few formal requirements to publish a document as a W3C
> Note...
> * DEFINITION:
>
> ....and they have no standing as a recommendation of W3C, but are
> simply documents preserved for historical reference.
>
>
> Assertions in 7.1.2 Maturity Levels
>
> * DEFINITION:
>
> A Working Group Note or Interest Group Note is published by a
> chartered Working Group or Interest Group to provide a stable
> reference for a document that is not intended to be a specification
> requiring conformance, but is nevertheless useful.
>
> * EXAMPLES:
>
> Examples include supporting documents such as Use case and
> Requirements documents, Design Principles that explain what the
> Working Group was trying to achieve with a specification, or 'Good
> Practices" documents.
>
> * USED TO STOP WORK ON REC
>
> A Working Group may also publish a specification as a Note if they
> stop work without producing a Recommendation.
>
> * NO PRIOR WD REQUIRED
>
> A Working Group or Interest Group may publish a Note with or
> without its prior publication as a Working Draft.
>
>
>
> Assertions in 7.3.3 Stopping Work on a specification
>
> * REQUIRED TO STOP WORK ON REC (WHEN GROUP CLOSES)
>
> If the Director closes a Working Group W3C must publish any
> unfinished specifications on the Recommendation track as Working
> Group Notes.
>
> * REQUIRED TO STOP WORK ON REC (IN OTHER CASES)
>
> If a Working group decides, or the Director requires, the Working
> Group to discontinue work on a technical report before completion,
> the Working Group should publish the document as a Working Group
> Note.
>
>
>
> Assertions in 7.8 Publishing a Working Group or Interest Group Note
>
> * DEFINITION:
>
> Working Groups and Interest Groups publish material that is not a
> formal specification as Notes.
>
> * EXAMPLES:
>
> This may include supporting documentation for a specification, such
> as requirements, use cases, good practices and the like, as well as
> specifications where work has been stopped and there is no longer
> interest in making them a new standard.
>
> * TRANSITION REQUIREMENTS:
>
> In order to publish a Note a Working Group or Interest Group: ...
>
>
>
> --
> Ian Jacobs <ij@w3.org> http://www.w3.org/People/Jacobs
> Tel: +1 718 260 9447
>
>
>
--
Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
chaals@yandex-team.ru Find more at http://yandex.com
Received on Monday, 17 February 2014 18:53:24 UTC