Nick, yes, I think it all makes sense!
-Erik
On Thu, Jun 21, 2012 at 5:23 AM, Nick Van den Bleeken <
Nick.Van.den.Bleeken@inventivegroup.com> wrote:
> All,
>
> Is was about to add text to the spec that stated that it is an error to
> add functions to the XForms or XPath function namespace. While having a
> look at the XSLT spec I noticed that you aren't allowed to define custom
> functions in one of the reserved namespaces, nor are you allowed to define
> variables in those namespaces. It kind of makes sense to me not to be able
> to add variables to the XForms namespace, maybe we want to add variables in
> the XForms namespace in the future, and then it is good practice to prevent
> form authors to add variables to our namespace.
>
> I also noticed that in xslt 'The default namespace of the defining
> element (see Section 6.2 Element Nodes<http://www.w3.org/TR/xpath-datamodel/#ElementNode>
> DM) is *not* used for unprefixed names.' I think that we should also do
> this, otherwise if people change the default namespace to our xforms
> namespace the variables will be in XForms namespace (which I think we
> shouldn't allow).
>
> I also think that we should allow other modules to add restrictions to
> which namespaces aren't allowed for adding functions and variables into.
> For example the XPath expression module will prevent adding variables and
> custom functions to the XPath function namespace.
>
> Kind regards,
>
> Nick Van den Bleeken
> R&D Manager
>
> Phone: +32 3 425 41 02
> Office fax: +32 3 821 01 71
> nick.van.den.bleeken@inventivegroup.com
> www.inventivedesigners.com
>
>
>
>
> ------------------------------
>
> Inventive Designers' Email Disclaimer:
> http://www.inventivedesigners.com/email-disclaimer
>
