XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + Unresponsive - Custom XML Conv... (2)
-> - Need Help defining Flat File w... (1)
-> + XML to Database (6)
-> + XSD path when associating to a... (3)
-> - Auto EDI File Translation (1)
-> + Need help parsing EDI and crea... (2)
-> + Bug in generating Xml from Dtd (7)
-> + Stylus Studio 15, install erro... (4)
-> + How to create UML from XSD (2)
-> + Java configuration (4)
-> + embedding/starting X15 dircet ... (2)
-> + Stylus X15 R2 environment crip... (5)
-> + Output Method TEXT does not wo... (6)
-> + CONV loses its format on re-op... (5)
-> - Trouble Converting 846 EDI Fil... (1)
-> + XML Catalog support - DITA (2)
-> + non-persistent VDI, App-V Lice... (2)
-> + Can we READ XLS file and Conve... (8)
-> + Mapping XML to XML (3)
-> + SS X15 - Getting Error with 45... (2)
-> + Optimal for DB to XML? (2)
-> + Issues exporting SQL Server ->... (2)
-> + need additinal field in XML (2)
-> + blinking (3)
-> + HELP ANYONE PLEASE (3)
-> + xi:include including include s... (2)
-> + Validating an XML file against... (2)
-> + XML to EDI Telco D.0 field len... (2)
-> + Converting EDIFACT to XML in c... (3)
-> + XSLT Transformation fails with... (4)
-> + StylusStudio X15 R2 java Auto ... (6)
-> + StylusStudio X15 Review - firs... (2)
-> + Stylus Studio X15 stuck on pro... (11)
-> + Error handling in Coverter fil... (2)
-> + RESTful Web Services in Stylus... (3)
-> + How to produce a human-readabl... (3)
-> + EDI 945 to AX (2)
-> + Help x15 failing install (5)
-> + XSD 1.0/1.1 schema validation ... (3)
-> + Java Runtime Environment 8.0 (3)
-> + Web Service Call to Oracle OSM... (2)
-> + Telco EDI to XML output on opt... (12)
-> + Authentication failed (2)
-> + no declaration found for eleme... (2)
-> + Component installation failed (5)
-> - Component installation failed (1)
-> - AUP to expire (1)
-> + Disable Automatic Updates in S... (2)
-> + Windows 7 64 bit compatibility (2)
-> + EDI 8.1 to 10.6 (2)
-> - Conerting EDI 8.1 to EDI 10.6 ... (1)
-> + Debugging with Java built-in p... (3)
-> + Moving Stylus Studio (2)
-> + When using an xsl:import file,... (3)
-> + Generate XSD file from XML fil... (2)
-> + Custom XML Conversion (2)
-> + Create XML from XSD schema fil... (4)
-> + Slimed by Microsoft Word 2010 (6)
-> + XML to EDI (Telco D.0) convers... (3)
-> + XML Pipeline Troubleshooting (10)
-> + Allow negative values in Telco... (7)
-> + Unable to add new arguments to... (2)
-> + Validating XML Document (4)
-> + Debugging with X15 and MSXML p... (2)
-> + Parameter values (5)
-> + Limit on size of schema/instan... (4)
-> + Enterprise 12r1-The decompress... (5)
-> + Lost my copy - how do I renew? (2)
-> + Add Arguments to JVM does not ... (10)
-> + Page-position='last' not inple... (3)
-> + Decode the base 64 encrypted f... (2)
-> + XALAN Processor (4)
-> + How to create an XSD for flat ... (4)
-> + xslt saxon processor failure (3)
-> + Variables window Context path ... (4)
-> + XLS Formatting Objects Preview... (7)
-> + German DTA File (2)
-> + EDI to XML and LX segment (2)
-> - The element with name "F0101Z2... (1)
-> + How to insert the current date... (3)
-> + XSD - XML Sample (4)
-> + XSD to XML (3)
-> + Java extension functions, Xala... (2)
-> + XML with XSD to PDF (7)
-> + mapped network drives not show... (5)
-> + WCF Message size (2)
-> + Re-imaged desktop/laptop lost ... (4)
-> + Relative path in Stylus Studio (2)
-> + & and & in web service cal... (8)
-> + Which JRE do I need now? (3)
-> + Line Delimitted File Conversio... (4)
-> + Generating EDI Data from XML w... (2)
-> + Generating an XML file using C... (2)
-> - Generating an XML file from (1)
-> + output document cannot be pars... (10)
-> + convert RELAX NG to xsd (2)
-> + Intended Use of a .sef File (3)
-> + Skipping invalid records on SQ... (5)
-> + EDI XML Converters Inserting "... (2)
-> + Trying to use EDI to XSD docum... (5)
-- Previous [121-140] [141-160] [161-180] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Ronan HayesSubject: Recursively Mathcing up two XML Schemas?
Author: Ronan Hayes
Date: 14 Feb 2006 05:01 AM
I have 2 XML Schemas, one is from an older version while another is from a newer version of my application.

