MHonArc v2.5.2 -->
wsia message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: Re: WSIA 5/9/2002: [wsia][wsia-requirements][R602]
I would note that we should keep the list of languages as short as
possible. The general case is support for XML & HTML. XHTML & WML are
included only due to their prevalence in the marketplace. SVG (& many other
interesting/useful languages) is covered by supporting XML.
Kurt Cagle
<kurt@kurtcagle.n To: wsia@lists.oasis-open.org
et> cc:
Subject: Re: WSIA 5/9/2002: [wsia][wsia-requirements][R602]
05/10/2002 01:30
PM
I'm a general lurker on this list, so I apologize if I'm out of line here.
I'd make a strong recommendation that in your formal MUST support
requirements that you include SVG in that list as well. It is, as of
January, unencumbered and Open Source, it is an XML format that's supported
by both Windows and Linux based browsers, and it provides the one piece of
infrastructure that XHTML, WML, etc. don't give you - precise graphics
creation - I'm already building a framework around it to replace some of
the
more graphical elements of HTML (tabs, button bars, buttons, gauges, etc.)
and my early experimentation with it has worked great.
On the other front, concerning plug-in technology, I'd recommend just
taking
a hint from HTML and create a standardized <object> or <embed> capability
that includes parameter passing, plug-in source code and viewport
specification sizes. Couple this with a mechanism to let these plug-ins
hook
into a native web service capability for conformity sake, and you don't
need
to worry about formal support of a given vendor's products - they would
instead write a wrapper AI to be conformant with the WSIA spec.
-- Kurt Cagle