Kay, Michael | 2 Jun 21:46 2002

RE: xslt 2.0 vs xslt 1.0 !

If you are new to XSLT, Othman, then I suggest you concentrate on learning XSLT 1.0 and XPath 1.0 for the time being, since the 2.0 versions are still under development and not available yet in most products.
 
The only real way to learn about XSLT 2.0 and XPath 1.0 at present is to study the W3C specifications, though you will probably find it useful to read Evan Lenz's introductory articles first:
 
 
Michael Kay
-----Original Message-----
From: Othman Haddad [mailto:ohaddad <at> neomalogic.com]
Sent: 31 May 2002 16:28
To: xsl-editors <at> w3.org
Cc: public-qt-comments <at> w3.org
Subject: xslt 2.0 vs xslt 1.0 !

 
 
i'm sorry,
but i was wondering if studying any xslt tutorial is ok for me, even if i want to work on the new XSLT2.0?
are they too many differences ?, i know there are some between XPATH 1.0 and XPATH2.0 (sequences instead of nodes etc..), but does it change anything for the XSLT?
thank you..
 
Tim Stewart | 5 Jun 19:40 2002

XSLT - trim-whitespace function


Hi,
   I was wondering if the W3C had any plans to add a whitespace
trimming function to XSLT's function set.  The function would only trim
leading and trailing whitespace.  I am using XSLT to generate source code
where "internal" whitespace can play a significant role.  The function
normalize-space() would not work for me in this scenario.

Thanks a lot for your time.

Tim Stewart

Mihai Ionescu | 6 Jun 16:10 2002
Picon

<oXygen/> XML Editor 1.1.9


Hello,

<oXygen/> XML Editor 1.1.9 is available for download
http://oxygen.sync.ro/generate.php?topicID=download

New in this version:
    * XML Schema driven code insight is improved to offer attribute values
in case of enumeration and default values and to handle multiple namespaces.
    * The checks for valid and well formed documents and the apply
stylesheet operations run on a different thread so that the GUI remains
usable
    * Acknowledgements of the above operations are replaced with
notifications in status bar to avoid interruptions.
    * Registration form in application - now, you can get your license
submiting informations using a registration form which is loaded if no
license detected.
    * Improved GUI
    * Support for changing the printing scale factor

<oXygen/> XML Editor supports XML, XSL, TXT, XSD and DTD documents.
<oXygen/> is written in Java; it has a high development dynamics and is
availabile on many platforms. It has Unicode support and the interface is
available in English, French, German, Italian and Romanian. <oXygen/> goal
is to make tasks shorter, thus it offers end tag auto-completion and a
powerful code insight that guide the user to write valid XML content. The
code can be driven by a DTD, an XML schema or by the structure of a partial
edited document. Taking manipulation of XML content into consideration XML
and XSL documents can be easily associated one with the other and the
transformation results can be viewed in different formats; more the user can
test XPath expressions. <oXygen/> validates XML, XSL and XSD content,
reporting eventual errors with description and line number information. The
multiple document interface is enhanced with the support for projects. It
has drag and drop support and on Windows it can be associated with file
extensions. The syntax highlight allows a nice view of the XML documents and
the colors can be customized.

Best Regards,
Mihai

Max Froumentin | 6 Jun 16:24 2002
Picon

Re: <oXygen/> XML Editor 1.1.9


Please refrain from sending commercial email to this list. Even if it is
related to XSLT, this is not the right forum. 

Max.

"Mihai Ionescu" <mihai <at> sync.ro> writes:

