W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > June 2008

Re: XSLT functions

From: Innovimax SARL <innovimax@gmail.com>
Date: Thu, 26 Jun 2008 16:35:30 +0200
Message-ID: <546c6c1c0806260735g359403a7p60f3e7fe2164d6bd@mail.gmail.com>
To: "Norman Walsh" <ndw@nwalsh.com>
Cc: public-xml-processing-model-wg@w3.org
Well...

generate-id() has many use in XSLTMatchPattern for testing node equality (in
XSLT 1.0)

If we forbid all, I would ask for having p:generate-id()

I also admit that unparsed-text()
unparsed-text-available()


On Thu, Jun 26, 2008 at 4:19 PM, Norman Walsh <ndw@nwalsh.com> wrote:

> XSLT adds 19 functions to XPath. Several make no sense because they rely
> on XSLT instructions:
>
> current()
> current-group()
> current-grouping-key()
> element-available()
> function-available()
> key()
> regex-group()
>
> A few we can easily do without because we have our own mechanisms
> (or we already support them):
>
> document()
> system-property()
>
> That leaves these:
>
> format-date()
> format-dateTime()
> format-number()
> format-time()
> generate-id()
> type-available()
> unparsed-entity-public-id()
> unparsed-entity-uri()
> unparsed-text()
> unparsed-text-available()
>
> On balance, I think we should say that they're all forbidden.
> Even in XSLT Match patterns?
>
>                                        Be seeing you,
>                                          norm
>
> --
> Norman Walsh <ndw@nwalsh.com> | One does what one is; one becomes what
> http://nwalsh.com/            | one does.--Robert Musil
>



-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Thursday, 26 June 2008 14:36:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 June 2008 14:36:07 GMT