update extensibility section. https://www.w3.org/Bugs/Public/show_bug.cgi?id=15307
authorAnne van Kesteren <annevk@opera.com>
Thu, 22 Dec 2011 10:54:16 +0100
changeset 29ac2bf114fd20
parent 28 20b49c8da6d3
child 30 9090a37c787f
update extensibility section. https://www.w3.org/Bugs/Public/show_bug.cgi?id=15307
Overview.html
Overview.src.html
     1.1 --- a/Overview.html	Thu Dec 22 10:19:47 2011 +0100
     1.2 +++ b/Overview.html	Thu Dec 22 10:54:16 2011 +0100
     1.3 @@ -310,14 +310,13 @@
     1.4    <h3 id="extensibility"><span class="secno">2.2 </span>Extensibility</h3>
     1.5  
     1.6    <p>User agents, Working Groups, and other interested parties are
     1.7 -  <em>strongly encouraged</em> to discuss extensions on a relevant public
     1.8 +  <em>strongly encouraged</em> to discuss new features on a relevant public
     1.9    forum, preferably
    1.10    <a href="mailto:public-webapps@w3.org">public-webapps@w3.org</a>. If this
    1.11 -  is for some reason not possible prefix the extension in some way and start
    1.12 -  the prefix with an uppercase letter. E.g. if company Foo wants to add a
    1.13 -  private method <code>bar()</code> it could be named <code>FooBar()</code>
    1.14 -  to prevent clashes with a potential future standardized
    1.15 -  <code>bar()</code>.</p>
    1.16 +  is for some reason not possible prefix the extension in some way. E.g. if
    1.17 +  company Foo wants to add a proprietary method <code>bar()</code> it could
    1.18 +  be named <code>fooBar()</code> to prevent clashes with a potential
    1.19 +  non-proprietary method <code>bar()</code>.</p>
    1.20  
    1.21  
    1.22  
     2.1 --- a/Overview.src.html	Thu Dec 22 10:19:47 2011 +0100
     2.2 +++ b/Overview.src.html	Thu Dec 22 10:54:16 2011 +0100
     2.3 @@ -318,14 +318,13 @@
     2.4    <h3 id="extensibility">Extensibility</h3>
     2.5  
     2.6    <p>User agents, Working Groups, and other interested parties are
     2.7 -  <em>strongly encouraged</em> to discuss extensions on a relevant public
     2.8 +  <em>strongly encouraged</em> to discuss new features on a relevant public
     2.9    forum, preferably
    2.10    <a href="mailto:public-webapps@w3.org">public-webapps@w3.org</a>. If this
    2.11 -  is for some reason not possible prefix the extension in some way and start
    2.12 -  the prefix with an uppercase letter. E.g. if company Foo wants to add a
    2.13 -  private method <code>bar()</code> it could be named <code>FooBar()</code>
    2.14 -  to prevent clashes with a potential future standardized
    2.15 -  <code>bar()</code>.</p>
    2.16 +  is for some reason not possible prefix the extension in some way. E.g. if
    2.17 +  company Foo wants to add a proprietary method <code>bar()</code> it could
    2.18 +  be named <code>fooBar()</code> to prevent clashes with a potential
    2.19 +  non-proprietary method <code>bar()</code>.</p>
    2.20  
    2.21  
    2.22