Alternatives to the W3C (was Re: Alternatives to the W3C)

Didier PH Martin martind at
Sun Jan 23 15:50:02 GMT 2000

Hi Simon,

Simon said:
That plus support for simple XLinks is about the minimum needed for
building Web sites.  IE 5.0 will let you read XML+CSS; it won't let you
surf it.

(I could try its bizarrely broken html: pseudo-namespace, but let's not
even go there.)

Didier replies:
If we have the "link" property and the "@style" construct + EcmaScript we
have about everything needed to implement two kind of links:
a) simple links = object with "link" property
b) extended links = objects with attached behavior.

For extended links I already experimented with an EcmaScript behavior that
displays a menu in which all the links are displayed as menu options. Thus,
if you include an xlink:extended link in the document, this element is
associated to a behavior with a selector that match to either the
"xlink:extended" element or an other selector that matches to the attribute
"xlink:type="extended". the behavior uses the DOM to construct the context
menu from all the locators included in the extended link.

So, what is then required for an Xlink support is:
a) the link property
b) a behavior for the xlink:extended construct
c) and off course the behavior and @script constructs added to CSS.


If fact the behavior construct allows to create modular browser by adding
new functionalities in a standard way if the scripts are written in
EcmaScript and that they use strictly compliant DOMs.

Didier PH Martin
Email: martind at
Conferences: Web New York (
Book to come soon: XML Pro published by Wrox Press

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: or CD-ROM/ISBN 981-02-3594-1
Unsubscribe by posting to majordom at the message
unsubscribe xml-dev  (or)
unsubscribe xml-dev your-subscribed-email at your-subscribed-address

Please note: New list subscriptions now closed in preparation for transfer to OASIS.

More information about the Xml-dev mailing list