From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!uio.no!nntp.uio.no!ifi.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: Alternative *ML syntaxes Date: 19 Nov 2002 00:01:02 +0000 Organization: Naggum Software, Oslo, Norway Lines: 34 Message-ID: <3246652862008190@naggum.no> References: <3DD20E0C.4@nyc.rr.com> <3246208885669993@naggum.no> <3246567106498053@naggum.no> <3246645143676184@naggum.no> <871y5i1ons.fsf@pokey.henrik-motakef.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: maud.ifi.uio.no 1037664063 19253 129.240.65.5 (19 Nov 2002 00:01:03 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 19 Nov 2002 00:01:03 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.lisp:47112 * Henrik Motakef | May I infer that you have a DTD parser lying around somewhere? Maybe | even a fully SGML-conformant one? In Common Lisp? Care to share? ;-) As sharing in any way could be construed as encouragement to use SGML or XML, I have to decline. | However, even if DTDs are still somehow priviledged in XML compared to | other schema languages (simply by being part of the XML 1.* spec), in | practice the only thing you really /need/ a DTD for are entity | declarations (and notations, but they aren't too useful in XML anyway). That the DTD is sort of "implied" by the application or the instance in no way negates it. Although some elements may have sub-element contents according to their own position in the hierarchy, which could be hard to express in a "standard" DTD, sender and receiver even of XML-encoded data need to agree on /something/. The situation may not actually be better than it was absent the stupid tags, but the only thing you have on an XML without a pre-agreed structure is attributes and sub-elements and data. | What do you do with XML applications that lack a DTD, most prominent | example being XSLT? Do you simply ignore them, or do you construct a DTD | from what you get? I try to ignore XSLT. Most of the time, document instances have enough information to construct useful content models and keep track of which things are attributes. It is not particularly hard. The biggest problem is in fact that some users actually need the retarded syntax. -- Erik Naggum, Oslo, Norway Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.