f2fkc-agenda 23.9 KB

Raw Blame History Permalink

<?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="application/xhtml+xml; charset=UTF-8" />
<title>Agenda for TAG F2F Meeting in Kansas City, Missouri 23-25th September 2008</title>
<link href="http://www.w3.org/StyleSheets/base.css" rel="stylesheet" type="text/css" />
<style type="">
<!--
DIV.PlainText {
	FONT-SIZE: 120%;
	FONT-FAMILY: monospace
}

p.highlight {color ="red";background-color ="#FFFFCC"

}
-->
</style>
</head>

<body>

<p><a href="http://www.w3.org/">W3C</a> | <a href="http://www.w3.org/2001/tag/"> TAG</a> | Previous teleconference:
<a href="http://www.w3.org/2001/tag/2008/09/11-minutes">11th</a> Sept&nbsp; | Next teleconference: 2nd October 2008.</p>
<h1>TAG face-to-face meeting, 23rd-25th September 2008<br />
<a href="http://www.kauffman.org/">Ewing Marion Kauffman Foundation</a>, Kansas City, Missouri.</h1>

<div class="photo">
<img src="24-TagKansasCityGroupPicture.jpg" alt="9 TAG members in front of the Kauffman foundation conference center" />
<p>Ashok, Stuart, Norm-by-phone, Noah, Dave, Henry, Tim, Dan, Jonathan, Raman (with Hubbell)</p>
</div>

<p>Nearby: <a href="http://www.w3.org/2001/tag/group/track/">TAG Issues Tracker</a> - <a
	href="http://www.w3.org/2001/tag/findings">findings</a> - <a href="http://lists.w3.org/Archives/Public/www-tag/">www-tag
archive</a> - <a href="http://lists.w3.org/Archives/Member/tag/">tag archive</a></p>
<h2>Meeting at a glance</h2>
<table border="1" cellpadding="1" cellspacing="1">
	<tbody>
		<tr>
			<th bgcolor="#BEBEBE">Tue 23rd Sep</th>
			<td><b>Agenda</b></td>
			<th>Minutes</th>
		</tr>
		<tr>
			<td align="left" valign="top">09:00-10:30</td>
			<td align="left" valign="top"><a href="#convene">Convene</a><br />
			<a href="#URNsAndRegistries-50">URNsAndRegistries-50</a><br />
			<a href="#binaryXML-30">binaryXML-30</a></td>
			<td rowspan="5">
<ol>
	<li><a href="23-minutes#item01">Convene, review agenda</a></li>
<li><a href="23-minutes#item02">FTF meeting schedule</a></li>
<li><a href="23-minutes#item03">TAG at TPAC 2008</a></li>
<li><a href="23-minutes#item04">URNsAndRegistries-50</a></li>
<li><a href="23-minutes#item05">binaryXML-30</a></li>
<li><a href="23-minutes#item06">HTML and Web: the Big Picture</a></li>
<li><a href="23-minutes#item07">HTML5 should be modularized?</a></li>
<li><a href="23-minutes#item08">URI Parsing in HTML5</a></li>
</ol>
</td>
		</tr>
		<tr>
			<td align="left" valign="top">11:00-12:30</td>
			<td align="left"><a href="#htmlAndWebBigPicture">HTML and Web: the Big Picture</a></td>
		</tr>
		<tr>
			<td align="left" valign="top" bgcolor="#FFFFCC">12:30-13:30</td>
			<td align="left" valign="top" bgcolor="#FFFFCC">Lunch</td>
		</tr>
		<tr>
			<td align="left" valign="top">13:30-15:00</td>
			<td align="left" valign="top"><a href="#html5Modularization"> Modularized HTML5?</a></td>
		</tr>
		<tr>
			<td align="left" valign="top">15:30-17:00</td>
			<td align="left" valign="top"><a href="#html5andURI">URI parsing in HTML5</a></td>
		</tr>
		<tr>
			<th bgcolor="#BEBEBE">Wed 24th Sep</th>
			<td align="left" valign="top">&nbsp;</td>
			<th>Minutes</th>
		</tr>
		<tr>
			<td align="left" valign="top">09:00-10:30</td>
			<td align="left" valign="top"><a href="#selfDescribingWeb">Self Describing Web</a></td>
			<td align="left" valign="top" rowspan="5">

	<ol>
	<li><a href="24-minutes#item01">3.5 Self Describing Web</a></li>
