Re: [apps-discuss] Last Call for HTML5 in the W3C

Mykyta Yevstifeyev <> Wed, 22 June 2011 04:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B561E21F845F for <>; Tue, 21 Jun 2011 21:11:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.484
X-Spam-Status: No, score=-3.484 tagged_above=-999 required=5 tests=[AWL=0.115, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id P1dLFeRxgiEE for <>; Tue, 21 Jun 2011 21:11:47 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 6F43321F845B for <>; Tue, 21 Jun 2011 21:11:47 -0700 (PDT)
Received: by fxm15 with SMTP id 15so387982fxm.31 for <>; Tue, 21 Jun 2011 21:11:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=iFZq0RQCRu4mh9QjioAHEWsXYidfuu3KDRgNSAnmHsQ=; b=S3CS3cEDTXHySiPz8ZAGdqL89CXPEKnTN09Yt32HmMekHgE2meVHlyRRPA9PoFMBHg 4Pmt40N+x6YcvL9/qcnjrhx0+P/I+NPMQBrvrTvN+4t45nOj0JIG+In9iDT4lrox8slW 0SYaJY8x7b40Amr2xq6oqGTVlKrZJjkgDSJ4I=
DomainKey-Signature: a=rsa-sha1; c=nofws;; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=bafmBZlLp/Qim1Ry2zD1gAqRx6bXt6Pvi5EG68+mZKp82l2s67XXziiX2zLL7Yk2cT 05e4fdnUJbKRZ8g6KoyTegHyf0INJM9odM+hlgQBVAc0lwmq53G0ntfumRI48zHMZ5Tk /A5+IUBzMqM2f1NJWwUyRo/6JMpzK3lkDVdgs=
Received: by with SMTP id g2mr213419fal.133.1308715906588; Tue, 21 Jun 2011 21:11:46 -0700 (PDT)
Received: from [] ([]) by with ESMTPS id g7sm67711fac.39.2011. (version=SSLv3 cipher=OTHER); Tue, 21 Jun 2011 21:11:45 -0700 (PDT)
Message-ID: <>
Date: Wed, 22 Jun 2011 07:12:31 +0300
From: Mykyta Yevstifeyev <>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv: Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Frank Ellermann <>
References: <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [apps-discuss] Last Call for HTML5 in the W3C
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 22 Jun 2011 04:11:48 -0000

19.06.2011 23:16, Frank Ellermann wrote:
> On 18 June 2011 06:45, Mykyta Yevstifeyev wrote:
> [ . . . ]
>> This specification defines the URLabout:srcdoc  as a
>> reserved, though unresolvable, about: URI, that is
>> used as the document's address of iframe srcdoc
>> documents. [ABOUT]
> If that is a good idea (I didn't know it and have no time
> to check it today) independent of HTML5 it should be
> added to the about: draft.
We discussed the idea to add these two about URIs in the draft and 
decided not to do this and leave reservation to the HTML5 itself.
>> Moreover, the [ABOUT] references the well-known
>> draft-holsten-about-uri-scheme which we have had
>> a lot of discussions on.
> Well, it should.  The about: draft should be an RFC long
> before HTML5 arrives at its "last last call" in 2012.  The
> WhatWG HTML is no problem, it's a moving target and
> can be updated whenever the WhatWG folks feel like it.
We haven't currently reached a consensus whether to create or not the 
possibility to reserve the about URI tokens, as far as you know.  It's 
better for HTML5 to mention the above URIs as "used for a specific 
purpose" and later, if about URI draft progresses with the above 
possibility, they may be included by reference.
>> Probably the same is with 'javascript' URIs (Section 6.1.5).
>> It references [JSURL], the draft-hoehrmann-javascript-
>> scheme, which is now expired.  It includes-by-reference
>> the source code retrieval operation for these URIs
>> (
>> scheme-03#section-3.1).
> I recall an old version of this brave attempt to document
> javascript: URLs, and various essential points were
> unclear in the 2006 draft.  But now there's a newer draft
> (expired in March 2011), maybe it's ready before HTML5.
The draft is currently expired.  If Bjoern is ready to reopen work on 
it, then this shouldn't be a problem.
>> I propose not to include it by reference but rather
>> describe in the specification itself.  The algorithm
>> contains only 4 steps so it shouldn't be a problem.
> If what you want is simple it should better be done in the
> javascript:  URL draft.
That draft isn't going to progress, as I see; see below.
>   And as long as the new draft says
> "you really do not want to do this" at least once per page
> and subsection I might even like it now. ;-)
Mykyta Yevstifeyev
>> The [MAILTO] references the document which was
>> obsoleted by RFC 6068.
> [etc.]
> Yes, but as Mark said that's not the business of the IETF
> Apps list.  Hopefully the W3C HTML5 Last Call FAQ
> meanwhile manages to identify which of the numerous
> HTML drafts is the "first last call" version, e.g., giving an
> immutable URL of this draft would be a good thing in the
> FAQ.  And it should specify where interested users can
> post comments (without preconditions above a working
> mail address).