Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


schema arrangement or architecture

From: "Andrew Welch" <andrew.j.welch@-----.--->
To: xmlschema-dev@--.---
Date: 6/2/2008 4:16:00 PM
Hi,

Given the "salami slice" style of schema (all elements and types are
global) are there any established practices for arranging a large
schema? eg

- try to keep to one large file or break it down into several files?
- ensure all element definitions are always in a single file, or where
possible keep element definitions in the same file as their type
definitions?
- should all attribute be defined globally?

etc.

There seems to be quite a lot of information about the different
schema styles out there, but not much on managing a large schema...
(in this case I'm calling a "large" schema one with just over 100
different elements each with their own type... ~150 attributes)

Is the secret of maintaining a large schema down to good tooling
rather than an intimate knowledge of what's in each file?

thanks
-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

From tuquenukem@h... Tue Jun 03 03:20:56 2008
Received: from mag


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent