Lists Home |
Date Index |
- From: Derek Denny-Brown <email@example.com>
- To: "Rick Jelliffe" <firstname.lastname@example.org>, "Simon St.Laurent" <SimonStL@classic.msn.com>, "Xml-Dev (E-mail)" <email@example.com>
- Date: Wed, 26 Nov 1997 10:31:38 -0800
At 01:18 AM 11/27/97 +1100, Rick Jelliffe wrote:
>> From: Simon St.Laurent <SimonStL@classic.msn.com>
>> I gave a seminar
>> two weeks ago in Washington DC to the ACM ...
>> ... Every time I brought up
>> SGML (in connection with XML, CSS, and the DOM), I was greeted with
>> about "is that really necessary?" "Are those SGML people trying to change
>> _our_ world?" These questions didn't just come from the HTML beginners;
>> of them came from the developers who had worked with SGML, some quite
>> extensively. At lunch the discussion quickly turned to XML, and I had
to do a
>> lot of convincing to get people 'past' SGML.
>However, I do think that a lot of the antagonism against SGML is actually
>antagonism against the standard ISO 8879 (which is not intended to be
>entry-level or novice-friendly) mixed with antagonism against the early HTML
>DTDs (which were overly-complicated, IMHO, in structure for their
>as it turned out).
I would tend to disagree. I have talked to a number of people who are
antagonistic against SGML because the standard is so complicated. The fact
that it takes a book that large to really give an implementor enough
information to build a parser says something. As does the fact that SP is
roughtly 1Mb compiled. There are reasons for all of this, but people tend
to avoid things which take too long to understand, and react adversely when
they are forced to use something which they don't understand. Part of the
problem falls back to the tools, but if the initial standard had been more
directed to a specific audience, then the tools would have been easier.
Generality has its pros and cons. SGML was so general that it was
extremely complicated and only the determined could wade through the
initial waves of confusion. Thus there were very few people who
'understood' this SGML thing, so organizations trying to use SGML had to
get by with people who "didn't get SGML," and as a result had a horrid time
at it. Thus there are a number of people who think SGML is "a bad thing"
because 3/4 projects using it crashed and burned... (the preceeding figure
is purely random. I personnaly have watched a number of projects fail, but
I claim no knowledge of a general success/failure rate....)
This is not to say SGML is a bad thing. SGML is based on some extreemly
sound ideas, which are real driving requirements in a number of industries.
(otherwise SGML would have been dead a long time ago) XML (hopefully) is
the necessary compromises to get SGML used in more of the cases where it
can really provide benefit.
Derek E. Denny-Brown II || firstname.lastname@example.org
"Reality is that which, || Seattle, WA USA
when you stop believing in it, || WWW/SGML/HyTime/XML
doesn't go away." -- P. K. Dick || Java/Perl/Scheme/C/C++
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)