[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: support for namespace axis?

Subject: RE: support for namespace axis?
From: "Vun Kannon, David" <dvunkannon@xxxxxxxx>
Date: Thu, 2 Dec 1999 10:44:06 -0500
namespace axis
	Indeed, I thought my original message made clear that I was working
with multiple namespaces. Here is a sample document from the Microsoft
Biztalk.org website:
<BizTalk xmlns=
  "urn:schemas-biztalk-org:biztalk-0.81.xml">
<Route>
. . . see above . . .
</Route>
<Body>
<PurchaseOrder xmlns=
  "urn:schemas-biztalk.org:your-namespace/purchaseorder.xml">
<POHeader> 
<PONumber>12345</PONumber>
<PaymentType>INVOICE</PaymentType> 
<POShipTo>
<street1>Your Street 1</street1>
<street2>Your Street 2</street2> 
<city>Your City</city>
</POShipTo >
<POBillTo>
<street1>Your Street 1</street1>
<street2>Your Street 2</street2> 
<city>Your City</city>
</POBillTo >
</POHeader>
<POLines>
<Item>
<partno>ikypop1</partno>
<quantity>1</quantity>
<unitPrice>14.00</unitPrice>
</Item>
</POLines>
</PurchaseOrder>
</Body>
</BizTalk>

	It uses the default namespace to enable the simple wrappering of the
BizTalk tags around messages in another vocabulary. Here's a simple
stylesheet that attempts to work with such a document:

<stylesheet xmlns="http://www.w3.org/1999/XSL/Transform">
	<!-- This stylesheet will transform the XML into 
		another document, using the identity transform template
-->
	<template match="@*|*|comment()|text()|processing-instruction()">
		<copy>
			<apply-templates
select="@*|*|comment()|text()|processing-instruction()"/>
		</copy>
	</template >
	<template match="//city">Found a city
		<copy>
			<apply-templates
select="@*|*|comment()|text()|processing-instruction()"/>
		</copy>
	</template>
</stylesheet>

	I would expect the output from the stylesheet to include "Found a
city" before the copy of the city element, but it does not. I use XT of
19991105.
	IMHO, the stylesheet, which obviously knows the vocabulary that
includes city, should be able to process documents that reference such
elements irregardless of the namespace given to that vocabulary in the
source document, i.e. it shouldn't matter to the match expression whether
the source contains city elements or blah:city elements. I thought the
namespace axis was the lever I needed to accomplish this.
	Given the push to modularise and compose XML vocabularies, I feel
this is an important area to clarify for my own work.
Cheers,
David vun Kannon

-----Original Message-----
From: Kay Michael [mailto:Michael.Kay@xxxxxxx]
Sent: Thursday, December 02, 1999 8:54 AM
To: 'xsl-list@xxxxxxxxxxxxxxxx'
Subject: RE: support for namespace axis?


A new version of SAXON will be out in the next day or two (though I've been
saying that for a couple of weeks), with support for the namespace axis, as
well as just about everything else in XSLT and XPath 1.0

I'm interested to know why you need the namespace axis, I've yet to find a
use for it myself, except for the situation where namespace prefixes are
used within the user data.

Mike Kay

> -----Original Message-----
> From: Vun Kannon, David [mailto:dvunkannon@xxxxxxxx]
> Sent: 01 December 1999 17:47
> To: 'xsl-list@xxxxxxxxxxxxxxxx'
> Subject: support for namespace axis?
> 
> 
> 	I have failed in some recent work to apply transformations to
> documents that draw on several namespaces. It seems that I 
> probably should
> be using the namespace axis in my XPath expressions. It 
> doesn't seem that XT
> or Saxon implement this axis. I'd be interested to hear if 
> any implementors
> could comment on their plans/conformance.
> Cheers,
> David vun Kannon
> **************************************************************
> ***************
> The information in this email is confidential and may be 
> legally privileged.
> It is intended solely for the addressee. Access to this email 
> by anyone else
> is unauthorized. 
> 
> If you are not the intended recipient, any disclosure, 
> copying, distribution
> or any action taken or omitted to be taken in reliance on it, 
> is prohibited
> and may be unlawful. When addressed to our clients any 
> opinions or advice
> contained in this email are subject to the terms and 
> conditions expressed in
> the governing KPMG client engagement letter.         
> **************************************************************
> ***************
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
*****************************************************************************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter.         
*****************************************************************************


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.