I certainly don't find RELAX NG instantly readable, although I'm sure it is once you get to know it. However, W3C XML Schema does have tools, and good tools, and don't find it significantly harder to write than anything else, not once you've learnt the few basics you need to get started. It makes some sense for marked-up human-readable text, but no great sense, to me at least, for data-oriented applications, where it's just another avenue for developers to make errors.Īs for being hard to write, I have to be honest that I learnt how to write W3C XML Schema initially by using TurboXML and seeing what it wrote. RELAX NG would let me to change the content of an element based on its attribute values, but I would never do that to my users. I need Schematron or a code layer to do that, so RELAX NG wins me nothing there. There are things that I can't validate with W3C XML Schema, but I can't validate those with RELAX NG either. Now, I work on the "data" side of things, and if I worked more on the "document" side of things (and those distinctions aren't hard, but they are real enough) I would probably be looking at RELAX NG. W3C XML Schema does a good enough job for almost everything do. Actually, I'm happy to write here and now that I don't use RELAX NG professionally, nor do I want to. Obasanjo, and now the comments have some push-back too.įrom: Anthony B. The time has come to declare it a worthy but failedĮxperiment, tear down the shaky towers with XSD in their foundation,Īnd start using RELAX for all significant XML work. So now lots of people say “Well, yeah, it sucks, but we’re stuck with it.” Wrong! Same as XML, it must be the way to go, and it got baked into aīunch of other technology before anyone really had a chance to think it over. It’s a pity when XSD came out people thought that since it came from the W3C, Pretty soon now, the Atom Publishing Protocol. XML applications that are RELAX-based, I’d add the Schemas based on Relax NG,Īlso known as ISO Standard 19757, are easy to write, easy to read, are backedīy a rigorous formalism for interoperability, and can describe immensely moreĭifferent XML constructs. Lots of things you want to do all the time in XML. Hard to understand, have interoperability problems, and are unable to describe Has known the truth for years, and it’s time to stop sweeping it under Everybody who actually touches the technology
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |