- From: Julian Aubourg <notifications@github.com>
- Date: Sun, 13 Mar 2016 21:05:39 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Monday, 14 March 2016 04:06:08 UTC
Also, why not "new element" rather than "novel element"? Is there something ambiguous about "new"? Anyway, we would have: A "custom element" is either a "new element" or a "tailored element". Good enough? On 14 March 2016 at 05:02, Julian Aubourg <j@ubourg.net> wrote: > How about "tailored element"? Makes it sound like an element that has been > tinkered with. > > On 14 March 2016 at 04:48, Domenic Denicola <notifications@github.com> > wrote: > >> I think we should avoid the whole author vs. developer debate by going >> with "novel element." >> >> If you're really worried about some kind of patent thing then maybe look >> through the thesaurus for "novel" and choose an adjective you'd prefer to >> propose as an alternative. >> >> — >> Reply to this email directly or view it on GitHub >> <https://github.com/w3c/webcomponents/issues/434#issuecomment-196127194>. >> > > --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/434#issuecomment-196130112
Received on Monday, 14 March 2016 04:06:08 UTC