> Hello,
>
> <oXygen/> XML Editor 1.1.9 is available for download
> http://oxygen.sync.ro/generate.php?topicID=download
>
> New in this version:
>     * XML Schema driven code insight is improved to offer attribute values
> in case of enumeration and default values and to handle multiple namespaces.
>     * The checks for valid and well formed documents and the apply
> stylesheet operations run on a different thread so that the GUI remains
> usable
>     * Acknowledgements of the above operations are replaced with
> notifications in status bar to avoid interruptions.
>     * Registration form in application - now, you can get your license
> submiting informations using a registration form which is loaded if no
> license detected.
>     * Improved GUI
>     * Support for changing the printing scale factor
>
> <oXygen/> XML Editor supports XML, XSL, TXT, XSD and DTD documents.
> <oXygen/> is written in Java; it has a high development dynamics and is
> availabile on many platforms. It has Unicode support and the interface is
> available in English, French, German, Italian and Romanian. <oXygen/> goal
> is to make tasks shorter, thus it offers end tag auto-completion and a
> powerful code insight that guide the user to write valid XML content. The
> code can be driven by a DTD, an XML schema or by the structure of a partial
> edited document. Taking manipulation of XML content into consideration XML
> and XSL documents can be easily associated one with the other and the
> transformation results can be viewed in different formats; more the user can
> test XPath expressions. <oXygen/> validates XML, XSL and XSD content,
> reporting eventual errors with description and line number information. The
> multiple document interface is enhanced with the support for projects. It
> has drag and drop support and on Windows it can be associated with file
> extensions. The syntax highlight allows a nice view of the XML documents and
> the colors can be customized.
>
> Best Regards,
> Mihai

Kay, Michael | 6 Jun 17:40 2002

RE: XSLT - trim-whitespace function


>    I was wondering if the W3C had any plans to add a 
> whitespace trimming function to XSLT's function set.  The 
> function would only trim leading and trailing whitespace.  I 
> am using XSLT to generate source code where "internal" 
> whitespace can play a significant role.  The function
> normalize-space() would not work for me in this scenario.
> 

We are working on regular expression capabilities which should satisfy this
need, but there's a lot of detail to be sorted out and agreed before we get
there.

In XSLT 1.0 you can do it using a recursive template, but I agree it's not
easy.

Michael Kay

Max Froumentin | 6 Jun 18:29 2002
Picon

Re: XSLT - trim-whitespace function


"Kay, Michael" <Michael.Kay <at> softwareag.com> writes:

> In XSLT 1.0 you can do it using a recursive template, but I agree it's not
> easy.

Dimitre Novatchev has posted a "trim" template on xsl-list a while ago

http://www.biglist.com/lists/xsl-list/archives/200112/msg01067.html

Max.

Werner Donné | 11 Jun 14:17 2002
Picon

Add assert element


Hi,

In order to prevent fatal errors from passing by unnoticed it would be 
interesting to
have an "assert" element with a "test" attribute, just like with the "if" and 
"when"
elements. The contents of the element could be anything that generates a 
message.
Whenever the evaluation of the test would fail, processing would stop after 
producing
the error message. For example:

<xsl:template name="foo">
  <xsl:param name="par"/>
  <xsl:assert test="number($par) > 0">
    <xsl:text>Parameter par of template foo has value </xsl:text>
    <xsl:value-of select="$par"/>
    <xsl:text>, while it must be a strictly positive number.</xsl:text>
  </xsl:assert>
  ...
</xsl:template>

Regards,

Werner.

--
Werner Donné  --  Re BVBA
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803   e-mail: werner.donne <at> re.be

Kay, Michael | 11 Jun 17:00 2002

RE: Add assert element


A nice-to-have, but you can achieve the same effect today with

<xsl:if test="not(assertion)">
  <xsl:message terminate="yes">Failed here!</xsl:message>
</xsl:if>

Michael Kay