<li><a href="24-minutes#item02">3.4.4 HTTP And HTML</a></li>
<li><a href="24-minutes#item03">HTML5: Embedding And Embedability</a></li>
<li><a href="24-minutes#item04">Uniform access to metadata</a></li>

	</ol>
</td>
		</tr>
		<tr>
			<td align="left" valign="top">11:15-12:30</td>
			<td align="left" valign="top"><a href="#httpAndHtml">HTTP and HTML</a></td>
		</tr>
		<tr>
			<td align="left" valign="top" bgcolor="#FFFFCC">12:30-13:30</td>
			<td align="left" valign="top" bgcolor="#FFFFCC">Lunch</td>
		</tr>
		<tr>
			<td align="left" valign="top">13:30-15:00</td>
			<td align="left" valign="top"><a href="#html5Embedding">HTML5 Embedding and Embedability</a></td>
		</tr>
		<tr>
			<td align="left" valign="top">15:30-17:00</td>
			<td><a href="#tagSoupPlanning"> tagSoupIntegration-54: How to move Forward</a></td>
		</tr>
		<tr>
			<th bgcolor="#BEBEBE">Thur 25th Sep</th>
			<td>&nbsp;</td>
			<th>Minutes</th>
		</tr>
		<tr>
			<td align="left" valign="top">09:00-10:30</td>
			<td><a href="#passwordsInTheClear-52">passwordsInTheClear-52</a></td>
			<td rowspan="6">

      <ol>
        <li><a href="25-minutes#item01">issue passwordsInTheClear-52</a></li>

        <li><a href="25-minutes#item02">XMLVersioning-41</a></li>

        <li><a href="25-minutes#item03">Thanks to the host</a></li>

        <li><a href="25-minutes#item04">XMLVersioning-41 (cont)</a></li>

        <li><a href="25-minutes#item05">wrap up on HTML</a></li>

        <li><a href="25-minutes#item06">binaryXML</a></li>

        <li><a href="25-minutes#item07">Postscript: versioning
        formalism</a></li>
      </ol>

</td>
		</tr>
		<tr>
			<td align="left" valign="top">11:00-12:30</td>
			<td><a href="#XMLVersioning-41">XMLVersioning-41</a></td>
		</tr>
		<tr>
			<td align="left" valign="top" bgcolor="#FFFFCC">12:30-13:30</td>
			<td align="left" valign="top" bgcolor="#FFFFCC">Lunch</td>
		</tr>
		<tr>
			<td align="left" valign="top">13:30-15:00</td>
			<td align="left" valign="top"><a href="#XMLVersioning-41">XMLVersioning-41 (cont)</a></td>
		</tr>
		<tr>
			<td align="left" valign="top">15:30-16:00</td>
			<td align="left" valign="top"><a href="#wrapUp">Wrapup/AOB</a></td>
		</tr>
	</tbody>
</table>

<p>&nbsp;</p>
<h2 id="Logistics">Logistics</h2>
<p>(also separate <a href="ftfkc.html">Logistics</a> page)</p>
<h2 id="reading">2. Preparation</h2>

<p>Participants are expected to read materials in the <strong>Preparation</strong> sections under each item below in
advance of the meeting.</p>

<p><small>TAG members are presumed to be familiar with the <a
	href="http://www.w3.org/2004/10/27-tag-charter.html">TAG Charter</a></small>.</p>


