ISSUE-119: Description of the Activity/Charter's scope

CharterScope

Description of the Activity/Charter's scope

State:

CLOSED

Product:

Process Document

Raised by:

Steve Zilles

Opened on:

2014-08-26

Description:

In Section 5.6 Activity Proposals there is the following,
"A description of the Activity's scope. How might a potential Recommendation interact and overlap with existing international standards and Recommendations? What organizations are likely to be affected by potential overlap (see the section on liaisons with other organizations)? What should be changed if the Activity is approved?"

Issue: Do we need this info beyond the dependency information already required?

Suggested Resolution:
The current Process Document in section 6.2.6 Working Group and Interest Group Charters says a charter MUST include the following information (a subset thereof):
"Any dependencies by groups within or outside of W3C on the deliverables of this group. For any dependencies, the charter MUST specify the mechanisms for communication about the deliverables;

Any dependencies of this group on other groups within or outside of W3C. For example, one group's charter might specify that another group is expected to review a technical report before it can become a Recommendation. For any dependencies, the charter MUST specify when required deliverables are expected from the other groups. The charter SHOULD set expectations about how coordination with those groups will take place; see the section on liaisons with other organizations. Finally, the charter SHOULD specify expected conformance to the deliverables of the other groups;"

This is similar to, but not the same as the Activity Proposal requirements which are expressed in terms of what organizations or work will be affected by the Activity/WG rather than "dependencies".

Perhaps, those affected should be listed as well as dependencies.
T

Related Actions Items:

No related actions

Related emails:

1. w3process-ISSUE-119 (CharterScope): Description of the Activity/Charter's scope [Process Document] (from sysbot+tracker@w3.org on 2014-08-26)

Related notes:

Display change log