RE: Extension Specification Authoring & Publication

I'll note that for a lot of other extension specs: MSE, EME, sourceset, <picture>, at least; they appear to be stand-alone documents.

I personally think that cloning HTML5.1 just to add one new behavior or tag is wayyy too much overhead. Yes, it'll be easy to merge later, but it's absolutely terrible for calling attention to the specific nature of the extension proposal.

I find it ridiculously easy to use respec and whip together a document that looks publish-ready without too much pain. At that point, I like to host it at mercurial because the access control is easy (vs. dev.w3.org, which requires public keys). I also like that mercurial is on a W3C server so it looks more official-looking. But I suppose putting it up on github works as well.

My 2c-
-Travis

From: Silvia Pfeiffer [mailto:silviapfeiffer1@gmail.com]
Sent: Wednesday, December 12, 2012 1:05 PM
To: Cameron Jones
Cc: public-html-admin@w3.org
Subject: Re: Extension Specification Authoring & Publication

On Wed, Dec 12, 2012 at 11:26 PM, Cameron Jones <cmhjones@gmail.com<mailto:cmhjones@gmail.com>> wrote:

On Wed, Dec 12, 2012 at 4:21 AM, Silvia Pfeiffer <silviapfeiffer1@gmail.com<mailto:silviapfeiffer1@gmail.com>> wrote:
(moving to the admin list)

Hi Cameron,

Since we are doing most of our editing work on GitHub, as one of the editors I'd like to see it in GitHub in your private repository, preferably in a way that we can merge it into the existing spec easily.

HTH.

Silvia.


Ok, how do i publish it for review? Is a link to the repository from the existing proposal sufficient or should i generate and publish a build?

Thanks,
Cameron Jones


You can take inspiration from other extension specs: http://www.w3.org/html/wg/wiki/ExtensionSpecifications

HTH.

Cheers,
Silvia.