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

Re: Best Practice - beyond schema

Re:  Best Practice - beyond schema
Hi Len,

Bullard, Claude L (Len) wrote:

>An alternative is to move the local definition to a transformation 
>document, eg, XSLT over the XML Schema.   The technical 
>advantage here is to have the modifications in a single 
>automated document including any value constraint controls 
>which presumably will be local  The XML Schema is one and the authority 
>is centralized.  The XSLT modifier is one and is owned by the 
>local authority.  
I have written a utility to include or exclude xsd elements for / from a specific project, using embedded appinfo markup and an XSLT transform that takes the project name as a commandline parameter.

I'll pop it up on a site if anyone thinks it might be interesting

"Never mind manoeuvre, go straight at 'em." - Admiral Horatio Nelson


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.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.

Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

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.