<hr />
<h2 id="agenda">3. Agenda</h2>
<h3><a name="convene">3.1 Convene</a></h3>
<ul>
	<li><b>Pre-flight checks!</b>
	<ul>
		<li>Local logistics.</li>
		<li>Agenda Review</li>
	</ul>
	</li>
	<li><b>Future Meetings</b>
	<ul>
		<li>Proposed Wed-Fri 10-12 Dec 2008: Cambridge Mass
		<ul>
			<li>Offer still good?</li>
			<li><a href="http://www.w3.org/2002/09/wbs/34270/200812-F2FDecision/results">WBS Poll results</a></li>
		</ul>
		</li>
	</ul>
	</li>
	<li><b>TAG at TPAC 2008</b>
	<ul>
		<li>Liason Meetings
		<ul>
			<li>Requests/Invitations from:
			<ul>
				<li>WebApps WG on the topic of URI Schemes for Widgets (forwarded <a
					href="http://lists.w3.org/Archives/Member/tag/2008Sep/0073">request</a> and <a
					href="http://lists.w3.org/Archives/Member/tag/2008Sep/0074">response</a>)</li>
				<li>WAI-PF invitation to observe (forwarded <a href="http://lists.w3.org/Archives/Member/tag/2008Sep/0085">invitation</a>)</li>
			</ul>
			</li>
			<li>Requests sent to: (none)</li>
		</ul>
		</li>
		<li>AC Meeting Report</li>
		<li>Plenary Day</li>
	</ul>
	</li>
</ul>
<hr />
<h3><a name="URNsAndRegistries-50">3.2 URNsAndRegistries-50</a></h3>

<h4><span style="font-weight: 400">Our goals for this session are: to review progress and direction of our
work on UrnsAndRegististres-50; to review the progress of the dialog between the TAG and the OASIS XRI TC.</span></h4>

<h4>Background for reference</h4>
		<ul>
			<li><em style="font-style: normal">Current draft finding </em><em> <a
				href="http://www.w3.org/2001/tag/doc/URNsAndRegistries-50.html">URNs, Namespaces and Registries</a></em> 1.13 2006/08/17</li>
	<li><a href="http://lists.w3.org/Archives/Member/tag/2008Sep/0088">Possible
	directions for XRI TC</a> 15 Sep 2008 (tag internal)</li>
		</ul>

<h4>Preparation</h4>
<ul>
	<li><cite><a href="http://www.w3.org/2001/tag/doc/justSayHTTP">Dirk and Nadia design a naming scheme</a></cite> draft 16 Sep 2008
	</li>
	<li><a href="http://wiki.oasis-open.org/xri/AbstractIdentifierArchitecture">AbstractIdentifierArchitecture</a> in
	the OASIS XRI TC Wiki<br />
	2008-09-04 01:42:20 <!-- that's the date as of this writing; if they update it, we should check the diffs --></li>
</ul>
<hr />

<h3><a name="binaryXML-30">3.3 binaryXML-30</a></h3>
<p>Our goals for this session is to checks the status of TAG interaction with the EXI-WG;
review our progress in reviewing their publications; and discuss a LC review
<a href="http://lists.w3.org/Archives/Member/tag/2008Sep/0087">request</a> from
the WG. </p>
<ul>
	<li>Related Action Items:
	<ul>
     <li><a href="http://www.w3.org/2001/tag/group/track/actions/93">ACTION-93</a> on Henry S. Thompson: Review EXI
		WDs since 20 Dec - due <span class="date overdue">2008-02-25</span> - open</li>
    </ul></li>
    <li>Background<ul>
     <li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0224">[binaryXML-30] Binary XML problem statement</a>
     from Chris Lilley (2003)</li>
     <li><a href="http://lists.w3.org/Archives/Public/www-tag/2007Nov/0065">TAG
    input to EXI WG on Efficient XML Interchange and EXI Measurements</a> and
     <a href="http://lists.w3.org/Archives/Public/www-tag/2007Dec/0094">response</a>
     (Nov/Dec 2007)</li>
    </ul></li>
    <li>'Recent' FP-WDs
    <ul>
     <li>First Public Working Draft of the
     <a href="http://www.w3.org/TR/exi-impacts">Efficient XML Interchange
		Impacts</a> Note, 3 September, 2008</li>
     <li>Fourth Public Working Draft of the spec itself:
     <a
		  href="http://www.w3.org/TR/2008/WD-exi-20080728/">Efficient XML Interchange (EXI) Format
		  1.0</a>, 28 July 2008</li>
     <li>First Public Working Draft of the
     <a href="http://www.w3.org/TR/2008/WD-exi-evaluation-20080728/">Efficient
		XML Interchange Evaluation Note</a>, 28 July 2008</li>
     <li><strong>EXI Primer </strong>,
     <a href="http://www.w3.org/TR/2007/WD-exi-primer-20071219">First Public
		Working Draft, 19 December 2007</a>.</li>
     <li><strong>EXI Best Practices </strong>,
     <a href="http://www.w3.org/TR/2007/WD-exi-best-practices-20071219">First
		Public Working Draft, 19 December 2007</a>.</li>
    </ul></li>
