Saxon XSLT and XQuery Processor

Jirka Kosek wrote:

> it is possible to create extension elements which are
> recognized at the top level of stylesheet?

  As per XSLT 2.0, these are not extension instructions, but
user-defined data elements.  See §2.7, §3.6.2, §3.3 and §18.2.

  Regards,

--drkm























	
 p5.vert.ukl.yahoo.com uncompressed/chunked Fri Aug 25 11:13:41 GMT 2006 
	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com

No: this is one reason the terminology in XSLT 2.0 has changed from
"extension elements" to "extension instructions". Top level elements in =
your
own namespace are now called "user data elements" or similar (and they =
serve
very little purpose, other than for documentation or as input to a
preprocessor).

Michael Kay
http://www.saxonica.com/=20

> -----Original Message-----
> From: saxon-help-bounces@...
> [mailto:saxon-help-bounces@...] On Behalf=20
> Of Jirka Kosek
> Sent: 25 August 2006 12:32
> To: Mailing list for SAXON XSLT queries
> Subject: [saxon] Top level extensions elements
>=20
> Hi,
>=20
> it is possible to create extension elements which are=20
> recognized at the top level of stylesheet? For example=20
> <t:init> element in the following stylesheet is not recognized:
>=20
> <?xml version=3D"1.0" encoding=3D"UTF-8" ?>
> <xsl:stylesheet xmlns:xsl=3D"http://www.w3.org/1999/XSL/Transform"
>       version=3D"2.0"
>       xmlns:t=3D"http://kosek.cz/cz.kosek.saxon.gettext.Gettext"
>       extension-element-prefixes=3D"t">
>=20
> <t:init locale=3D"cs" domain=3D"Messages"/>
>=20
> <xsl:template match=3D"/">
>    Test: <xsl:value-of select=3D"t:_('Hello!')"/> </xsl:template>
>=20
> </xsl:stylesheet>
>=20
> It is recognized only inside templates. Implementation of=20
> <t:init/> is derived from=20
> net.sf.saxon.style.ExtensionInstruction. Will help deriving=20
> it from net.sf.saxon.style.StyleElement?
>=20
> Thanks,
>=20
> 			Jirka
>=20
>=20
> --
> ------------------------------------------------------------------
>    Jirka Kosek     e-mail: jirka@...     http://www.kosek.cz
> ------------------------------------------------------------------
>    Profesion=E1ln=ED =B9kolen=ED a poradenstv=ED v oblasti =
technologi=ED XML.
>       Pod=EDvejte se na n=E1=B9 nov=EC spu=B9t=ECn=FD web =
http://DocBook.cz
>         Podrobn=FD p=F8ehled =B9kolen=ED http://xmlguru.cz/skoleni/
> ------------------------------------------------------------------
>                     Nejbli=BE=B9=ED term=EDny =B9kolen=ED:
>      ** XSLT 23.-26.10.2006 ** XML sch=E9mata 13.-15.11.2006 **
>       ** DocBook 11.-13.12.2006 ** XSL-FO 11.-12.12.2006 **
> ------------------------------------------------------------------
>    http://xmlguru.cz    Blog mostly about XML for English readers
> ------------------------------------------------------------------
>=20
>=20

>  Top level elements in your
> own namespace are now called "user data elements" or similar (and they serve
> very little purpose, other than for documentation or as input to a
> preprocessor).

Oh so does that mean uses such as msxsl:script would be deprecated (or
banned) in 2.0? I hadn't noticed that.

David

> >  Top level elements in your
> > own namespace are now called "user data elements" or 
> similar (and they 
> > serve very little purpose, other than for documentation or 
> as input to 
> > a preprocessor).
> 
> Oh so does that mean uses such as msxsl:script would be deprecated (or
> banned) in 2.0? I hadn't noticed that.

Sorry, my comment referred to user-defined top-level elements. There's still
a role for vendor-defined top-level elements (and the two things aren't
differentiated in the XSLT spec).

Michael Kay
http://www.saxonica.com/

David Carlisle wrote:

> >  Top level elements in your own namespace are now called
> > "user data elements" or similar (and they serve very
> > little purpose, other than for documentation or as input
> > to a preprocessor).

> Oh so does that mean uses such as msxsl:script would be
> deprecated (or banned) in 2.0? I hadn't noticed that.

  What those elements can do is defined in §3.3.  I don't
know what msxsl:script does, but if it defines an extension
function, IMHO it is still ok.

  (maybe we'd can switch to XSL List?)

  Regards,

--drkm





















	
 p5.vert.ukl.yahoo.com uncompressed/chunked Fri Aug 25 11:13:42 GMT 2006 
	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com