XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » XSLT Help and Discussion » Using XSLT to transform XML to qualified XML
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
+ Stylus Studio Technical Forum (14621)
+ Website Feedback (249)
- XSLT Help and Discussion (7625)
-> + How to add page number in to v... (2)
-> + XSL Grouping (7)
-> + Repeat images using FOR EACH l... (7)
-> + How to get File name (2)
-> + image and text on the same lin... (2)
-> + Create XSLT stylesheets for us... (2)
-> + Merge Multiple Files While Che... (2)
-> + xslt 3 level or multi level gr... (6)
-> + How to create xsl which will c... (2)
-> + xsl:variable and Result Tree F... (7)
-> - XSL-FO fo:table continued from... (1)
-> + XSLT Java issue (2)
-> + problem with hyperlink (4)
-> + substring-after function probl... (4)
-> + Xalan Processing (3)
-> + Memory utilization high with m... (2)
-> + check all parent node groups s... (2)
-> + CSV DOC to XML CONVERSION (11)
-> + XSLT: Ordered List (based on r... (4)
-> + XSLT Mapping - Issue (4)
-> + XSL following-sibling, how to ... (5)
-> + need xslt elements help (2)
-> + Dynamic generation of URL in X... (2)
-> + List Created from Section Navi... (2)
-> + xslt elements help (2)
-> + Map field if source is not nul... (3)
-> + XSLT group and sort whith gene... (4)
-> + Nested XML value (2)
-> + Specifying condition with coun... (4)
-> + xsl:function using found in er... (4)
-> + How to remove an unwanted spac... (2)
-> + Question about variable substi... (2)
-> + XSL for Comparing nodes and di... (4)
-> + External lookup list (8)
-> + XSL HTML output now needs to b... (2)
-> + Adding a new sub element to th... (4)
-> + How do I get rid of 'Tip' node... (9)
-> + Trying to dynamically create n... (2)
-> + Display XML link, using XSLT a... (9)
-> + calling templates based on ord... (2)
-> + How to add internal links usin... (4)
-> + How to call user defined java ... (3)
-> + XSLT and WebApps past and futu... (3)
-> + passing condition through java... (3)
-> + Apllying a template from withi... (4)
-> + Getting xsl element in javascr... (3)
-> + The document() function inside... (3)
-> + Footnote text move to para (2)
-> + XSL: multiple element come to ... (3)
-> + How to use following-sibling &... (2)
-> + How to use FOP 0.95 with Stylu... (4)
-> + Error during creating PDF from... (2)
-> + Help creating a comma delimite... (4)
-> + Selective Add using XSLT recur... (3)
-> + Help: convert without parent e... (2)
-> - Correct my substring function ... (1)
-> + Old xsl into reports (4)
-> + How to save xslt converted fil... (3)
-> + How to find non tagging text? (5)
-> + Help: Hex entity to Character... (6)
-> + EDI QUOTES MESSAGE NEED TO REP... (2)
-> + How to convert in multi level ... (4)
-> + Need some help with a styleshe... (3)
-> - Conditional Formattinf Formula... (1)
-> + Creating HTML Unordered LIsts.... (2)
-> + xslt params uknown number of i... (2)
-> + How to use fonts other than ba... (2)
-> - Converting existing HTML into ... (1)
-> + Help to tune up this XSLT (2)
-> + XSLT - is only converting the ... (2)
-> + XSLT Editor tab (4)
-> + Convert multiple files from XM... (2)
-> + how to use in select expressi... (2)
-> + Help needed in XSL transformat... (2)
-> + How to add a string with math ... (5)
-> + How to add a string with math ... (6)
-> - br element (1)
-> + Stylesheet directed terminatio... (2)
-> + Who can help me whit sum funct... (2)
-> + XSLT Works in Stylus Studio, n... (3)
-> - Filter by Attribute (1)
-> + Display x number of items whic... (6)
-> + MultiColumn Reporting (3)
-> + cant get namespace declaration... (3)
-> + Performance xsl:for each and n... (3)
-> + How to assign value to a XSLT ... (3)
-> + Select element value based on ... (2)
-> + Version 10 of Saxon? (8)
-> + How to get the value of a node... (5)
-> + Display Xpath using (4)
-> + XSLT to report (2)
-> + xslt help for a noobie (2)
-> + XSL-FO XML to PDF with XSLT (3)
-> - Using XSLT to transform XML to... (4)
-> ->Using XSLT to transform X...
-> ->Using XSLT to transform X...
-> ->Using XSLT to transform X...
-> + XSLT to sort a list alphabetic... (4)
-> + How to Get Colum Values based ... (2)
-> + non persisting predicate filte... (5)
-> + HTML to XSLT (2)
-> + extra carriage returns in "csv... (2)
-> + extra carriage returns in "csv... (3)
-- Previous [301-320] [321-340] [341-360] Next
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Zach SSubject: Using XSLT to transform XML to qualified XML
Author: Zach S
Date: 12 Mar 2009 04:56 PM
To anyone who can help,

My issue is that I have just finish redoing an XML Schema, in which I have taken a schema that was all in one file and separated it into multiple schema documents that call one another by way of <import>. The original (one document schema) was a no-namespace schema. In order to provide the hierarchy I needed I had to use namespaces in the new schema with the <import> ability.

The issue here is that I have a ton of test files that use the no-namespace schema, and I was hoping to write an XSLT file to transform these test XML files from having elements with no namespace prefixes to elements with proper namespace prefixes. That is all I want to change, I want everything else to remain the same and to be ported over into the new XML test documents.

For example:

current XML test document:
<EMP>
<PropCalc>
<SectorJob>
<StartPoint x="90" y="30"/>
<Antenna>
<Dipole gain="30"/>
</Antenna>
</SectorJob>
</PropCalc>
</EMP>

new XML test document (what I need it to look like after the XSLT transformation):
<EMP>
<prop:PropCalc>
<prop:SectorJob>
<util:StartPoint x="90" y="30"/>
<ant:Antenna>
<ant:Dipole gain="30"/>
</ant:Antenna>
</prop:SectorJob>
</prop:PropCalc>
</EMP>

XSLT I have tried:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml"/>
<xsl:template match="/">
<xsl:apply-templates select="*"/>
</xsl:template>
<xsl:template match="node()">
<xsl:copy>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="PropCalc">
<prop:PropCalc>
<xsl:apply-templates select="@* | node()"/>
</prop:PropCalc>
</xsl:template>
<xsl:template match="SectorJob">
<prop:SectorJob>
<xsl:apply-templates select="@* | node()"/>
</prop:SectorJob>
</xsl:template>
<xsl:template match="StartPoint">
<util:StartPoint>
<xsl:apply-templates select="@* | node()"/>
</util:StartPoint>
</xsl:template>
<xsl:template match="Antenna">
<ant:Antenna>
<xsl:apply-templates select="@* | node()"/>
</ant:Antenna>
</xsl:template>
<xsl:template match="Dipole">
<ant:Dipole>
<xsl:apply-templates select="@* | node()"/>
</ant:Dipole>
</xsl:template>
</xsl:stylesheet>

I have also tried declaring the prop, ant, and util namespaces in the <xsl:stylesheet> element and used exclude-result-prefixes to try and get the xmlns attributes to not appear - this didn't work.

The problem is that my output document has the xmlns:*="*" attribute declared for each element in the new XML test document. I don't want this because I plan on globally declaring all namespaces in the XML test document and want the prefixes put in place to reference these global namespace declarations.

Thanks in advance for your time and help.

Postnext
John BamptonSubject: Using XSLT to transform XML to qualified XML
Author: John Bampton
Date: 13 Mar 2009 06:34 AM
XSLT output will always be namespace-well-formed. If an element in the result tree uses the prop: prefix, then the result tree will contain a declaration of that prefix. There is no way of switching this off, any more than you could generate an end tag that doesn't match the corresponding start tag

Cheers, John Bampton.
Postnext
Zach SSubject: Using XSLT to transform XML to qualified XML
Author: Zach S
Date: 13 Mar 2009 09:53 AM
Thats what I was afraid of. Thanks.
Posttop
Zach SSubject: Using XSLT to transform XML to qualified XML
Author: Zach S
Date: 13 Mar 2009 01:01 PM
So, I found a solution to my "unsolvable problem" that I thought I would post here in case anyone else had the same problem I did.

Inside the <xsl:stylesheet> element declare the namespaces to be used. The idea is then to get these namespaces to be declared inside the root element of the XSLT output document. Upon doing so all the elements that are children of the root element (everything) XSLT will not need to declare their respective namespaces explicitly.

To get the namespaces declared inside <xsl:stylesheet> to show up in the root element of the output XML document use the following code:

<xsl:template match="/*">
<xsl:element name="{local name of root element}">
<xsl:copy-of select="document('')/xsl:stylesheet/namespace::*[name() != 'xsl']"/>
<xsl:apply-templates select="node()"/>
</xsl:element>
</xsl:template>


I believe this essential creates a new root element with the namespaces added, but as long as the local name of the root element stays the same, nothing has changed from the input XML to the output XML (with the obvious exception of the added namespaces).

I hope this helps anyone who happens to have the same problem I did. Enjoy.
   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.