Basically the majority of the elements are the same, and instead of going through the 5000 nodes, and potentially missing 1 or 2 or worse yet mapping something to the wrong spot.

Is it possible just to map all elements with the same name, (and possibly under the same parent using stylus?)

Postnext
Minollo I.Subject: Recursively Mathcing up two XML Schemas?
Author: Minollo I.
Date: 14 Feb 2006 09:03 AM
If most of the structures match, then it's probably easier to build a mapper "by difference", by using <xsl:copy-of> for unchanged trees and by skipping/modifying elements that are gone/changed.

So, you could have something like (I'm typing without checking syntax, so forgive my errors)...
<xsl:template match="/">
<xsl:apply-templates/>
</xsl:template>

<xsl:template match="deletedElement1">
<!-- do nothing -->
</xsl:template>

<xsl:template match="renamedElement2">
<newElement2>
<xsl:for-each select="@*">
<xsl:attribute name="{name()}">
<xsl:value-of select="."/>
</xsl:attribute>
</xsl:for-each>
<xsl:apply-templates/>
</newElement2>
</xsl:template>

<xsl:template match="*"> <!-- normal case -->
<xsl:element name={name()}>
<xsl:for-each select="@*">
<xsl:attribute name="{name()}">
<xsl:value-of select="."/>
</xsl:attribute>
</xsl:for-each>
<xsl:apply-templates/>
</xsl:element>
</xsl:template>

Hope this helps,
Minollo

Postnext
Ronan HayesSubject: Recursively Mathcing up two XML Schemas?
Author: Ronan Hayes
Date: 14 Feb 2006 09:55 AM
Originally Posted: 14 Feb 2006 09:30 AM
Not 100% clear on whats going on there, but I wll take a closer read in a second.<br> <br> The problem with the approach above, is that I am not 100% as to what has been changed, hence why I was hoping for a recursive style <br> <br> eg: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:template match="/test"> <diff> <xsl:call-template name="compareNodes"> <xsl:with-param name="curNode" select="."/> <xsl:with-param name="ghostNode" select="document('comp2.xml')/test"/> <xsl:with-param name="repPath" select="'/test'"/> </xsl:call-template> </diff> </xsl:template> <xsl:template name="compareNodes"> <xsl:param name="curNode"/> <xsl:param name="ghostNode"/> <xsl:param name="repPath"/> <xsl:choose> <xsl:when test="*"> <xsl:for-each select="*"> <xsl:variable name="cname" select="name()"/> <xsl:choose> <xsl:when test="$ghostNode/*[name() = $cname]"> <xsl:call-template name="compareNodes"> <xsl:with-param name="curNode" select="."/> <xsl:with-param name="ghostNode" select="$ghostNode/*[name() = $cname]"/> <xsl:with-param name="repPath" select="concat($repPath, '/', $cname)"/> </xsl:call-template> </xsl:when> <xsl:otherwise> <missingPath><xsl:value-of select="concat($repPath, '/', $cname)"/></missingPath> </xsl:otherwise> </xsl:choose> </xsl:for-each> </xsl:when> </xsl:choose> </xsl:template> </xsl:stylesheet> Any ideas on how to adapt the copy-of to this similar style? <br> <br> Basically what I do know, is that each Schema has the same root, and potentially the same structure, just with varios elements being added or removed, depending on how the schemas have been updated. I want to remain generic and flexible, so that in 3 months time when the schema is changed again, that the application still functions correctly.

Postnext
Minollo I.Subject: Recursively Mathcing up two XML Schemas?
Author: Minollo I.
Date: 14 Feb 2006 09:37 AM
I'm sure you can come up with different solutions similar to what you have sketched out; but I have the feelings you are ending up simulating the pattern matching XSLT processing algorithm manually...

The approach I suggested earlier is indeed recursive; the <xsl:apply-templates/> instruction will make XSLT scan the children of the current node and apply the proper template based on the matching pattern.

Minollo

Postnext
Ronan HayesSubject: Recursively Mathcing up two XML Schemas?
Author: Ronan Hayes
Date: 14 Feb 2006 09:41 AM
Ok, sorry new to XSLT and trying to get my head around it

Postnext
Ronan HayesSubject: Recursively Mathcing up two XML Schemas?
Author: Ronan Hayes
Date: 14 Feb 2006 10:02 AM
You mention about using <xsl:copy-of> in your first post, yet your example doesnt use it??

Posttop
Minollo I.Subject: Recursively Mathcing up two XML Schemas?
Author: Minollo I.
Date: 14 Feb 2006 10:39 AM
You can use <xsl:copy-of> for those branches/sub-branches that you know need to be copied verbatim with no changes; so, if you know that your <order> element, for example, needs to be copies "as is", you could simply do:

<xsl:template match="order">
<xsl:copy-of select="."/>
</xsl:template>

That would simplify and speed up processing clearly.

Minollo

   
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.