Subject:One more feature Author:Adam Van den Hoven Date:04 Oct 2001 06:41 PM
I just noticed that the SenseX doesn't seem to have any awareness of "where it is". It seems wrong to me that it would "allow" me to place an xsl:template as a child of an xsl:text element. In the context of an xsl:choose element one would only expect xsl:when and xsl:otherwise.
It might also be nice to select schemas to use for SenseX when editing XML. this way one could first of all customize the XSL schema to include support for saxon or xt nodes. Have the editor check the listed namespaces and build the SenseX from that (if I'm transforming to MathML why should I be getting HTML tags?)
It seems to me to be a rather difficult feature to add since one can't expect to have a well formed document at any given time.
Subject:Re: One more feature Author:Minollo I. Date:04 Oct 2001 07:14 PM
At 06:48 PM 10/4/2001 -0400, you wrote:
>From: "Adam Van den Hoven"
>
>I just noticed that the SenseX doesn't seem to have any awareness of
>"where it is". It seems wrong to me that it would "allow" me to place an
>xsl:template as a child of an xsl:text element. In the context of an
>xsl:choose element one would only expect xsl:when and xsl:otherwise.
SenseX knows where it is as XSLT context (helping you when you do
select="..."); but you are right, it doesn't know yet where it is XSLT
grammar wise.
>It might also be nice to select schemas to use for SenseX when editing
>XML. this way one could first of all customize the XSL schema to include
>support for saxon or xt nodes. Have the editor check the listed namespaces
>and build the SenseX from that (if I'm transforming to MathML why should I
>be getting HTML tags?)
>
>It seems to me to be a rather difficult feature to add since one can't
>expect to have a well formed document at any given time.
We have a PCR open about that; as we are already doing a similar operation
in the XML editor (building the SenseX list from the associated DTD or
XMLSchema), we'll expose the same functionality in the XSLT editor, so that
you can choose to have just XSLT tags, or XSLT + FO or XSLT + FO + a custom
grammar or any combination of things. That will happen soon, but not in 3.1
final, as we are feature frozen now.