From: Reza B'Far (rbfar@ebuilt.com)
Date: Sat Sep 16 2000 - 10:35:22 PDT
While I agree, we have been (at eBuilt) looking at "families" of devices.
It seems like you can stream line the XSL creation process by assigning one
XSL to a family of devices.
That way, you actually can create a finite set of XSL's and support multiple
devices by picking which XSL to use at run time. You can also
"pre-generate" all the content whose only dynamic content is encapsulated in
the XSL (the content which doesn't have CGI, servlet, ASP stuf, etc.)....
We've actually been working on a white paper on this and would love to send
it to you for comments prior to publication for comments from those who may
be interested.
R
----- Original Message -----
From: Edd Dumbill <edd@usefulinc.com>
To: <rbfar@ebuilt.com>
Cc: <fork@xent.com>; B.K. DeLong <bkdelong@pobox.com>
Sent: Saturday, September 16, 2000 4:47 AM
Subject: Re: [Wash Post] The WAP backlash continues...
> On Fri, Sep 15, 2000 at 10:31:58AM -0700, rbfar@ebuilt.com wrote:
> > But don't you think that content will get pushed into XML and HTML will
be
> > generated from XML?
> >
> > That way, all you need to do is create content in XML and build XSL's on
the
> > top of it to spit out HTML, WML, or whatever.... (I know this is really
> > obvious and I'm probably missing something...)
>
> <decloak/>
>
> Seems to me that both the nature of the content and the interaction
> model is different for wireless devices than PC browsers--so it's not a
> case of creating the data once in XML and then using XSLT to get WML for
> free. The WML application, to be effective (ha!), needs to be designed
> in a way sensitive to the device. Often a part of this could be
> abbreviated content, etc. For all XSLT's convenience it can't do that
> work for you.
>
> -- Edd
This archive was generated by hypermail 2b29 : Sat Sep 16 2000 - 10:34:23 PDT