[
Lists Home |
Date Index |
Thread Index
]
"My own proposal was for special XSLT error templates that could
"match" or trigger on error conditions, assuming a very simple XML
vocab for XSLT error communication in the
first place."
Oooohhhh.... I totally love that idea!!! Basically like built-in
templates that exist in the 1.0 definition... basic output and easily
overidable if desired as such.
Dimitre, can you think of a way to do this with FXSL, especially with
XSLT 2.0 and everything being a sequence of nodes it seems that a
certain condition could easily insert, for example, <error id="123"/>
into the output and further apply-templates to all error elements
before finishing each process contained within a template?
On Thu, 30 Dec 2004 18:25:33 -0700, Uche Ogbuji
<uche.ogbuji@fourthought.com> wrote:
> On Fri, 2004-12-31 at 00:13 +0000, Michael Kay wrote:
> > > Going off on a tangent here ... that is a subject which intrigues me.
> > > It is clear that much of XSLT2 really does offer simpler ways of doing
> > > things that are possible but tedious in XSLT 1. It's hard to know,
> > > before XSLT 2 gets into people's hands and the wheat and chaff get
> > > sorted out by experience, which parts reflect the the voice of
> > > experience, and which parts are "second system syndrome". Anyone want
> > > to offer opinions?
> >
> > You're asking a very heavily loaded question. Have you stopped beating your
> > wife?
>
> Whoa. Yikes.
>
> Actually I'd thought the resulting discussion pretty even-handed and
> useful.
>
>
> > There are other important features that aren't included because the WG
> > worked hard to avoid feature creep - examples are dynamic XPath evaluation
>
> Really miss this. Thank goodness for EXSLT dyn:evaluate()
>
> > higher-order functions
>
> Really miss this, but Dimitre has some astonishingly clever work in the
> area even given XSLT 1.0.
>
> > and try/catch.
>
> Ooh. Intriguing. We had a discussion about such extensions in the
> 4Suite mailing list a few years back. My own proposal was for special
> XSLT error templates that could "match" or trigger on error conditions,
> assuming a very simple XML vocab for XSLT error communication in the
> first place. Then there could be some sort of error mode so that
> explicitly scoped try/catch constructs were not necessary. Rather,
> simple heuristics would provide for matching current error and error
> mode to error template.
>
> Do you know of or have any references to any particular exception
> handling proposals from the XSLT 2.0 development process?
>
> Thanks.
>
>
> --
> Uche Ogbuji Fourthought, Inc.
> http://uche.ogbuji.net http://4Suite.org http://fourthought.com
> Use CSS to display XML - http://www.ibm.com/developerworks/edu/x-dw-x-xmlcss-i.html
> Full XML Indexes with Gnosis - http://www.xml.com/pub/a/2004/12/08/py-xml.html
> Be humble, not imperial (in design) - http://www.adtmag.com/article.asp?id=10286
> UBL 1.0 - http://www-106.ibm.com/developerworks/xml/library/x-think28.html
> Use Universal Feed Parser to tame RSS - http://www.ibm.com/developerworks/xml/library/x-tipufp.html
> Default and error handling in XSLT lookup tables - http://www.ibm.com/developerworks/xml/library/x-tiplook.html
> A survey of XML standards - http://www-106.ibm.com/developerworks/xml/library/x-stand4/
> The State of Python-XML in 2004 - http://www.xml.com/pub/a/2004/10/13/py-xml.html
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
>
>
--
:: M. David Peterson ::
XML & XML Transformations, C#, .NET, and Functional Languages Specialist
|
