Re: HTMLElement.register--giving components tag names

Referencing a note dated 2003 may not sound strong any more - web-based
applications (or to be more specific - their UI) have evolved significantly
since the date. Today limiting developers to an extremely low level markup
API, such as SVG or HTML only leads to huge, hardly manageable JavaScript UI
code in any more or less complex solution.

The need in custom markup that facilitates higher level UI technologies
abstractions is here. (Meaning - has been here. Since, say 2003)

As for searching engines "not capable of indexing applications" - this is in
no way a concern, I bet neither GMail, nor AdSense apps etc. have been
successfully indexed so far. Exposing data or electronic documents is
something else.

Sergey/

On 31 August 2011 09:00, Anne van Kesteren <annevk@opera.com> wrote:

> On Wed, 31 Aug 2011 07:33:16 +0200, Dominic Cooney <dominicc@chromium.org>
> wrote:
>
>> Thanks for reading this far! These proposals aren't formal or
>> detailed. I would love to get feedback as I try to nail down some
>> specifics.
>>
>
> The basic problem with this is that you get proprietary markup going over
> the wire:
>
> http://ln.hixie.ch/?start=**1064828134&count=1<http://ln.hixie.ch/?start=1064828134&count=1>
>
> Having said that, I am not sure what the "correct" alternative would be.
> XBL (as Ian envisioned it anyway) was meant to enhance non-proprietary
> markup, not to let authors create novel constructs. Now you cannot stop
> authors from exploring novel constructs of course, but whether we should
> explicitly endorse it is another matter.
>
>
> --
> Anne van Kesteren
> http://annevankesteren.nl/
>
>