Lists Home |
Date Index |
10/8/2002 11:28:14 AM, Sam Hunting <firstname.lastname@example.org> wrote:
> I remember writing a DTD several years ago that
>implemented the Bluebook standard for legal citations using
>SHORTREF. Since it was SGML, no "custom code" was required to handle it,
>and if you wanted SGML angle brackets, you used sgmlnorm. (This could be
>viewed as a recognition that whitespace and punctujation were the first
>forms of markup.)
>It should be stressed that such a document was in fact 100% valid
>SGML, even though it looked like (and was) also a little language. It
>didn't need to be transformed into order to be valid, that is.
I meant "transformation" loosely enough to cover what you're talking about :-)
So, I think you answered my question: One can write an SGML DTD using
SHORTREFs that defines a "little language", and use the sp tools to
"transform" it into something an XML parser might handle.
Next question -- what arguments might one offer to someone who would
prefer to whip up a yacc grammar or some Perl/Python regexp code (c.f.
the one-line Python parser for RSS 3.0) rather than use SGML to define
the little language?