findings 7.55 KB
<?xml version='1.0' encoding='UTF-8'?>
<!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 http-equiv="content-type" content="text/html; charset=UTF-8"/>
  <meta name="keywords" content="TAG, Technical Architecture Group, Web Architecture"/>
  <meta name="description" content="Home page of W3C's Technical Architecture Group"/>
  <title>Findings of the W3C Technical Architecture Group (TAG)</title>
  <link href="http://www.w3.org/2001/tag/style/default.css" rel="stylesheet" type="text/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> Findings
of the W3C Technical Architecture Group (TAG)</h1>
<map id="nearby">
  <p>Nearby: <a href="http://www.w3.org/2001/tag/">TAG home page</a> · <a href="http://www.w3.org/2001/tag/ilist">issues list</a></p>

  <p>The primary activity of the TAG is to develop Architectural
  Recommendations. The TAG findings listed below document fundamental
  principles that should be adhered to by all Web components. The TAG expects
  to include these findings in the TAG's Architectural Recommendations, to be
  published according to the requirements of the <a href="http://www.w3.org/Consortium/Process-20010719/tr#Recs">W3C
  Recommendation Track process</a>.</p>

  <p>This page documents TAG findings, which may either be <a href="#approved">approved</a> or <a href="#draft">draft findings</a>.</p>

  <p>The TAG gathers input from the community as it works on draft findings.
  Once the TAG approves finding, it announces it to www-tag as an approved
  finding. The TAG may review the finding if there is substantial
  opposition.</p>
</map>

<h2><a id="approved" name="approved">Approved findings</a></h2>
<ol>
  <li><a href="http://www.w3.org/2001/tag/2002/01-uriMediaType-9">Mapping
    between URIs and Internet media types</a> (27 May 2002)</li>
  <li><a href="http://www.w3.org/2001/tag/doc/formatting-properties.html">Consistency
    of Formatting Property Names, Values, and Semantics</a> (25 Jul 2002)</li>
  <li><a href="http://www.w3.org/2001/tag/doc/deeplinking-20030911">"Deep
    Linking" in the World Wide Web</a> (11 Sep 2003)</li>
  <li><a href="http://www.w3.org/2001/tag/doc/qnameids.html">Using QNames as
    Identifiers</a> (17 March 2004)</li>
  <li><a href="http://www.w3.org/2001/tag/doc/whenToUseGet.html">URIs,
    Addressability, and the use of HTTP GET and POST</a> (21 March 2004)</li>
  <li><a href="http://www.w3.org/2001/tag/2004/0430-mime">Internet Media Type
    registration, consistency of use</a> (30 April 2004)</li>
  <li><a href="http://www.w3.org/2001/tag/doc/xmlIDSemantics-32.html">How
    should the problem of identifying ID semantics in XML languages be
    addressed in the absence of a DTD?</a> (30 November 2004)</li>
  <li><a href="http://www.w3.org/2001/tag/doc/namespaceState.html">The
    Disposition of Names in an XML Namespace</a> (9 January 2006)</li>
  <li><a href="doc/leastPower.html">The Rule of Least Power</a> (23 February
    2006)</li>
  <li><a href="doc/mime-respect-20060412">Authoritative Metadata</a> (12
    April 2006)</li>
  <li><a href="doc/alternatives-discovery.html">On Linking Alternative
    Formats To Enable Discovery And Publishing</a> (1st November 2006)</li>
  <li><a href="http://www.w3.org/2001/tag/doc/metaDataInURI-31.html">The use
    of Metadata in URIs</a> (2 January 2007)</li> 
  <li><a href="http://www.w3.org/2001/tag/doc/nsDocuments/">Associating
    Resources with Namespaces</a> (25 June 2008)</li>
  <li><a href="http://www.w3.org/2001/tag/doc/selfDescribingDocuments.html">The Self-Describing Web</a> (7 February 2009)</li>
  <li><a href="http://www.w3.org/2001/tag/doc/IdentifyingApplicationState">Identifying Application State</a> (1 December 2011)</li>

</ol>

<h2><a id="draft" name="draft">Draft findings</a></h2>
<ul>
  <li><a href="doc/passwordsInTheClear-52">Passwords in the Clear</a></li>
  <li><a href="http://www.w3.org/2001/tag/doc/abstractComponentRefs.html">Abstract
    Component References</a></li>
  <li><a href="http://www.w3.org/2001/tag/doc/xmlChunkEquality.html">XML
    Chunk Equality</a></li>
  <li><a href="http://www.w3.org/2001/tag/doc/SchemeProtocols.html">URI
    Schemes and Web Protocols</a></li>
  <li><a href="http://www.w3.org/2001/tag/doc/URNsAndRegistries-50.html">URNs,
    Namespaces and Registries</a></li>
  <li><a href="http://www.w3.org/2001/tag/doc/versioning">Extending and Versioning Languages: Terminology</a><br/>
    <a href="http://www.w3.org/2001/tag/doc/versioning-compatibility-strategies">Extending and Versioning Languages: Compatibility Strategies</a><br/>
    <a href="http://www.w3.org/2001/tag/doc/versioning-xml">Extending and Versioning Languages: XML Languages</a></li>
  <li><a href="http://www.w3.org/2001/tag/doc/state.html">State in Web
    application design</a></li>
  <li><a href="http://www.w3.org/2001/tag/doc/httpRange-14/2007-08-31/HttpRange-14">Dereferencing HTTP URIs</a> (Abandoned in favour of "Cool URIs for the Semantic Web")</li>
  <li><a href="http://www.w3.org/TR/hash-in-uri/">Usage Patterns For Client-Side URL parameters</a></li>
</ul>

<h2>Archival findings</h2>
<ul>
  <li><a href="http://www.w3.org/2001/tag/doc/contentPresentation-26.html">Separation
    of semantic and presentational markup, to the extent possible, is
    architecturally sound</a></li>
</ul>

<h2><a id="about" name="about">About TAG findings</a></h2>

<p>At its <a href="http://www.w3.org/2002/11/04-tag-summary#findings">4 Nov
2002 teleconference</a>, the TAG agreed to adopt the following policy for
managing findings versions.</p>

<p>A finding draft should be treated like a W3C technical report:</p>
<ul>
  <li>After announcement of a draft, we don't modify it.</li>
  <li>Each draft has a latest/this version URI and links to the previous
    version.</li>
  <li>The status section of a finding draft indicates whether the document is
    a draft/for review in light of TAG consensus/ approved by the TAG.</li>
</ul>

<p>Having approved a finding:</p>
<ul>
  <li>For minor changes thereafter, we continue to publish updates using the
    same "latest version URI" (i.e., it remains part of the same document
    series). It is possible for the latest version of the series to be "not
    yet approved". That should be a temporary state, however. Findings in an
    intermediate state should refer to the previous approved version.</li>
  <li>For major changes, we can start a new series (with a different "latest
    version URI"). If we start a new series, the new series should explain
    its relation to the old one (e.g., whether the new series supersedes the
    old series).</li>
</ul>
<hr/>
<address>
  <a href="http://www.w3.org/People/Berners-Lee">Tim Berners-Lee</a>, Noah Mendelsohn, co-chair<br/>
  Last modified: $Date: 2011/12/21 23:15:09 $ by $Author: nmendels $ 
</address>

<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>©
2002 <a href="http://www.w3.org/">W3C</a><sup>®</sup> (<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="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
<a href="http://www.w3.org/Consortium/Legal/copyright-documents">document
use</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-software">software
licensing</a> rules apply.</p>
</body>
</html>