Descriptive markup Leading in this area is the SGML approach. It is argued that
authors should concentrate on the contents - and inherently on the structure - of their documents, leaving the details for formatting to the publisher. |
\input cfp.tex%Call for Papers format and macros %next copy proper The aim of this paper... Paper are solicited on ... \lstitm Picture editing \lstitm Text processing \lstitm Algorithms and software... Detailed abstracts should not ... Duration of presentation... \bye |
For this format the heading is always the same, so there is no need for a user to
provide it each time the format is used. It comes along with the format. So do the
fonts used and the shortcuts like \def\lstitm{\item{--} }
.
My approach looks simpler than Furuta's - in that paper all the low-level formatting details were present - because I applied the principle of the separation of concerns and abstracted from the low-level formatting details. The point I'd like to make is that it is possible to hide formatting details, to account for these separately and at a lower level. I like to call this approach generic, because the markup is customized at a lower level to the suited tool.