- From: poot <cvsmail@w3.org>
- Date: Sat, 8 Aug 2009 17:20:38 +0900 (JST)
- To: public-html-diffs@w3.org
- Message-Id: <20090808082039.3CA612BCC2@toro.w3.mag.keio.ac.jp>
hixie: Clean up some references in preparation for actually having a references section. (whatwg r3567) http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2759&r2=1.2760&f=h http://html5.org/tools/web-apps-tracker?from=3566&to=3567 =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.2759 retrieving revision 1.2760 diff -u -d -r1.2759 -r1.2760 --- Overview.html 8 Aug 2009 07:58:46 -0000 1.2759 +++ Overview.html 8 Aug 2009 08:20:10 -0000 1.2760 @@ -1546,7 +1546,7 @@ user agent must not mutate the DOM in such situations.</span><p>The term <dfn id="text-node">text node</dfn> refers to any <code>Text</code> node, including <code>CDATASection</code> nodes; specifically, any <code>Node</code> with node type <code title="">TEXT_NODE</code> (3) - or <code title="">CDATA_SECTION_NODE</code> (4). <a href="#references">[DOM3CORE]</a><p>A content attribute is said to <dfn title="">change</dfn> value + or <code title="">CDATA_SECTION_NODE</code> (4). <a href="#references">[DOMCORE]</a><p>A content attribute is said to <dfn title="">change</dfn> value only if its new value is different than its previous value; setting an attribute to a value it already has does not change it.<h4 id="scripting-0"><span class="secno">2.1.3 </span>Scripting</h4><p>The construction "a <code>Foo</code> object", where <code>Foo</code> is actually an interface, is sometimes used instead @@ -1559,7 +1559,7 @@ <span class="impl">must</span> operate on the actual underlying data, not a snapshot of the data.<p>The terms <dfn title="">fire</dfn> and <dfn title="">dispatch</dfn> are used interchangeably in the context of events, as in the DOM Events - specifications. <a href="#references">[DOM3EVENTS]</a><h4 id="plugins"><span class="secno">2.1.4 </span>Plugins</h4><p>The term <dfn id="plugin">plugin</dfn> is used to mean any content handler + specifications. <a href="#references">[DOMEVENTS]</a><h4 id="plugins"><span class="secno">2.1.4 </span>Plugins</h4><p>The term <dfn id="plugin">plugin</dfn> is used to mean any content handler for Web content types that are either not supported by the user agent natively or that do not expose a DOM, which supports rendering the content as part of the user agent's interface.<p>Typically such content handlers are provided by third @@ -1896,12 +1896,12 @@ model — of a document and its content. The DOM is not just an API; the conformance criteria of HTML implementations are defined, in this specification, in terms of operations on the DOM. - <a href="#references">[DOM3CORE]</a></p> + <a href="#references">[DOMCORE]</a></p> <p>Implementations must support some version of DOM Core and DOM Events, because this specification is defined in terms of the DOM, and some of the features are defined as extensions to the DOM Core - interfaces. <a href="#references">[DOM3CORE]</a> <a href="#references">[DOM3EVENTS]</a></p> + interfaces. <a href="#references">[DOMCORE]</a> <a href="#references">[DOMEVENTS]</a></p> </dd> @@ -5807,7 +5807,7 @@ </div><h4 id="dom-feature-strings"><span class="secno">2.8.7 </span>DOM feature strings</h4><p>DOM3 Core defines mechanisms for checking for interface support, and for obtaining implementations of interfaces, using <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMFeatures">feature - strings</a>. <a href="#references">[DOM3CORE]</a><p>Authors are strongly discouraged from using these, as they are + strings</a>. <a href="#references">[DOMCORE]</a><p>Authors are strongly discouraged from using these, as they are notoriously unreliable and imprecise. Authors are encouraged to rely on explicit feature testing or the graceful degradation behavior intrinsic to some of the features in this specification.<div class="impl"> @@ -5863,7 +5863,7 @@ </div> </div><h2 id="dom"><span class="secno">3 </span>Semantics, structure, and APIs of HTML documents</h2><h3 id="semantics-intro"><span class="secno">3.1 </span>Introduction</h3><p><i>This section is non-normative.</i><p class="XXX">An introduction to marking up a document.<h3 id="documents"><span class="secno">3.2 </span>Documents</h3><p>Every XML and HTML document in an HTML UA is represented by a - <code>Document</code> object. <a href="#references">[DOM3CORE]</a><p><dfn id="the-document-s-address">The document's address</dfn> is an <a href="#absolute-url">absolute URL</a> + <code>Document</code> object. <a href="#references">[DOMCORE]</a><p><dfn id="the-document-s-address">The document's address</dfn> is an <a href="#absolute-url">absolute URL</a> that is set when the <code>Document</code> is created. <dfn id="the-document-s-current-address">The document's current address</dfn> is an <a href="#absolute-url">absolute URL</a> that can change during the lifetime of the <code>Document</code>, @@ -6084,7 +6084,7 @@ it would include if <a href="#fetch" title="fetch">fetching</a> the resource indicated by <a href="#the-document-s-address">the document's address</a> over HTTP, as per RFC 2109 section 4.3.4 or later specifications, excluding HTTP-only - cookies. <a href="#references">[RFC2109]</a> <a href="#references">[RFC2965]</a></p> + cookies. <a href="#references">[RFC2109]</a> <a href="#references">[COOKIES]</a></p> <p>On setting, if the document is not associated with a <a href="#browsing-context">browsing context</a> then the user agent must raise an @@ -6101,7 +6101,7 @@ response with a <code>Set-Cookie</code> header whose value was the specified value, as per RFC 2109 sections 4.3.1, 4.3.2, and 4.3.3 or later specifications, but without overwriting the values of - HTTP-only cookies. <a href="#references">[RFC2109]</a> <a href="#references">[RFC2965]</a></p> + HTTP-only cookies. <a href="#references">[RFC2109]</a> <a href="#references">[COOKIES]</a></p> <p class="note">This specification does not define what makes an HTTP-only cookie, and at the time of publication the editor is not @@ -7895,9 +7895,9 @@ </div><h3 id="apis-in-html-documents"><span class="secno">3.4 </span>APIs in HTML documents</h3><p>For <a href="#html-documents">HTML documents</a>, and for <a href="#html-elements">HTML elements</a> in <a href="#html-documents">HTML documents</a>, certain APIs defined - in DOM3 Core become case-insensitive or case-changing, as sometimes - defined in DOM3 Core, and as summarized <span class="impl">or - required</span> below. <a href="#references">[DOM3CORE]</a>.<p>This does not apply to <a href="#xml-documents">XML documents</a> or to elements + in DOM Core become case-insensitive or case-changing, as sometimes + defined in DOM Core, and as summarized <span class="impl">or + required</span> below. <a href="#references">[DOMCORE]</a>.<p>This does not apply to <a href="#xml-documents">XML documents</a> or to elements that are not in the <a href="#html-namespace-0">HTML namespace</a> despite being in <a href="#html-documents">HTML documents</a>.<dl><dt><code title="">Element.tagName</code> and <code title="">Node.nodeName</code></dt> @@ -9115,7 +9115,7 @@ the order that they were given in the HTTP entity header. (URIs in these headers are to be processed and resolved according to the rules given in HTTP; the rules of <em>this</em> specification don't - apply.) <a href="#references">[HTTP]</a> <a href="#references">[RFC2068]</a></p> + apply.) <a href="#references">[HTTP]</a> <a href="#references">[WEBLINK]</a></p> <!-- WEBLINK is ref for Link: header --> <p>The DOM attributes <dfn id="dom-link-href" title="dom-link-href"><code>href</code></dfn>, <dfn id="dom-link-rel" title="dom-link-rel"><code>rel</code></dfn>, <dfn id="dom-link-media" title="dom-link-media"><code>media</code></dfn>, <dfn id="dom-link-hreflang" title="dom-link-hreflang"><code>hreflang</code></dfn>, and <dfn id="dom-link-type" title="dom-link-type"><code>type</code></dfn>, and <dfn id="dom-link-sizes" title="dom-link-sizes"><code>sizes</code></dfn> each must <a href="#reflect">reflect</a> the respective content attributes of the same @@ -14246,7 +14246,7 @@ </div><p>Mathematical expressions often use subscripts and superscripts. Authors are encouraged to use MathML for marking up mathematics, but authors may opt to use <code><a href="#the-sub-and-sup-elements">sub</a></code> and <code><a href="#the-sub-and-sup-elements">sup</a></code> if - detailed mathematical markup is not desired. <a href="#references">[MathML]</a><div class="example"> + detailed mathematical markup is not desired. <a href="#references">[MATHML]</a><div class="example"> <pre><var>E</var>=<var>m</var><var>c</var><sup>2</sup></pre> <pre>f(<var>x</var>, <var>n</var>) = log<sub>4</sub><var>x</var><sup><var>n</var></sup></pre> </div><h4 id="the-span-element"><span class="secno">4.6.18 </span>The <dfn><code>span</code></dfn> element</h4><dl class="element"><dt>Categories</dt> @@ -35625,7 +35625,7 @@ title="">index</var>th row in the selection. If the argument is out of range (less than zero or greater than the number of selected rows minus one), then it must raise an <code>INDEX_SIZE_ERR</code> - exception. <a href="#references">[DOM3CORE]</a></p> + exception. <a href="#references">[DOMCORE]</a></p> <p>The <dfn title="dom-DataGridSelection-isSelected"><code>isSelected()</code></dfn> @@ -41288,7 +41288,7 @@ media used for the presentation of a particular <code>Document</code> object in some media. A view may be interactive. Each view is represented by an - <code>AbstractView</code> object. <a href="#references">[DOM2VIEWS]</a><p>The main <a href="#view">view</a> through which a user primarily + <code>AbstractView</code> object. <a href="#references">[DOMVIEWS]</a><p>The main <a href="#view">view</a> through which a user primarily interacts with a user agent is the <dfn id="default-view">default view</dfn>. The <code>AbstractView</code> object that represents this view <span class="impl">must also implement the <code><a href="#window">Window</a></code> interface, and</span> is referred to as the <code>Document</code>'s @@ -41301,12 +41301,12 @@ <code>DocumentView</code> interface must return the <a href="#browsing-context">browsing context</a>'s <code><a href="#windowproxy">WindowProxy</a></code> object, not the actual <code>AbstractView</code> object of the <a href="#default-view">default - view</a>. <a href="#references">[DOM3VIEWS]</a></p> + view</a>. <a href="#references">[DOMVIEWS]</a></p> </div><p class="note">The <code title="dom-document">document</code> attribute of an <code>AbstractView</code> object representing a <a href="#view">view</a> gives the view's corresponding - <code>Document</code> object. <a href="#references">[DOM2VIEWS]</a><p class="note">In general, there is a 1-to-1 mapping from the + <code>Document</code> object. <a href="#references">[DOMVIEWS]</a><p class="note">In general, there is a 1-to-1 mapping from the <code><a href="#window">Window</a></code> object to the <code>Document</code> object. In one particular case, a set of <a href="#view" title="view">views</a> can be reused for the presentation of a second <code>Document</code> in the @@ -41322,7 +41322,7 @@ the <code><a href="#windowproxy">WindowProxy</a></code> object of the <a href="#browsing-context">browsing context</a> of that <a href="#view">view</a>, not the actual <code>AbstractView</code> object of the <a href="#default-view">default - view</a>. <a href="#references">[DOM3EVENTS]</a></p> + view</a>. <a href="#references">[DOMEVENTS]</a></p> </div><p class="note">A typical Web browser has one obvious <a href="#view">view</a> per <code>Document</code>: the browser's window @@ -43626,7 +43626,7 @@ elements. For example, the <code title="dom-click"><a href="#dom-click">click()</a></code> method on the <code><a href="#htmlelement">HTMLElement</a></code> interface is defined as firing a <code title="event-click">click</code> event on the - element. <a href="#references">[DOM3EVENTS]</a></p> + element. <a href="#references">[DOMEVENTS]</a></p> <p><dfn id="fire-a-click-event" title="fire a click event">Firing a <code title="event-click">click</code> event</dfn> means that a <code title="event-click">click</code> event with no namespace, which bubbles and is cancelable, and which uses the @@ -46807,7 +46807,7 @@ <p>The <dfn id="dom-popstateevent-initpopstateevent" title="dom-PopStateEvent-initPopStateEvent"><code>initPopStateEvent()</code></dfn> and <dfn id="dom-popstateevent-initpopstateeventns" title="dom-PopStateEvent-initPopStateEventNS"><code>initPopStateEventNS()</code></dfn> methods must initialize the event in a manner analogous to the - similarly-named methods in the DOM3 Events interfaces. <a href="#references">[DOM3EVENTS]</a></p> + similarly-named methods in the DOM Events interfaces. <a href="#references">[DOMEVENTS]</a></p> <p>The <dfn id="dom-popstateevent-state" title="dom-PopStateEvent-state"><code>state</code></dfn> attribute represents the context information for the event, or null, @@ -47494,7 +47494,7 @@ <p>When faced with displaying an XML file inline, user agents must first <a href="#create-a-document-object">create a <code>Document</code> object</a>, following the requirements of the XML and Namespaces in XML recommendations, - RFC 3023, DOM3 Core, and other relevant specifications. <a href="#references">[XML]</a> <a href="#references">[XMLNS]</a> <a href="#references">[RFC3023]</a> <a href="#references">[DOM3CORE]</a></p> + RFC 3023, DOM3 Core, and other relevant specifications. <a href="#references">[XML]</a> <a href="#references">[XMLNS]</a> <a href="#references">[RFC3023]</a> <a href="#references">[DOMCORE]</a></p> <p>The actual HTTP headers and other metadata, not the headers as mutated or implied by the algorithms given in this specification, @@ -49605,7 +49605,7 @@ --><p>The <code><a href="#selection-0">Selection</a></code> interface is represents a list of <code>Range</code> objects. The first item in the list has index 0, and the last item has index <var title="">count</var>-1, where - <var title="">count</var> is the number of ranges in the list. <a href="#references">[DOM2RANGE]</a><p>All of the members of the <code><a href="#selection-0">Selection</a></code> interface are + <var title="">count</var> is the number of ranges in the list. <a href="#references">[DOMRANGE]</a><p>All of the members of the <code><a href="#selection-0">Selection</a></code> interface are defined in terms of operations on the <code>Range</code> objects represented by this object. These operations can raise exceptions, as defined for the <code>Range</code> interface; this can therefore @@ -50524,7 +50524,7 @@ <p>The <dfn id="dom-dragevent-initdragevent" title="dom-DragEvent-initDragEvent"><code>initDragEvent()</code></dfn> and <dfn id="dom-dragevent-initdrageventns" title="dom-DragEvent-initDragEventNS"><code>initDragEventNS()</code></dfn> methods must initialize the event in a manner analogous to the - similarly-named methods in the DOM3 Events interfaces. <a href="#references">[DOM3EVENTS]</a></p> + similarly-named methods in the DOM Events interfaces. <a href="#references">[DOMEVENTS]</a></p> <p class="note">The <code title="dom-DragEvent-initDragEvent"><a href="#dom-dragevent-initdragevent">initDragEvent()</a></code> and <code title="dom-DragEvent-initDragEventNS"><a href="#dom-dragevent-initdrageventns">initDragEventNS()</a></code> methods handle modifier keys differently, much like the equivalent @@ -51796,7 +51796,7 @@ <p>The <dfn id="dom-undomanagerevent-initundomanagerevent" title="dom-UndoManagerEvent-initUndoManagerEvent"><code>initUndoManagerEvent()</code></dfn> and <dfn id="initundomanagereventns"><code title="dom-UndoManagerEvent-initUndoManagerEventNS">initUndoManagerEventNS()</code></dfn> methods must initialize the event in a manner analogous to the - similarly-named methods in the DOM3 Events interfaces. <a href="#references">[DOM3EVENTS]</a></p> + similarly-named methods in the DOM Events interfaces. <a href="#references">[DOMEVENTS]</a></p> <p>The <dfn id="dom-undomanagerevent-data" title="dom-UndoManagerEvent-data"><code>data</code></dfn> attribute represents the <a href="#undo-object">undo object</a> for the event.</p> @@ -52329,7 +52329,7 @@ <p>The <dfn id="dom-messageevent-initmessageevent" title="dom-MessageEvent-initMessageEvent"><code>initMessageEvent()</code></dfn> and <dfn id="dom-messageevent-initmessageeventns" title="dom-MessageEvent-initMessageEventNS"><code>initMessageEventNS()</code></dfn> methods must initialize the event in a manner analogous to the - similarly-named methods in the DOM3 Events interfaces. <a href="#references">[DOM3EVENTS]</a></p> + similarly-named methods in the DOM Events interfaces. <a href="#references">[DOMEVENTS]</a></p> <p>The <dfn id="dom-messageevent-data" title="dom-MessageEvent-data"><code>data</code></dfn> attribute represents the message being sent.</p> @@ -56077,7 +56077,7 @@ <p id="mutation-during-parsing">DOM mutation events must not fire for changes caused by the UA parsing the document. (Conceptually, the parser is not mutating the DOM, it is constructing it.) This - includes the parsing of any content inserted using <code title="dom-document-write"><a href="#dom-document-write">document.write()</a></code> and <code title="dom-document-writeln"><a href="#dom-document-writeln">document.writeln()</a></code> calls. <a href="#references">[DOM3EVENTS]</a></p> + includes the parsing of any content inserted using <code title="dom-document-write"><a href="#dom-document-write">document.write()</a></code> and <code title="dom-document-writeln"><a href="#dom-document-writeln">document.writeln()</a></code> calls. <a href="#references">[DOMEVENTS]</a></p> <p class="note">Not all of the tag names mentioned below are conformant tag names in this specification; many are included to
Received on Saturday, 8 August 2009 08:21:15 UTC