W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: [webcomponents]: First stab at the Web Components spec

From: Elliott Sprehn <esprehn@gmail.com>
Date: Mon, 11 Mar 2013 16:48:07 -0700
Message-ID: <CAPJYB1hOTrabk6mseLOZySSnGO7To5dTSbGTzu4-04HcWfXpNw@mail.gmail.com>
To: Scott Miles <sjmiles@google.com>
Cc: Philip Walton <philip@philipwalton.com>, Dimitri Glazkov <dglazkov@google.com>, Robert Ginda <rginda@chromium.org>, Steve Orvell <sorvell@google.com>, Anne van Kesteren <annevk@annevk.nl>, public-webapps <public-webapps@w3.org>, Ian Hickson <ian@hixie.ch>
On Mon, Mar 11, 2013 at 4:39 PM, Scott Miles <sjmiles@google.com> wrote:

> My issue is that the target of this link will not in general be an atomic
> thing like a 'component' or a 'module'. It's a carrier for resources and
> links to other resources. IMO this is one of the great strengths of this
> proposal.
>
> For this reason, when it was rel="components" (plural) there was no
> problem for me.
>
> Having said all that, I'm not particularly up in arms about this issue.
> The name will bend to the object in the fullness of time. :)
>
>
>
I guess that doesn't bother me because rel="stylesheet" isn't just one
stylesheet either, you can @import lots of them down there. :)

Similarly when I think of a "component" I don't think of one custom widget,
I think of lots of logically related bundled things.

- E
Received on Monday, 11 March 2013 23:49:14 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:58 GMT