</ul>

<hr />
<h3>3.4 <a href="http://www.w3.org/2001/tag/group/track/issues/53">tagSoupIntegration-54</a> -
<a name="HTMLandTheWeb">HTML and The Web</a></h3>
<div class="outline-2" id="outline-container-1">
<div id="text-1">

<blockquote>We are planning to spend a total of 1.5 days on this topic, i.e. half the F2F. The F2F is being
organized as 4 90 minute sessions a day, so I'm assuming we get 6 sessions. I'll assign a core issue to each of 4 90
minute sessions, leave the first session for a high-level overview of issues with respect to how design decisions in
HTML affect the rest of the Web stack, and leave the final 90 minute session for defining global action items for the
TAG. My expectation is that each of the topic-focused 90 minute sessions end with their own action items.
<address><a href="mailto:raman@google.com">T.V. Raman</a></address>
</blockquote>

<p><em>Note tag-internal discussion of meeting goals <a
	href="http://lists.w3.org/Archives/Member/tag/2008Aug/0032.html">Re: updated Agenda 13 Aug</a> and following</em>.</p>

<hr />
</div>
<div class="outline-3">
<h3><a name="htmlAndWebBigPicture">3.4.1 HTML And Web The Big Picture</a></h3>
<div>When the world-view was <pre
	style="font-family: courier, monospace; font-size: 90%; border: 1pt solid #AEBDCC; padding: 5pt; background-color: #F3F5F7"> HTML will move to XML
</pre> the question of how other Web technologies integrated with HTML was usually answered by saying <pre
	style="font-family: courier, monospace; font-size: 90%; border: 1pt solid #AEBDCC; padding: 5pt; background-color: #F3F5F7"> XML will bring it all together.
</pre>
<p>However, that is no longer the case, there is now little or no hope of the HTML5 world converging with the XML
family of languages. HTML5 has an XML serialization that is a second-class citizen at best as far as that community is
concerned. In the above I said HTML and Web technologies — but that is just my perspective. The HTML5 community would
define themselves as encompassing <i>all</i> Web technologies, i.e., if it&#39;s not HTML5 and implemented in a browser,
it&#39;s not the Web. Personally that is a view that I do not subscribe to, but it&#39;s important for the TAG to have
thought about where we stand globally on this before we get to concrete details, since one&#39;s technical stand on any
of the issues that arise is deeply affected by the above.</p>
<p>If you take the world-view that the Web is more than a Web Browser, and that Web technology means more than just
HTML, then the core issue that underlies each specific technical issue is the following:</p>
<pre
	style="font-family: courier, monospace; font-size: 90%; border: 1pt solid #AEBDCC; padding: 5pt; background-color: #F3F5F7"> How do you make sure that  XML technologies can co-exist on the Web alongside HTML
without necessarily having  HTML&#39;s sloppiness leaking  into all Web languages?
</pre></div>

<h3>Preparation</h3>
<ul>
	<li><cite><a href="http://www.w3.org/2008/Talks/0519-htxml-tbl/text">HTML and XML</a></cite> v 1.20 2008/09/07
	(tag internal)</li>
</ul>


