Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

darobin (1316)

darobin
  (email not shown publicly)
http://berjon.com/

Journal of darobin (1316)

Friday August 16, 2002
05:59 AM

Insanity

[ #7124 ]

As was made clear before, it has long been my opinion that XML Schema sucks.

I am now almost done putting together a complete schema for SVG Tiny (I already had all the types last week and then moved on to actually mapping them to something) plus large bits for SVG Basic and SVG, as well as other minor schemata for things such as XLink.

So now I hate them even more because I have a much sharper understanding of why they suck than I did before I had to make them go places no one thus far had dared to push them ;) On the other hand, I seem to be strangely enjoying having to fight with this painstackingly undocumented spec. So yeah, I guess those people that were mocking me for the fact that I enjoyed using the DOM may freely snicker now as I clearly am insane (but it's strongly typed insanity, ha!).

* darobin tries to remember who it was that once commented on a strong BDSM trend in the Perl community...

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • As was made clear before, it has long been my opinion that XML Schema sucks.
    What do you think of the alternatives to schema? I'm particularly thinking of RELAX-NG here.
    • RelaxNG is imho much better for several reasons: 1) it relies on a model (hedge automata) that while it may appear as complex to some is imho sane; 2) it is documented properly (ie you can understand the spec by reading it even if you are not interested in implementing it); 3) it splits typing out of the picture; 4) it's readable to humans and you usually know what you're doing and which rules you're breaking when writing RNG schemata (that's hardly the case with WXS); 5) RNG doesn't do weird things with

      --

      -- Robin Berjon [berjon.com]

      • 3) it splits typing out of the picture

        This is both a benefit and a drawback to RNG. I like how RNG solves one problem well, leaving a best-of-breed solution to develop for the nasty problem of datatyping.

        Unfortunately, the only reasonable solution for datatyping content is WXS Part 2, which is highly arbitrary in its selection of basic types. Is that sufficient for your needs (are you even doing datatyping of content?), or do you find a need for something better than WXS Part 2? (Assuming you coul

        • I'm not sure that WXSp2 is the only reasonable solution for datatyping :) I think you mean that it is the only one that is presently sufficiently spec'd/adpoted/understood/something-like-that (for various meanings of "sufficiently"), no?

          We do use datatyping, in fact we use it quite extensively. MPEG-7 DDL extends WXSp2 with a few types that it needs (such as multidimensional arrays) which shows quite clearly imho that WXSp2 would have been better written as a framework for type creation than as an

          --

          -- Robin Berjon [berjon.com]