4 ms·
In the excellent Dr. Dobb's Journal interview "A Triumph of Simplicity: James Clark on Markup Languages and XML" [1], they ask him: DDJ: You're well known for
by DonHopkins 10y ago
In the excellent Dr. Dobb's Journal interview "A Triumph of Simplicity: James Clark on Markup Languages and XML" [1], they ask him:
DDJ: You're well known for writing very good reference implementations for SGML and XML Standards. How important is it for these reference implementations to be good implementations as opposed to just something that works?
JC: Having a reference implementation that's too good can actually be a negative in some ways.
DDJ: Why is that?
JC: Well, because it discourages other people from implementing it. If you've got a standard, and you have only one real implementation, then you might as well not have bothered having a standard. You could have just defined the language by its implementation. The point of standards is that you can have multiple implementations, and they can all interoperate.
You want to make the standard sufficiently easy to implement so that it's not so much work to do an implementation that people are discouraged by the presence of a good reference implementation from doing their own implementation.
DDJ: Is that necessarily a bad thing? If you have a single implementation that's good enough so that other people don't feel like they have to write another implementation, don't you achieve what you want with a standard in that all implementations — in this case, there's only one of them — work the same?
JC: For any standard that's really useful, there are different kinds of usage scenarios and different classes of users, and you can't have one implementation that fits all. Take SGML, for example. Sometimes you want a really heavy-weight implementation that does validation and provides lots of information about a document. Sometimes you'd like a much lighter weight implementation that just runs as fast as possible, doesn't validate, and doesn't provide much information about a document apart from elements and attributes and data. But because it's so much work to write an SGML parser, you end up having one SGML parser that supports everything needed for a huge variety of applications, which makes it a lot more complicated. It would be much nicer if you had one SGML parser that is perfect for this application, and another SGML parser that is perfect for this other application. To make that possible, the standard has to be sufficiently simple that it makes sense to have multiple implementations.
[1] http://www.drdobbs.com/a-triumph-of-simplicity-james-clark-on-m/184404686 http://www.drdobbs.com/a-triumph-of-simplicity-james-clark-o...
- tannhaeuser 10y agoHey, thanks for the link; I didn't know it, believing I knew all SGML resources. (I'm the fool having actually implemented SGML -- no less -- in Javascript).
- DonHopkins 10y agoJames Clark [1] has written some amazing stuff [2] [3]! The story behind the design [4] of Relax/NG [5] [6] is fascinating and triumphant (thanks to simplicity). That July 2001 interview is apparently from before he merged his work on TREX [7] with Makoto Murata's [8] work on RELAX [9], working together on the OASIS RELAX NG technical committee [10]. Wikipedia: Makoto Murata: RELAX and RELAX NG [9] Some people, including Murata and James Clark, had critical attitudes toward XML Schema. XML Schema is a modern XML schema language designed by W3C XML Schema Working Group. W3C intended XML Schema to supersede traditional DTD (Document Type Definition). XML Schema supports so many features that its specification is large and complex. Murata, James Clark and those who criticised XML Schema, pointed out the following: It is difficult to implement all features of XML Schema. It is difficult for engineers to read and write XML Schema definitions. It does not permit nondeterministic content models. Murata and collaborators designed another modern schema language, RELAX (Regular Language description for XML), more simple and mathematically consistent. They published RELAX specification in 2000. RELAX was approved as JIS and ISO/IEC standards. At roughly the same time, James Clark also designed another schema language, TREX (Tree Regular Expressions for XML). Murata and James Clark designed a new schema language RELAX NG based on TREX and RELAX Core. RELAX NG syntax is the expansion of TREX. RELAX NG was approved by OASIS in December 2001. RELAX NG was also approved as Part 2 of ISO/IEC 19757: Document Schema Definition Languages (DSDL). [1] https://en.wikipedia.org/wiki/James_Clark_(programmer) https://en.wikipedia.org/wiki/James_Clark_(programmer) [2] http://www.jclark.com/ http://www.jclark.com/ [3] http://www.jclark.com/xml/ http://www.jclark.com/xml/ [4] http://www.thaiopensource.com/relaxng/design.html http://www.thaiopensource.com/relaxng/design.html [5] http://relaxng.org/ http://relaxng.org/ [6] http://www.thaiopensource.com/relaxng/ http://www.thaiopensource.com/relaxng/ [7] http://www.thaiopensource.com/trex/ http://www.thaiopensource.com/trex/ [8] https://en.wikipedia.org/wiki/Makoto_Murata#RELAX_and_RELAX_NG https://en.wikipedia.org/wiki/Makoto_Murata#RELAX_and_RELAX_... [9] https://en.wikipedia.org/wiki/Makoto_Murata https://en.wikipedia.org/wiki/Makoto_Murata [10] https://www.oasis-open.org/committees/relax-ng/ https://www.oasis-open.org/committees/relax-ng/
- deleted 10y ago[deleted]