- From: CVS User sruby <cvsmail@w3.org>
- Date: Tue, 07 Oct 2014 20:05:42 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/2014/10
In directory roscoe:/tmp/cvs-serv23164
Added Files:
url-ref.html
Log Message:
Put proposal out for public review
--- /sources/public/html5/2014/10/url-ref.html 2014/10/07 20:05:42 NONE
+++ /sources/public/html5/2014/10/url-ref.html 2014/10/07 20:05:42 1.1
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<link href="http://www.w3.org/StyleSheets/TR/base.css" rel="stylesheet">
<style>
.note2 {
background: #e9fbe9;
border-left: 3px green solid;
padding-left: 1ex;
}
dt {
font-weight: bold;
}
</style>
</head>
<body>
<p>
The current HTML5 URL is given below:
</p>
<p>
<a href="http://www.w3.org/TR/2014/PR-html5-20140916/references.html#refsURL">http://www.w3.org/TR/2014/PR-html5-20140916/references.html#refsURL</a>
</p>
<dl>
<dt>[URL]</dt>
<dd>
<p class="note2">
URLs can be used in numerous different manners, in many differing contexts. For the purpose of producing strict URLs one may wish to consider
<cite><a href="http://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a> (URL:
<a href="http://tools.ietf.org/html/rfc3986">http://tools.ietf.org/html/rfc3986</a>)</cite>, T. Berners-Lee, R. Fielding, L. Masinter. IETF; and
<cite><a href="http://tools.ietf.org/html/rfc3987">Internationalized Resource Identifiers (IRIs)</a> (URL:
<a href="http://tools.ietf.org/html/rfc3987">http://tools.ietf.org/html/rfc3987</a>)</cite>, M. Duerst, M. Suignard. IETF.
</p>
<p>
<cite><a href="http://www.w3.org/TR/url/">URL</a> (URL:
<a href="http://www.w3.org/TR/url/">http://www.w3.org/TR/url/</a>)</cite>, E. Arvidsson, M.[tm] Smith. W3C.
</p>
<p class="note2">
At the time of publication, the URL draft above is out of date. We expect that it will be updated by the time this document goes to Recommendation.
</p>
</dd>
</dl>
<p>Here is our proposed change:</p>
<dl>
<dt>[URL]</dt>
<dd>
<div class="note2">
<p>
<b>Note:</b>
URLs can be used in numerous different manners, in many differing contexts. For the
purpose of producing strict URLs one may wish to consider [RFC3986] [RFC3987]. The W3C URL
specification defines the term URL, various algorithms for dealing with URLs, and an API
for constructing, parsing, and resolving URLs. Developers of Web browsers are advised to keep abreast of the latest URL developments by tracking the progress of <a
href="http://url.spec.whatwg.org/">http://url.spec.whatwg.org/</a>. We expect that the W3C URL draft will evolve along the Recommendation track as the community converges on a definition of URL processing.
</p>
<p>
Most of the URL-related used in the HTML specification (<strong>URL</strong>, <strong>absolute
URL</strong>, <strong>relative URL</strong>, <strong>relatives schemes</strong>,
<strong>scheme component</strong>, <strong>scheme data</strong>,
<strong>username</strong>, <strong>password</strong>, <strong>host</strong>,
<strong>port</strong>, <strong>path</strong>, <strong>query</strong>,
<strong>fragment</strong>, <strong>percent encode</strong>, <strong>get the base</strong>,
and <strong>UTF-8 percent encode</strong>) can be mapped directly to the
terminology of [RFC3986] and [RFC3987]. The <code>URLUtils</code> (formerly known as
<code>URL</code>) collection of attributes (e.g. <code>href</code> and <code>protocol</code>)
and its required definitions (<strong>input</strong>, <strong>query encoding</strong>,
<strong>url</strong>, <strong>update steps</strong>, <strong>set the input</strong>) are
considered common practice nowadays. Some of the URL-related terms are still being refined (e.g. <strong>URL
parser</strong>, <strong>parse errors</strong>, <strong>URL serializer</strong>,
<strong>default encode set</strong>, and <strong>percent decode</strong>).
</p>
<p>
As a word of caution, there are notable differences in the manner in which Web browsers and other software stacks outside the HTML context handle URLs. While no changes would be accepted to URL processing that would break existing Web content, some important parts of URL processing should therefore be considered as implementation-defined (e.g. parsing
file: URLs or operating on URLs that would be syntax errors under the [RFC3986] [RFC3987]
syntax).
</p>
</div>
<p>
<cite><a href="http://www.w3.org/TR/url/">URL</a>
(URL: <a href="http://www.w3.org/TR/url/">http://www.w3.org/TR/url/</a>)</cite>, E. Arvidsson, M.[tm] Smith. W3C.
</p>
</dd>
<dt>[RFC3986]</dt>
<dd>
<p>
<cite><a href="http://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a> (URL:
<a href="http://tools.ietf.org/html/rfc3986">http://tools.ietf.org/html/rfc3986</a>)</cite>, T. Berners-Lee, R. Fielding, L. Masinter. IETF.
</p>
</dd>
<dt>[RFC3987]</dt>
<dd>
<p>
<cite><a href="http://tools.ietf.org/html/rfc3987">Internationalized Resource Identifiers (IRIs)</a> (URL:
<a href="http://tools.ietf.org/html/rfc3987">http://tools.ietf.org/html/rfc3987</a>)</cite>, M. Duerst, M. Suignard. IETF.
</p>
</dd>
</dl>
</body>
</html>
Received on Tuesday, 7 October 2014 20:05:44 UTC