On Jan 12, 2006, at 4:43 AM, Bryan Rasmussen wrote:
various points so far, rated on scale of 1 to 10, 10 being most
important:
the following feature doesn't connect directly to the XSLT filter, but
it seems to me that one of the most important
things would be "validation" either based on XML Schema or RelaxNG. I
mean in the sense having a document loaded, that
one can only apply "custom styles" as the schema is allowing to.
As a general rule I would want validation to be seperable from
transformation, which I guess you're suggesting here. I have noted
though
that sometimes people like to have validation at the point of
transformation, I think this is basically a question as to how people
like
to structure their solutions and both should be supported.
value of adding validation: 4
reason: By adding validation you are opening up a large area for
development, with possibility of lots of different side effects, could
be a
big time drain. If validation is required one can still add validation
via
other ways. That said it is a selling feature. Maybe Star Office
should have
validation, using Sun's Multi-Schema Validator?
I agree. I don't see the value of adding validation here.
If one has an enterprise with 1000 users for instance
then it's not that nice to have install
the package every time a new version has been released of the package.
Agreed, this would be the difference between packages being useful for
an
expert user/hacker to being useful for administrators.
value of making packages load on the fly: 8
Agreed.
Some debug facility might be a nice thing to have -- at least some
sort
of support for xsl:message.
I never use xsl:message myself, but I suppose others do.
value of xsl:message: 3
I'd put the value slightly higher; maybe 6.
When discussing Saxon integration it might be useful to have a method
of
switching processors, I've noted this before in large applications
such as
OO as a (minor) selling point. In the context of XSLT 2.0 this might
be more
pronounced because it looks like support for XML Schema integration
with
XSLT 2.0 processors will be for processors one has paid for.
value of switching processors: 6 (unless I have saxon in which case
not so
much)
Agreed.
hmm, guess I only got up to 8. What was it Dick Clark said. Of course I
think parameters are at least an 8. They are pretty much used in any
serious
XSLT usage.
Also agreed.
The one caveat I'd add here is that it might be valuable to consider a
config mechanism for parameters. If for example, a parameter
effectively takes an option from an enumerated list (let's say "yes"
and "no"), then:
1. there's no way for the user to have a pop-up list of options without
configuring it outside the XSLT
2. you couldn't localize without the config option
Bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
