Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!ncrlnk!ncrstp!npdiss1!cape
From: cape@npdiss1.StPaul.NCR.COM (Robert Cape)
Newsgroups: comp.text.sgml
Subject: Writing SGML Applications
Keywords: lex, yacc, sobemap, parser
Message-ID: <767@npdiss1.StPaul.NCR.COM>
Date: 8 Dec 90 21:03:18 GMT
Reply-To: cape@ncrcis.StPaul.NCR.COM (Robert M. Cape)
Organization: NCR Network Products Division
Lines: 28

I've begun the task of writing an sgml application.  We have Sobemap's
(aka Yard) SGML parser.  In an appendix, they show a small sample sgml
application which uses lex and yacc to parse the canonical output from
their parser of an sgml instance.  The lex and yacc stuff is linked with
user code to perform the necessary transformations.

What I'd like to see is a discussion by others who are writing sgml
applications

 - What are people using for sgml parsers?
 - How are they creating their applications?
 - What design goals do people have in mind?
   - Portability across platforms?
   - Portability across OS's?
   = Speed?
   - Multiple passes?
 - Trade-offs between using lex (or flex) and yacc (or bison) and
   generalized translators? 
 - How do the various sgml parsers differ in their canonical output?
 - What are the implications?
 - Etc., etc.

Thanks,

Bob Cape

robert.cape@stpaul.ncr.com