Re: RFC Suggest: Use of L<> to link RFCs; "CONFLICTS WITH", "REQUIRES", "STATUS" sections

>>>>> "JP" == John Porter <[email protected]> writes:

JP> The rules by which these policies would be specified could be arbitrarily
JP> complex; in particular, the L<> rule could specify alternative behavior
JP> when different output translators are in effect.

I don't think that the pod itself should specify _how_ the output
should look. Rather it should be giving some clues as to the nature of
the mark up. (=use RFC would specify (well I don't have a positive value)
that an L<> is not a man page.)

Another piece of input that would actully define the textual (or bit wise)
values of what markup is finally to look like.

<chaim>
-- 
Chaim Frenkel					     Nonlinear Knowledge, Inc.
[email protected]				               +1-718-236-0183