FW: [xml-dev] Namespaces and overrides

"If something is not worth doing, it`s not worth doing well" - Peter DruckerToby Considine
TC9, IncTC Chair: oBIX & WS-CalendarTC Editor: EMIX, EnergyInteropU.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee

  Email: 
Phone: (919)619-2104http://www.tcnine.com/
blog: www.NewDaedalus.comFrom: Michael Kay [mailto:]
Sent: Tuesday, December 21, 2010 10:01 AM
To: 
Subject: Re: [xml-dev] Namespaces and overrides

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?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.

Michael Kay
Saxonica