re: [cam] Default Namespaces

[David RR Webber - XML ebusiness <Gnosis_@compuserve.com>]

Martin,

I see the issue with a default namespace.  So we're basically
saying - we do not recommend people assigning a 
default namespace.

How about using an <as:include> to pull in that line, that way
the actual offending 
    xmlns="http://somenamespace.org/
declaration can sit outside of the XML instance, and therefore
the CAM processor will not be bothered by it - but it will get
generated into the final output?  We could add a mode to the
<as:include> to indicate if it happens  pre-parsing or post-parsing.

Thanks, DW.
======================================================= 

Message text written by INTERNET:martin.me.roberts@bt.com
> 
Hi, 
        The CAM spec needs to specify what will happen with default
namespaces. 

        In one of the samples based on the BOD two occurances of default
namespaces exist: 

        one for CAM and one within the structure.  The problem with this is
that XPATH can not handle default namespaces, ie. A namespace-uri that has
not associated prefix.  It can handle no namespace.

        This must be explained in the document as processing the contents
is
not possible where the xpath expressions do not use any prefixes if there
is
a default namespace uri.

Exactly.  /ApplicationArea will only match <ApplicationArea> but not
<ApplicationArea xmlns="http://somenamespace.org/
<http://somenamespace.org/> "/>

        This means that CAM templates need to be more carefully created. 
<