contributor 6.55 KB
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<title>TAG Contributor Policies</title>
<meta http-equiv="Content-Type" content="text/html" />
<link rel="stylesheet" type="text/css" href="style/default.css" />
</head>
<body>
<h1><a href="http://www.w3.org/" title="W3C Home"><img alt="W3C"
height="48" src="http://www.w3.org/Icons/w3c_home" width="72"
border="0" /></a> TAG Contributor Policies</h1>

<p><a href="#copyright">copyright</a> &middot; <a
href="#roles">document roles</a></p>

<p>This document describes the contributor and copyright policies
associated with products of the <a href="/2001/tag/">W3C Technical
Architecture Group</a>.</p>

<p>TAG participants who are not employees of a W3C Member
organization must agree to the <a
href="/Consortium/Legal/collaborators-agreement">W3C invited expert
and collaborators agreement</a> (per <a
href="http://www.w3.org/Consortium/Process-20010719/groups#JoinGroups">
section 4.2.3</a> of the W3C Process Document).</p>

<h2><a id="copyright" name="copyright">Copyright</a></h2>

<p>Technical reports published by the TAG will bear the following
copyright notice:</p>

<blockquote>
<p><a
href="/Consortium/Legal/ipr-notice.html#Copyright"></a>Copyright
&nbsp;&copy;&nbsp;2002 <a href="http://www.w3.org">W3C</a> (<a
href="http://www.lcs.mit.edu">MIT</a>, <a
href="http://www.inria.fr/">INRIA</a>, <a
href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C
<a
href="/Consortium/Legal/ipr-notice.html#LegalDisclaimer">liability</a>,
<a
href="/Consortium/Legal/ipr-notice.html#W3CTrademarks">trademark</a>,
<a href="/Consortium/Legal/copyright-documents.html">document
use</a> and <a
href="/Consortium/Legal/copyright-software.html">software
licensing</a> rules apply.</p>
</blockquote>

<p>TAG participants who are not willing to contribute under these
terms must refrain from doing so and notify the Chair as to the
reason why.</p>

<p><strong>Note:</strong> Patent disclosures must be made by TAG
participants as discussed on the <a href="disclosures">TAG
patent disclosure page</a>.</p>

<h2><a id="roles" name="roles">Document roles</a></h2>

<p>The <a href="/2001/07/19-tag">TAG charter</a> sets expectations
that all TAG participants are expected to contribute to
Architectural Recommendations:</p>

<blockquote>
<p>W3C Members are encouraged to nominate individuals who: ...[a]re
available to spend approximately 25% percent of their time writing
and resolving issues.</p>
</blockquote>

<p>This document describes three levels of contribution towards
written work: Editor, Author, and Contributor.</p>

<dl>
<dt><a id="Editor" name="Editor">Editor</a></dt>

<dd>Editors are responsible for reflecting the proposals and
consensus of the WG within the specification. From <a
href="http://www.w3.org/Consortium/Process-20010719/tr#Recs">section
5.2</a> of the W3C Process Document, "Every technical report on the
Recommendation track is edited by one or more editors appointed by
a Working Group Chair. It is the responsibility of these editors to
ensure that the decisions of the group are correctly reflected in
subsequent drafts of the technical report. Editors are not required
to be part of the Team."</dd>

<dt><a id="Author" name="Author">Author</a></dt>

<dd>Authors by their own initiative or through commitments to the
Chair make substantive contributions that are included within a
specification. Frequently an author will make and write a proposal
that becomes the basis of a section of the specification. Criteria
for authorship are the expressed interest (agreed to by the Chair)
to be listed as an author and the substance and quality of
contributions. The Chair looks at the consistency of participation,
the willingness to take action items, and how much "authoring" the
TAG participant actually accomplished. These criteria are somewhat
relative in that, if this role is designated, the Chair wishes to
list the top handful of people that consistently plugged away on
the work and to avoid a list of names that occupies the first two
pages of the specification. Where the number of authors/editors are
small, the Author and Editor roles are frequently collapsed into
the Editor designation. Where there are may authors, the role will
be a specified subset of the Contributor designation which is an
Appendix to the specification.</dd>

<dt><a id="Contributor" name="Contributor">Contributor</a></dt>

<dd>Contributors are the many important TAG participants or non-TAG
commenters who provide the ideas, comments, feedback and
implementation experience that make the specification meaningful.
Criteria for the contributor role are an expressed interest to be
listed as a contributor to the document and the quality of
contributions, as determined by the Chair. The assessment of
quality is based on the consistency of participation on the email
list, participation in teleconferences and face-to-face meetings as
appropriate, and a responsiveness to open TAG issues. In reality,
this criteria are fairly relaxed in that the Chair wishes to
include all of those that helped, while not weakening that
acknowledgement through the inclusion of individuals who
contributed only slightly. Contributors are listed as an appendix
to the specification.</dd>
</dl>

<p>W3C does not have a clear process for defining the role of
author as it appears on a W3C technical report. It has become clear
through experience that this distinction is sometimes a useful one
within a Working Group. In general, only the document editors are
listed on the <a href="http://www.w3.org/TR">W3C Technical Reports
page</a>. In deciding attribution, the Chair will consider a final
formulation that is reasonably terse but as fair as possible to all
involved.</p>

<h3><a id="changes" name="changes">Changes in attribution</a></h3>

<p>In the event that a TAG participant discontinues participation
in one of the roles above, the Chair has the option of changing or
removing acknowledgment Criteria for removal include duration and
reason of absence, as well as the weight of previous contributions
to the present draft. The goal is to give credit where credit is
due, but not to carry forward attributions that are no longer
relevant.</p>

<hr />
<address><a href="/People/Jacobs/">Ian Jacobs</a><br />
 This document draws heavily on the <a
href="/Signature/Contributor">XML Signature Working Group
Contributor policy</a>, by Joseph Reagle and Donald Eastlake
III<br />
 Last revised: $Date: 2002/01/20 23:17:01 $</address>
</body>
</html>