<hr />
</div>
<div class="outline-3" id="outline-container-1.2">
<h3 id="sec-1.2"><a name="html5Modularization">3.4.2 Issue: HTML5 Should Be Modularized?</a></h3>
<div id="text-1.2">
<ul>
	<li>Modular specs make for easier review, and make addressing issues tractable. At present, each issue that is
	raised loops back to something else, and worse, the spec is not getting the architectural review it deserves.</li>
	<li>The spec is being cherry-picked by implementations with everyone claiming they&#39;re implementing it. But
	they are all implementing different parts of it.</li>
	<li>Propose a reasonable breakdown based on prior experience.
	<ul>
		<li>Parsing</li>
		<li>DOM</li>
		<li>Serialization (canonical serialization) XML and HTML.</li>
		<li>Semantics of related groups of elements.</li>
		<li>Interaction with CSS</li>
		<li>Interaction with other Web languages –both embedding and being embeded.</li>
	</ul>
	</li>
</ul>

<h4>Preparation</h4>

<ul>
	<li><a href="http://lists.w3.org/Archives/Public/public-html/2007JanMar/0096.html">Re: brainstorming: test
	cases, issues, goals, etc.</a> 14 Mar 2007 23:12:55 +0000 regarding dependencies between parts of the spec</li>
	<li><a href="http://lists.w3.org/Archives/Public/www-tag/2008May/0087.html">Re: Invitation to the TAG to
	provide feedback on HTML5</a> 21 May 2008 21:17:20 +0000</li>

</ul>

</div>
<hr />
</div>
<div class="outline-3" id="outline-container-1.3">
<h3 id="sec-1.3"><a name="html5andURI">3.4.3 URL Parsing In HTML5</a></h3>
<div id="text-1.3">As the underlying authoring language for the Web, HTML by definition has to be able to utter
phrases in all of the Web&#39;s basic technologies, e.g. URLs. Traditionally, building blocks like URLs have been
specified outside of HTML, since they need to be used in more than just HTML. This has also left the question of error
recovery underspecified. At present, HTML5 is attempting to rectify such <i>under-specified error recovery</i> by trying
to write down all of the rules for moving from a sequence of bytes to a URL. This necessarily introduces aspects of the
overall HTML5 parsing, and might over time lead to HTML5 error behavior bleeding into the rest of the Web that is more
than just browsers.

<h4>Preparation</h4>
<ul>
	<li><a href="http://lists.w3.org/Archives/Public/public-html/2008Jun/thread.html#msg348">heads-up about "new"
	URLs section in HTML5 editor's draft</a> thread 27 to 30 June 2008, ending with <a
		href="http://www.w3.org/2002/02/mid/4868B926.8@Rhul.Ac.Uk;list=public-html">endorsement of an objection</a></li>
</ul>

&nbsp;</div>
<hr />
</div>
<div class="outline-3" id="outline-container-1.4">
<h3 id="sec-1.4"><a name="httpAndHtml">3.4.4 HTTP And HTML</a></h3>
<div id="text-1.4">The Web has been built on (HTTP, URL, HTML). HTML5 impinges on many parts of the HTTP
specification and its use. The <a href="http://lists.w3.org/Archives/Public/public-html/2008Jan/0129.html"> _ping_</a>
attribute generated much heat and little light before the FF3 launch, and that issue has moved to the back-burner,
mostly because FF3 decided to postpone implementing it. But this is not a resolved issue, and HTML5 has many places
where it impinges on HTTP. This is of concern wherever those points of intersection are being designed purely from the
perspective of the browser. I believe there should be more coordination with the work on updating HTTP that is presently
ongoing in the IETF. At present (and this is but a rough sketch) the browser vendors appear to be doing HTML5, everyone
else is doing HTTP.
<p>Another core issue that lies at the intersection of HTTP and HTML is the issue of:</p>
<pre
	style="font-family: courier, monospace; font-size: 90%; border: 1pt solid #AEBDCC; padding: 5pt; background-color: #F3F5F7">Content-Type Sniffing
