[XML-DEV Mailing List Archive Home]
[Reply To This Message]
Re: Namespaces and overrides
- From: Michael Kay <email@example.com>
- To: firstname.lastname@example.org
- Date: Tue, 21 Dec 2010 15:00:38 +0000
XSD tries to do this with complex type restrictions, but I would
avoid that route if possible, partly because it involves restating
all the things that don't change, partly because you have to define
complex type resctrictions at every level of the XML hierarchy. I
would rely on XPath assertions to define additional constraints from
those in the base schema - expressed either using XSD 1.1, or
Schematron, or simply an XSLT stylesheet.
iCalendar is a very loose standard in which
nearly every component, and every element of those components,
is optional. As we revise, extend, “inherit” those components,
we often need to make certain of their elements mandatory for
some of these service interactions. What are the language /
descriptive formats, preferably machine readable, that you
would use to tighten specifications in this way as you adopt
them for specific re-use scenarios?
| [Thread Prev]
| [Thread Next]
| [Date Next]
| [Thread Index]
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
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