> -----Original Message-----
> From: Werner Donné [mailto:werner.donne <at> re.be] 
> Sent: 11 June 2002 13:17
> To: xsl-editors <at> w3.org
> Subject: Add assert element
> 
> 
> 
> Hi,
> 
> In order to prevent fatal errors from passing by unnoticed it 
> would be 
> interesting to
> have an "assert" element with a "test" attribute, just like 
> with the "if" and 
> "when"
> elements. The contents of the element could be anything that 
> generates a 
> message.
> Whenever the evaluation of the test would fail, processing 
> would stop after 
> producing
> the error message. For example:
> 
> <xsl:template name="foo">
>   <xsl:param name="par"/>
>   <xsl:assert test="number($par) > 0">
>     <xsl:text>Parameter par of template foo has value </xsl:text>
>     <xsl:value-of select="$par"/>
>     <xsl:text>, while it must be a strictly positive 
> number.</xsl:text>
>   </xsl:assert>
>   ...
> </xsl:template>
> 
> Regards,
> 
> Werner.
> 
> --
> Werner Donné  --  Re BVBA
> Engelbeekstraat 8
> B-3300 Tienen
> tel: (+32) 486 425803   e-mail: werner.donne <at> re.be
> 

Werner Donné | 11 Jun 17:07 2002
Picon

RE: Add assert element


Indeed. I didn't expect the terminate attribute in the message element.

Werner.

>===== Original Message From "Kay, Michael" <Michael.Kay <at> softwareag.com> =====
>A nice-to-have, but you can achieve the same effect today with
>
><xsl:if test="not(assertion)">
>  <xsl:message terminate="yes">Failed here!</xsl:message>
></xsl:if>
>
>Michael Kay
>
>> -----Original Message-----
>> From: Werner Donné [mailto:werner.donne <at> re.be]
>> Sent: 11 June 2002 13:17
>> To: xsl-editors <at> w3.org
>> Subject: Add assert element
>>
>>
>>
>> Hi,
>>
>> In order to prevent fatal errors from passing by unnoticed it
>> would be
>> interesting to
>> have an "assert" element with a "test" attribute, just like
>> with the "if" and
>> "when"
>> elements. The contents of the element could be anything that
>> generates a
>> message.
>> Whenever the evaluation of the test would fail, processing
>> would stop after
>> producing
>> the error message. For example:
>>
>> <xsl:template name="foo">
>>   <xsl:param name="par"/>
>>   <xsl:assert test="number($par) > 0">
>>     <xsl:text>Parameter par of template foo has value </xsl:text>
>>     <xsl:value-of select="$par"/>
>>     <xsl:text>, while it must be a strictly positive
>> number.</xsl:text>
>>   </xsl:assert>
>>   ...
>> </xsl:template>
>>
>> Regards,
>>
>> Werner.
>>
>> --
>> Werner Donné  --  Re BVBA
>> Engelbeekstraat 8
>> B-3300 Tienen
>> tel: (+32) 486 425803   e-mail: werner.donne <at> re.be
>>

--
Werner Donné  --  Re BVBA
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803   e-mail: werner.donne <at> re.be

DPawson | 18 Jun 09:02 2002
Picon

feature request.


That it be possible to utilise a given namespace for
(effectively) comments, i.e. the named namespace is not
treated as a literal and output.

Rationale:

 E.g. constructing an
outline of the stylesheet operation,
explanatory documentation,  
providing multi-modal representations, etc.

Perhaps something like
<xsl:ns-ignore prefix='doc'/>

The stylesheet application then simply bypasses anything
in that namespace, treating it as a comment.

This would support conformance to the XML accessibility guidelines.

http://www.w3.org/TR/xag

regards DaveP

************snip here************** 

- 

NOTICE: The information contained in this email and any attachments is 
confidential and may be legally privileged. If you are not the 
intended recipient you are hereby notified that you must not use, 
disclose, distribute, copy, print or rely on this email's content. If 
you are not the intended recipient, please notify the sender 
immediately and then delete the email and any attachments from your 
system.

RNIB has made strenuous efforts to ensure that emails and any 
attachments generated by its staff are free from viruses. However, it 
cannot accept any responsibility for any viruses which are 
transmitted. We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email 
and any attachments are those of the author and do not necessarily 
represent those of RNIB.

RNIB Registered Charity Number: 226227

Website: http://www.rnib.org.uk 

14th June 2002 is RNIB Look Loud Day - visit http://www.lookloud.org.uk to
find out all about it.


Gmane