XSD could make me very happy

You can tell from my recent posts that I have a mixed relationship with XSD. Yesterday's post explained my approach to XSD design, which grew out of my investigation of RNG, and which I'm pretty happy with. (I've been criticizin XSD a lot lately, but I have to give it credit for supporting a wide range of alternative approaches, including the one the I like). The one big issue that remains for me is versioning, which I've mentioned before. Noah Mendelsohn posted this message to the W3C TAG about potential changes to XSD to facilitate versioning by altering the unique particle attribution rule so that wildcards are weaker than element declarations, which take precedence. This would be a huge step and is exactly what I want. He goes further, adding the notion of declaring a default implicit extensibility model that injects wildcards at the end of or in between each particle in a complex content model. That would be a very cool feature too. If you are interested in the XSD versioning problem, read his email. For me, this change can't come fast enough, at the W3C and in System.Xml. Given this and the XSD style I talked about yesterday, I would probably give up on RNG (which isn't that hard, since people don't think it'll happen ;-).


Posted Aug 25 2004, 09:08 AM by tim-ewald

Comments

Dare Obasanjo wrote re: XSD could make me very happy
on 08-25-2004 7:59 AM
>For me, this change can't come fast enough, at the W3C and in System.Xml.

Don't hold your breath.
Tim wrote re: XSD could make me very happy
on 08-25-2004 8:35 AM
Yeah, I know. But I can dream can't I?

Tim-
The XML Files wrote XSD Can Make Us Happy
on 08-25-2004 11:45 AM
The XML Files wrote XSD Can Make Us Happy
on 08-25-2004 11:45 AM
The XML Files wrote When something is
on 08-27-2004 9:45 AM
The XML Files wrote When something is
on 08-27-2004 9:48 AM
XML Eye for the Object Guy wrote XSD 1.0 2nd Edition
on 10-20-2004 2:24 PM
Noah Mendelsohn wrote re: XSD could make me very happy
on 11-11-2004 11:34 AM
Thanks for the encouragement, and also to those who've posted interesting followup comments. The schema WG is indeed actively discussing these proposals among others.

Tim: I'm curious, do you share my feeling that to make this practical in many scenarios we'd also need a new form of wildcard along the lines of: "anything not explicitly declared in this schema"? In other words, if I already knew about it, I would have referenced explicitly in the content model; this wildcard is only for stuff I've never heard of before. Presumably this would be intersected with namespace constraints on the same wildcard. Make sense?

Add a Comment

(required)  
(optional)
(required)  
Remember Me?