text: Vielen Dank für Ihre Nachricht!
  Ich bin bis einschließlich 15.03.2002 nicht im Haus. In dringenden Fällen können Sie mich erreichen unter 0177/24 069 24.
  Mit freundlichen Grüßen,
  Heide Ebert
  -------------------------
  Heide Ebert
  Stellv. Leiterin DVEP/RWS EP
  Hüthig Fachverlage GmbH & Co. KG
  Im Weiher 10
  69121 Heidelberg
  Tel.: 06221/489-641
  Mobile: 0177/24 069 24
  --------------------------------
  Dear all,
  I have been trying to solve this, and I have no idea.
  I the following situation
  <doc-root
  <element cd="mynamespace:id-there"/>
  </doc-root>
  I would like to write a template for 'element' that picks out the namespace
  of the value at its its 'cd' attribute. I have tried something like
  <xsl:template
  <xsl:value-of
  </xsl:template>
  or (although this looks very krufty
  <xsl:template
  <xsl:variable
  <xsl:value-of
  </xsl:template>
  The problem here seems to be that namespace declarations xmlns:mynamespace
  is not counted as an attribute (is this standard?)
  I have tried using the namespace-uri function, but i am not sure where I
  could get a nodeset where the first element has the namespace mynamespace.
  I am a bit confused, so any clarification would help.
  Michael
  >Dear all,
  >
  >I have been trying to solve this, and I have no idea.=20
  >
  >I the following situation=20
  >
  ><doc-root id=3D"???" xmlns:mynamespace=3D"">
  > <element cd=3D=3D"";.=3D"element">
  <xsl:variable name=3D"ns" select=3D"substring-before(@cd,':')"/>
  <xsl:value-of select=3D"namespace::*[local-name()=3D.
  Hope that helps,
  Trevor Nash
  Melvaig Software Engineering Limited
  voice: +44 (0) 1445 771 271=20
  You appear to be trying to output a namespace declaration by writing
  <xsl:attributejavascript:code</xsl:attribute>
  This doesn't do what you expect. The value of the namespace attribute is
  a namespace URI, not a namespace prefix. So Saxon has to output an
  attribute named XX:js, where the prefix XX is mapped to the namespace
  URI "xmlns". It chooses an arbitrary namespace prefix, in this case
  "ns0".
  You can't output namespace declarations using xsl:attribute, because
  attribute nodes and namespace nodes are quite different things in the
  data model.
  So how do you do it?
  In XSLT 2.0 (and with Saxon 7.1) you can write
  <xsl:namespacejavascript:code</xsl:attribute>
  In XSLT 1.0 the simplest way is to output a dummy attribute that's in
  the required namespace, for example:
  <xsl:attribute
  It's not actually guaranteed by the spec that the result document will
  use the prefix "js", but Saxon will normally do this unless there is a
  conflict with another attribute.
  This only works if the "dummy" attribute isn't going to cause problems.
  Fortunately XSLT has a rule that unrecognized attributes in a
  non-default namespace are simply ignored.
  The answer to your question at the end is that the output you have
  written is a valid XML document, but it is not a valid stylesheet. When
  Saxon wrote it out, it didn't know you were trying to write a
  stylesheet, but when it read it back in, it did!
  Just one more comment: you seem to be trying to write a stylesheet that
  calls JavaScript extension functions. Saxon can generate such a
  stylesheet, but it can't run it: Saxon has no interface to JavaScript.
  Michael Kay
  Software AG
  home: Michael.H.Kay@...
  work: Michael.Kay@...
  > -----Original Message-----
  > From: saxon-help-admin@...
  > [mailto:saxon-help-admin@...] On Behalf Of
  > Bloom, James D
  > Sent: 15 July 2002 12:49
  > To: 'saxon-help@...'
  > Subject: [saxon] (no subject)
  >
  >
  >
  >
  >
  > -------------------------------------------------------
  > This sf.net email is sponsored by:ThinkGeek
  > Welcome to geek heaven.
  >
  > _______________________________________________
  > saxon-help mailing list
  > saxon-help@...
  >> axon-help
  >
  Hello.
  I don't know much about this quiestion, but I think saxon (as Xalan and
  brothers) are server side engines... And I prefer client-side solutions.
  Is possible to integrate Saxon into Mozilla as a Plug-in ?? Mozilla
  has his own XSLT engine, but it's horrible.
  SG93IGNhbiBJIHVuc3Vic2NyaWJlLg0KIA0Ka25ndXllbkBlLWNlbnRpdmVzLmNvbQ0K
  See the last section of the page at =
  =20
  Michael Kay
  Software AG
  home: Michael.H.Kay@...
  work: Michael.Kay@...=20
  -----Original Message-----
  From: saxon-help-admin@... =
  [mailto:saxon-help-admin@...] On Behalf Of Khoivu =
  Nguyen
  Sent: 18 July 2002 20:01
  To: saxon-help@...
  Subject: [saxon] (no subject)
  How can I unsubscribe.
  =20
  knguyen@...
  Is it possible to have saxon (6.5) read the source document from stdin?
  That is, use saxon like this:
  cat source-doc.xml | java com.icl.saxon.StyleSheet - style-doc
  I think it would be really easy if the source document was the last argument,
  or at least be able to pass arguments like "-xsl style doc" and
  "-source source-doc". Thanks for any help.
  --
  Jiann-Ming Su jsu2@... 404-712-2603
  Development Team Systems Administrator
  General Libraries Systems Division
  Jiann-Ming Su <jsu2@...> writes:
  > Is it possible to have saxon (6.5) read the source document from stdin?
  > That is, use saxon like this:
  >
  > cat source-doc.xml | java com.icl.saxon.StyleSheet - style-doc
  Using Pine and mentioning cat, you seem to be on a Unix variant. If
  you use Bash, you can use
  cat source-doc.xml | java com.icl.saxon.StyleSheet /dev/stdin style-doc
  Note that this works even with applications that expect absolute URLs
  not filenames,
  cat source-doc.xml | java org.apache.xalan.xslt.Process -in
  Ari
  Sorry about the posting from gsk.com; the company mailserver rewrites
  outgoing email addresses, and I forget about it. Thanks to the list
  manager for posting the question anyway.
  >> In version 6.5.2, Saxon doesn't allow variables in template
  >> match patterns.
  >
  >It's well hidden, but the restriction is in the spec: section 5.3,
  >
  >"It is an error for the value of the match attribute to contain a
  >VariableReference."
  >
  >The restriction is lifted in XSLT 2.0 and therefore in Saxon 7.x
  >
  >Some XSLT 1.0 processors have been a bit relaxed about some of these
  >finer details of the 1.0 spec (indeed, Saxon's handling of result tree
  >fragments is still a little over-liberal).
  I see it. Thanks for the pointer.
  I suppose it is too late to be complaining about the specification,
  it being three years old and all, but the spec is broken. The grammar
  rules explicitly allow variables in predicates. The grammar really
  should be the overriding authority in formal specifications.
  Thanks again, although this makes my life much more difficult ;-)
  --
  ### SER Deutsch|Esperanto|Francaise|Linux|Java|Ruby|Aikido|Dirigibles|GPG ###
  ### jabber.com:ser ICQ:83578737 ###
  "(Bill Gates) shoots at a wall, and the industry paints a bullseye
  around his shot." -- Larry Press
  > I suppose it is too late to be complaining about the
  > specification, it being three years old and all, but the spec
  > is broken. The grammar
  > rules explicitly allow variables in predicates. The grammar really
  > should be the overriding authority in formal specifications.
  >
  Grammar rules are always subject to semantic rules, e.g. that variables
  must be declared before they are referenced.
  Some patterns can contain variable references, e.g. those used in
  xsl:number; it's the ones in xsl:template and xsl:key that can't.
  I agree with you that the restriction was a mistake. It was a
  last-minute attempt to fix a problem with circular references, and it
  turned out to be neither necessary nor sufficient to fix the problem.
  But it's there.
  Michael Kay
  Software AG
  home: Michael.H.Kay@...
  work: Michael.Kay@...
  The saxon:output instruction was changed at various stages to align it
  with the evolving working drafts from W3C. You should check the
  documentation for the release you are using. You are probably using
  Instant Saxon 6.5.2, which has the same specification as full Saxon
  6.5.2: use the -t option to be sure which release you are running.
  The specification at
  makes it clear that saxon:output is a synonym of xsl:document, described
  at
  (the link from saxon:output is broken, unfortunately)
  Changing the "file" attribute to "href", as the error messages suggest,
  will probably do the job, but you should be aware that there have been
  semantic changes between different releases as well.
  Michael Kay
  > -----Original Message-----
  > From: saxon-help-admin@...
  > [mailto:saxon-help-admin@...] On Behalf Of
  > Tsumaki, Junko
  > Sent: 25 March 2003 08:11
  > To: saxon-help@...
  > Subject: [saxon] (no subject)
  >
  >
  >
  >
  >
  I will give it a try. First I need to check that there are no incompatible
  changes between 7.3.x and 7.6.5.
  Thanks for this tip.
  Pascal
  Message: 5
  From: "Michael Kay" <mhk@...>
  To: "'Munerot Pascal'" <pascal.munerot@...>,
  <saxon-help@...>
  Subject: RE: [saxon] Throwing an exception from an XSL stylesheet or
  returning a resul t value
  Date: Tue, 15 Jul 2003 15:46:53 +0100
  There is an XPath 2.0 function error() which is intended to serve this
  purpose.
  You may need to move forward from 7.3.x to 7.6.5 to take advantage of
  it.
  Michael Kay
  > -----Original Message-----
  > From: saxon-help-admin@...
  > [mailto:saxon-help-admin@...] On Behalf Of
  > Munerot Pascal
  > Sent: 15 July 2003 09:06
  > To: 'saxon-help@...'
  > Subject: [saxon] Throwing an exception from an XSL stylesheet
  > or returning a resul t value
  >
  >
  > Hi all,
  >
  > I am using Saxon (7.3.x) in a reporting framework I made
  > (running inside a Tomcat / Glue Web service).
  >
  > In some cases, I have reports that happen to return 'no data'
  > at all (or the data is considered as not significant for
  > further processing).
  >
  > When it happens in Java; it is just fine ; I can handle it
  > from there. However, when I discover the corresponding
  > situation in the report stylesheets , I would like to be able
  > to raise an exception to the caller or at least have a return
  > value back so that I can raise the exception myself).
  >
  >
  > For this, I have tried to implement a template that calls a
  > java extension object (a class with a static method which
  > throws the exception I want).
  >
  > Problem is, it seems to break the XML stream and then the
  > transformation is terminated 'badly'. (I am also using Glue ;
  > a web service API from The Mind Electric which may cause this
  > last problem due to the exception mishandling).
  >
  > Anyone has done this before ? Or have an idea ?
  >
  > Having only a return value would suit me fine (However, by
  > looking at the Trax API (Transform...), I could not find the
  > way to do it.
  >
  > Thanks in advance for your help.
  >
  > Pascal
  >