Quoting joern turner:
> Eduardo Millán wrote:
>
> > Quoting joern turner:
> > Well, the ampersand (&) is one of them, I guess. Think about the
> *character
> > entities* as well, quotes("), apostrophe('), and the like.
>
> ok, right. i silently assumed that expression inside of {} conform to
> the typical syntax used in xslt so these would be restricted to use:
> -a function name such context()
> -a locationpath
> -a single quoted string
> -a number
> -predicate expressions as part of locationpathes
Ok, then we can make a try. ;)
> the *evaluated* string surely should conform to the characterset allowed
> for URIs
I see no problem with URI's, as the function is responsible to return it in the
right way, as you perfectly explained. I was wondering about special characters
in the XML side.
Nevermind, lets start with this job.
Cheers.
--
Eduardo Millán
Technical Telecommunications engineer, specialist in Telematics
Java programmer and analyst
ALBA Software: http://www.albasoft.com
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
|