</pre>

<p><em>For reference, that's <a href="http://www.w3.org/html/wg/tracker/issues/28">ISSUE-28
http-mime-override</a> in the HTML WG tracker.</em></p>

<h4>Preparation</h4>

<ul>
	<li><a href="http://www.w3.org/2002/02/mid/4E2E32D6-1AD4-4EEF-9E7E-F043A2868ECB@gbiv.com;list=public-html">Re:
	several messages about content sniffing in HTML</a> 29 Feb 2008</li>
	<li>section <a href="http://www.w3.org/html/wg/html5/#content-type-sniffing">2.7 Determining the type of a
	resource</a> in <cite><a href="http://www.w3.org/html/wg/html5/">HTML 5</a></cite> editor's draft 11 September 2008 (or
	later)
	<p><em>Note that a <a href="http://lists.w3.org/Archives/Public/public-html/2007Aug/0678.html">17 Aug 2007
	message from Hickson</a> notes other related sections.</em></p>
	</li>
</ul>

</div>
<hr />
</div>
<div class="outline-3" id="outline-container-1.5">
<h3 id="sec-1.5"><a name="html5Embedding">3.4.5 HTML5: Embedding And Embedability</a></h3>
<div id="text-1.5">The issue of <a href="http://www.w3.org/html/wg/tracker/issues/41">distributed
extensibility</a> and namespaces has been beaten to death. I don't believe anyone in either camp can really be made to
change their minds at this point with regard to XML namespaces. The latest proposal from the HTML5 editor to enable
extensibility is to stick whatever globally unique identifier one wants in the <u>class</u> attribute. This brings us
back to something I observed in 2001 <pre
	style="font-family: courier, monospace; font-size: 90%; border: 1pt solid #AEBDCC; padding: 5pt; background-color: #F3F5F7">Given CSS and JavaScript, HTML can be reduced to _div_ and _span_.
</pre> I later revised this to: <pre
	style="font-family: courier, monospace; font-size: 90%; border: 1pt solid #AEBDCC; padding: 5pt; background-color: #F3F5F7"> display:inline allows you reduce this to just one element --- _div_
</pre>
<p>Distributed extensibility ends up reducing to a power-struggle between browser vendors who want to dictate what
the vocabulary of the Web is — and content creators who do not want to cede this right entirely to the browser. I
believe this power struggle to be the root cause of all of the tension that can be observed whenever this issue is
brought up.</p>
<p>At this point, I believe we should let the marketplace decide --- it will anyway, with or without the TAG.</p>
<p>But there is a more fundamental design issue that needs to be addressed in this context with respect to the
top-level <i>co-existence</i> question we asked in our first session:</p>
<pre
	style="font-family: courier, monospace; font-size: 90%; border: 1pt solid #AEBDCC; padding: 5pt; background-color: #F3F5F7">Embedding And Embeddability
</pre>
<ol>
	<li>Given an XML-based language e.g., ATOM, how does one embed HTML content fragments without the HTML5 slopping
	out into the XML? At present, the only answer is to make the HTML payload a CData section, but in that case, you might
	as well use something equally opaque like PostScript or PDF.</li>
	<li>How does one host/embed other languages inside HTML5 e.g., MathML, SVG, or other vocabularies?</li>
</ol>
</div>


<h4>Preparation</h4>

<ul>
	<li><a href="http://lists.w3.org/Archives/Public/public-html/2008Mar/thread.html#msg39">SVG and MathML in
	text/html</a> thread 9-16 March 2008</li>
</ul>

<hr />
</div>
<div class="outline-3" id="outline-container-1.6">
<h3 id="sec-1.6"><a name="tagSoupPlanning">3.4.6 tagSoupIntegration-54 How To Move Forward</a></h3>
<div id="text-1.6">This session is for the TAG as a whole to decide how and if we want to move forward with the
overall issue of TAG Soup integration. <br />
&nbsp;</div>
</div>
</div>
<hr />
<h3><a name="selfDescribingWeb">3.5 Self Describing Web</a></h3>

