• To: "Bullard, Claude L (Len)" <clbullar@i...>
• Subject: Re: Best Practice - beyond schema
• From: Francis Norton <francis@r...>
• Date: Mon, 17 Jun 2002 17:13:34 +0100
• Cc: 'Paul Spencer' <paul@a...>, Xml-Dev <xml-dev@l...>, "Roger L. Costello" <costello@m...>
• References: <2C61CCE8A870D211A523080009B94E430752B582@HQ5>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530

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

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

• Follow-Ups:
  • Re: Best Practice - beyond schema
    • From: "Rick Jelliffe" <ricko@a...>

• References:
  • RE: Best Practice - beyond schema
    • From: "Bullard, Claude L (Len)" <clbullar@i...>

• Prev by Date: RE: Best Practice - beyond schema
• Next by Date: Re: Illegal Characters in Namespace URIs
• Previous by thread: RE: Best Practice - beyond schema
• Next by thread: Re: Best Practice - beyond schema
• Index(es):
  • Date
  • Thread