F.2.3 Decisions from 1999 October meeting, RAL

This is the subset of decisions from that meeting which refer to the DTD specifically.

The "publicity" level of a prologue should be indicated by the number of + and - signs at the beginning and end as follows: `*+' = private `*++' = protected (i.e. for internal docs) `*+++' = public (i.e. for external docs)

Not done yet, but half-hour's work for me, probably less for Mark.

"givenandreturned" should become two separate attributes "given" and "returned", defaulting to "given" if neither are specified.

Done.

"othernote" should be renamed "diytopic" We need to be able to include "diytopics" anywhere in the prologue, not just within a "notelist". This will probably mean doing away with "notelists".

Done. It's not particluarly pretty, but it's done.

We need to be able to classify prologues using keywords. This requires a "keywordlist" element in the codeprologue DTD. One or zero of these should be allowed in each prologue, and they should provide two name spaces (e.g. using "keyword" elements for public keywords, and "group" elements for private keywords).

Done. See Appendix D.1.63 and Appendix D.1.75 elements.

The design for obsolete IDs in release 0.3 was accepted.

Implemented. See Appendix C.1.45.

Including graphics files in-line in the main document is not needed.

OK - although not terribly useful, it's reasonably easy in fact, and if you include MetaPost source as a graphics format, it's implemented!

Foreign words to be introduced using the foreign tag. Non-"full stop" dot to be "."

Done. See Appendix C.1.34 element.

"docxref" should not generate any "magic" text, and they should be allowed in code prologues.

Further discussed at March 2000 Cambridge meeting.