<p>Our goal for this session is to reach agreement to publish the TAG Finding titled: <a
	href="http://www.w3.org/2001/tag/doc/selfDescribingDocuments">The Self-Describing Web</a>. Norm Walsh and Stuart
Williams took an action in Bristol to do reviews, and the results of those reviews were generally supportive of
publication (<a href="http://lists.w3.org/Archives/Public/www-tag/2008Aug/0122.html">Norm's review</a>, <a
	href="http://lists.w3.org/Archives/Public/www-tag/2008Sep/0000.html">Stuart's original review</a> and Stuart's
followups <a
	href="http://lists.w3.org/Archives/Public/www-tag/2008Sep/0002.html
">here</a>, <a
	href="http://lists.w3.org/Archives/Public/www-tag/2008Sep/0008.html
">here</a>, and <a
	href="http://lists.w3.org/Archives/Public/www-tag/2008Sep/0009.html
">here</a>).</p>
<p>The principle question that's still known to be a point of debate is whether the normative specifications do or
do not suport the claim that RDFa embedded in an <code>application/xhtml+xml</code> document retrieved via HTTP is
self-describing, in the sense that the server can be held responsible for triples inferred from the RDFa. See <a
	href="http://lists.w3.org/Archives/Public/www-tag/2008Sep/0013.html">email from Noah</a>, as well messages linked from
that email, and others in the same threads.</p>

<h4>Preparation</h4>
<ul>
	<li><cite><a href="http://www.w3.org/2001/tag/doc/selfDescribingDocuments-2008-09-08">The
	Self-Describing Web</a></cite> Draft Tag Finding 08 September 2008 (<a
		href="http://lists.w3.org/Archives/Public/www-tag/2008Sep/0014">cover note</a>)</li>
</ul>

<hr />
<p>&nbsp;</p>
<h3><a name="passwordsInTheClear-52">3.6 passwordsInTheClear-52</a> (<a
	href="http://www.w3.org/2001/tag/group/track/issues/52">ISSUE-52</a>)</h3>
<p>Our goal for this session is to review the most recent draft of the related draft finding and the message that we
want it to convey.</p>

<h4>Preparation</h4>
<ul>
	<li><em><cite> <a href="http://www.w3.org/2001/tag/doc/passwordsInTheClear-52-20080602">Passwords
	in the Clear</a></cite> </em>Draft TAG Finding 12 September 2008 (<a href="http://lists.w3.org/Archives/Public/www-tag/2008Sep/0057">cover
	note</a>)</li>
</ul>

<hr />
<p>&nbsp;</p>
<h3><a name="XMLVersioning-41">3.7 XMLVersioning-41</a> (<a href="http://www.w3.org/2001/tag/group/track/issues/41">ISSUE-41</a>)</h3>
<p>Our goals for this session are: to further expand the body of text in the Compatibility Strategies draft finding
supported by the TAG; to consider whether the finding needs to include any particular formalism either by inclusion or
by reference.</p>

<h4>Preparation</h4>
<ul>
	<li>section <a
		href="http://www.w3.org/2001/tag/doc/versioning-compatibility-strategies-20080912#forwardsCompatible">5 Forwards
	Compatible</a> in <cite><a href="http://www.w3.org/2001/tag/doc/versioning-compatibility-strategies-20080912">Extending
	and Versioning Languages: Compatibility Strategies</a></cite> Editorial Draft 12 September 2008</li>
	<li><a href="http://lists.w3.org/Archives/Public/www-tag/2008May/0155.html">Alternative language versioning
	formalism</a> 27 May 2008 17:05:10 -0400</li>
</ul>


<hr />
<address>Stuart Williams for the TAG, <br />
$Revision: 1.22 $ of $Date: 2008/10/15 13:54:01 $</address>
<hr />
<p><a href="http://validator.w3.org/check?uri=referer"> <img src="http://www.w3.org/Icons/valid-xhtml10"
	alt="Valid XHTML 1.0 Transitional" height="31" width="88" /></a></p>
</body>

</html>