W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: xdash name prefixes (was Re: Component Model Update)

From: Roland Steiner <rolandsteiner@google.com>
Date: Wed, 31 Aug 2011 13:15:50 -0700
Message-ID: <CACFPSphYyDd7dEVeEAs9hKmfcdNNJH0quhf+4qH5PLEq62mf5g@mail.gmail.com>
To: Dominic Cooney <dominicc@chromium.org>
Cc: Adam Barth <w3c@adambarth.com>, Dimitri Glazkov <dglazkov@chromium.org>, public-webapps <public-webapps@w3.org>, Maciej Stachowiak <mjs@apple.com>, Jonas Sicking <jonas@sicking.cc>, Boris Zbarsky <bzbarsky@mit.edu>
On Wed, Aug 31, 2011 at 12:57 PM, Dominic Cooney <dominicc@chromium.org>wrote:

> I think for convenience registration probably should be carried around
> with the component, because:
> 1. It is convenient for the author using the component.
> 2. If the component library reuses its own abstractions, it probably
> expects them to have a specific element name. Putting registration in
> the hands of the author using the component jeopardizes that.

That is actually a good point.

Something declarative like module imports and exports, with scoped
> renaming, for registered tag names would be nice. This avoids these
> two problems, and is pretty convenient (particularly if import * gets
> you all of the exports by default.)

Wouldn't that be effectively namespaces by another name/mechanism? Also,
there's probably a limit to how far renaming can avoid clashes, e.g., if a
sub-components can also be utilized by a page's author.

In any case, until modules become a reality I think teaching component
authors to use "pseudo-namespaces" (e.g., "x-rogersoft-button" vs.
"x-delilahsoft-button") for stuff that might clash is not unreasonable.


- Roland
Received on Wednesday, 31 August 2011 20:45:13 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:34 UTC