OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cam message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [cam] Default Namespaces


David,
	Sorry you have not got it quite right.  The issue is not the
prefix but the URI.  If you want an example which uses a namespace of
any sort, then the CAM template MUST associate a prefix with the uri and
use it within all the Xpath statement.

	The only case where CAM will NOT require a namespace and
associated prefix is when the example you are using has NO NAMESPACE
definition.

	In other words.  CAM will work in exactly the same way as XSLT
in that it does not support the use of namespaces without associating a
prefix.  

	So if you look at the examples I sent you will see that the CAM
template has the namespace for the bod associated with the prefix bod.
The xml file that conforms to that template does not require a prefix as
CAM will match via the namespace uri not the prefix.

Martin Roberts 
xml designer, 
BT Exact
e-mail: martin.me.roberts@bt.com 
tel: +44(0) 1473 609785  clickdial
fax: +44(0) 1473 609834
Intranet Site :http://twiki.btlabs.bt.co.uk/twiki



-----Original Message-----
From: David RR Webber - XML ebusiness [mailto:Gnosis_@compuserve.com] 
Sent: 03 July 2003 19:10
To: Roberts,MME,Martin,XSG3 R
Cc: cam@lists.oasis-open.org
Subject: RE: [cam] Default Namespaces


Martin,

OK - I'm trying to restate the problem here.

If the output structure is using a default namespace prefix, then we
have to use one in the CAM template too.

If the output structure is not using a namespace prefix, then we do not
need one on the CAM template (apart from the as:  for embedded
functions).

This means with have two styles - one where prefix is required, and one
where its not.

Correct?

Thanks, DW.
==================================================================
Message text written by INTERNET:martin.me.roberts@bt.com
>       The issue is that CAM templates must NOT have default
namespaces.  The instance documents can.  This is the same rule as for
XSLT.

        Therefore you will see fro the attached bod example that I have
changed the cam template and left the instance document alone.

        I feel that this is very important as without it we would be not
fully namespace savvy.  
<



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]