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 » Generating XSLT to match a schema version change
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
+ Stylus Studio Technical Forum (14621)
+ Website Feedback (249)
- XSLT Help and Discussion (7625)
-> + Remove leading Zeros from a st... (4)
-> + how to parse a html element fo... (2)
-> + Add namespaces to target messa... (2)
-> + XSLT Transformation - insertin... (3)
-> + Convert binary xml (9)
-> + XSLT Transformation (4)
-> + Generating hyperlinks (3)
-> + XSLT to PDF problem (with JAVA... (2)
-> + how to add onclick_ with try/c... (2)
-> + Keep table in one page. xsl-fo... (4)
-> + Cannot find a matching 2-argum... (3)
-> + Creating one string from a sub... (2)
-> + XSLT: Traversing XML twice for... (6)
-> + Copy element without namespace... (5)
-> + Create dynamic elemant name (2)
-> + XSLT: Traversing XML twice for... (3)
-> + Problem including Javascript (2)
-> + Looping through attributes (4)
-> + Transform values into elements... (4)
-> + Problem with deep node copy an... (2)
-> + Comparing Dates With ASP.NET 2... (3)
-> + Converting tree structure to h... (4)
-> + Attributes to element transfor... (2)
-> + XSLT transformation (2)
-> + XSLT transformation (5)
-> + xsl:character-map not working (2)
-> + Removing duplicates entries. (2)
-> + Image issues. (2)
-> + xsl transformation (4)
-> + XSL Question (5)
-> + how to insert xml file as an n... (2)
-> + Document Function (2)
-> + convert seconds to hh:mm:ss (5)
-> + how to remove attribute while ... (3)
-> + XSL-FO question (2)
-> + EDI 997 creation. (7)
-> + Line break within a tag in XML... (2)
-> + Contact Help Needed (2)
-> + ACK 997 (2)
-> + XSLT to output XML( which conf... (11)
-> + Retrieving all nodes where a c... (6)
-> + Verifying XML and XSD within X... (4)
-> + How to validate date format in... (3)
-> + XSLT question (2)
-> + Muenchian grouping (2)
-> + How to remove specific text en... (8)
-> + If Else Condition along with L... (2)
-> + SAXON Problem (2)
-> + comapring global variable valu... (2)
-> + copying the value of xsl in va... (2)
-> + Urgent:XSLT element value sel... (2)
-> + Ignoring first element using f... (2)
-> + EDI X12 to XML (4)
-> + XSLT FOR-EACH HELP (2)
-> + Sorting Help Needed (3)
-> + XSLT help with linking (2)
-> + selecting data into node set b... (2)
-> + Watch and Variable in Debug no... (4)
-> + Transforming XML to XML - grou... (2)
-> + Saxon 9.0 B support in debug m... (2)
-> + Repeating element question (2)
-> + Newly Purchased Version Not La... (2)
-> + xsl:include not finding file (5)
-> + JAXP and XSLT 2.0 / XPATH 2.0 (2)
-> + ASP:DropDownList trigger in Xs... (2)
-> + Auto-Skip empty values (2)
-> + retrieving a javascript functi... (2)
-> + need help (2)
-> + html tag ignored (2)
-> + Quick reply needed (8)
-> + xslt to remove namespaces but ... (2)
-> - Using a WSDL definition in an ... (1)
-> + XSL logic issue for simple inp... (6)
-> + Regarding XML namespace prefix... (4)
-> + Mapper reoganizes itself. (8)
-> + XSL Substring Removal (2)
-> + Regarding XSLT logic for a sim... (3)
-> + XSLT Transform documentation (2)
-> + XSLT stack trace in case of er... (3)
-> + No New Line (2)
-> - No New Line (1)
-> + howto loop through a sequence (2)
-> + xml and xsl and whitespace in... (2)
-> + XSL Date formatting (4)
-> + XSL to XSL Mapping using custo... (4)
-> + flat xml to nested xml comvers... (4)
-> + Including schema in scenario (2)
-> + DTDs and traversing (2)
-> + Help with transformation (2)
-> + Problem running XSLT against X... (2)
-> + Carriage return in the output (5)
-> - Generating XSLT to match a sch... (3)
-> ->Generating XSLT to match ...
-> ->Generating XSLT to match ...
-> + WYSIWYG editor (2)
-> + Grouping without For-Each (3)
-> + output XML using XSLT (8)
-> + Help configuring Xalan-j proce... (8)
-> + Convert Existing HTML pages to... (2)
-> + Generating Transformation - XS... (4)
-> + DOCTYPE public and system info... (2)
-> + Using EXSLT str:tokenize funct... (5)
-- Previous [661-680] [681-700] [701-720] Next
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Matt WilsonSubject: Generating XSLT to match a schema version change
Author: Matt Wilson
Date: 23 Oct 2007 10:07 PM
NEMMCO has a schema (aseXML) which changes periodically to allow for new features. Not all users can change their systems at the same time as NEMMCO. Generating the XSL to convert XML files conforming to one version of the schema to another is easy in concept - but is a little harder when the schema definition is about 500Kb. Stylus Studio allows comparison of the schema files (.xsd) to show the differences, and can use the mapper to show the two schemas - but I cannot find an easy way to just identify the XSLT needed to transform the differences and just copy the rest.

For example, if all that changed from version 1 to version 2 is adding a new element (NewElement) then the templates needed to convert version 2 XML files back to version 1 are just:
<xsl:template match="NewElement"/><!-- just drop new element-->
<xsl:template match="@*|node()"><!-- identity transform -->
<xsl:copy>
<xsl:apply-templates select="@*|node()"/>
</xsl:copy>
</xsl:template>

For those that want the full schema, see www.nemmco.com.au/asexml and we want to be able to generate XSLT to go from latest release to any earlier release (e.g. r10). The question is: How to do it using Stylus Studio? (or any other tools?)
Postnext
(Deleted User) Subject: Generating XSLT to match a schema version change
Author: (Deleted User)
Date: 25 Oct 2007 08:00 AM
Hi Matt,
your problem doesn't have an easy solution; you can use Mapper to visually link all the elements from the latest schema to the previous release, but this can be a time-consuming operation, generating a complex stylesheet (as you would be building the final XML document, instead of using a "copy everything but XYZ" approach).
If you want to use the latter approach, you could write an XSL stylesheet that reads the two schemas and writes a new XSL stylesheet; it finds out the new element definitions and generates a template for each one to strip it from the source XML.

Hope this helps,
Alberto
Posttop
Matt WilsonSubject: Generating XSLT to match a schema version change
Author: Matt Wilson
Date: 25 Oct 2007 09:50 PM
Thanks Alberto. I had hoped that the general problem of managing schema versions might have had better support from the software product developers. My background is as a technical writer and I've been using XML occasionally since before it was a standard. This is the first time I've been asked to look at high-volume production data. I am disappointed with the supposedly leading products that they have not addressed such an obvious situation as the progressive change of a schema, albeit this one is large and complex.

If a business controls both the production and consumption of an XML data stream, ensuring compliance to change-over dates is just a matter of internal project management. If different businesses have each end, then the receiver is at the mercy of the sender - and there is not always enough resources to meet the deadline. I'd have thought this was a common business scenario, and I thought that XML was used extensively enough for inter-business data transfer, for such transition issues to have been widely experienced and general solutions developed.

Oh well. It looks like I manually do something quickly, then the XSL generator and maybe I'll have to see about creating the product - if nobody beats me to it!
   
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.