Nearby: SWBPD Home, mail archive

Template

SWBPD @@name@@ Task Force Description

NAME

STATUS

• "Considered": the WG is considering to do active work on this issue
• "Active": task force is actively working on (revision of) a deliverable
• "Closed": task force has produced a deliverables and is not active
• "Postponed": the WG does not expect to become active wrt. this issue

The latter should contain some (link to) the rationale for postponement

COORDINATORS

Names of coordinators, typically 1-2

MEMBERS

Task-force members other that the coordinators), typically 2-6

OBJECTIVES

• short-term objectives: realistic goals that the WG can be achieved with consensus: the "low-hanging fruit". Indicate the best practice or the deployment involved.
• longer-term objectives, if any

APPROACH

How you propose to go about achieving your objectives.

SCOPE

Indicate what is in scope and out of scope.

DELIVERABLES

Description of expected results:

• - (revision of) technical note(s)
• - RDF/OWL vocabularies/ontologies
• - ...

When ACTIVE: link to drafts
When: CLOSED: link to published deliverables

TARGET AUDIENCE & USE CASES

Description of the users who are expected to be interested plus some usage examples.

DEPENDENCIES (if any)

• with other task forces.
• with other W3C groups
• outside W3C

Created 2004-06-02 from mail of Guus Schreiber of 2004-03-31
Last updated $Date: 2004/12/09 18:54:08 $ by $Author: swick $