[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: XML=WAP? And DOA?
---- Original Message ----- From: "Nicolas LEHUEN" <nicolas.lehuen@u...> > We debated about the opportunity to patent the technology in my company. We > gave up the idea, because we felt that it would be way too costly for our > little structure (yep !), and that there was a potential overlap with > Cocoon's XSP. Interesting - just a couple of hours ago I've seen some home-grown XSP implementation, because people who've implemented it, have not spent too much time learning Cocoon ( and also they implemented it long time ago when Cocoon had less visibility than it has now ). XSP is pretty common pattern. In my oppinion XPathScript (AxKit) is also in that problem domain. By the way, XSP, PHP, JSP and alikes look in some sense orthogonal to XSLT, because XSP, PHP, JSP and alikes usually consider multiple sources ( and multiple *states* ) to be not an exception, but a rule. This is not actually the case for XSLT ( which has no idea sbout 'states' because printed document has *no* states ). XSLT-based frameworks are struggling when it comes to web applications. Perhaps what Mr. Leventhal said long time ago is true. ( For web applications, what we really need is a good DOM, that we can update / query / modify e t.c ) > I think I'm going to reschedule a meeting on the subject, to decide whether > it would be possible for us to at least donate the specs of the language to > the open-source community, so that anybody could scavenge good ideas out of > it. Maybe the best thing would be to work with the XSP people at Cocoon. The > biggest problem is to find time to write down those specs in English, as > everything was done in French here :), and/or to collaborate with the XSP > people... I'd gladly participate in any open group that would try building a practical language-neutral templatish language. There are some things in XSLScript that I like, but there are some things that I don't like. Yet another Text::Template is what we need ;-) However, it should be language and platform neutral. And I belive that { makes better separator than <%. ;-) OK, OK, really nice thing should allow both, because some people need to edit it in a GUI HTML editor, but some people are editing templates in vi / notepad And I think that there is no possible markup that would be good for *both* cases. Rgds.Paul.
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|