On Thu, Jun 12, 2003 at 01:08:38PM -0400, Richard Naugle wrote: > At 01:05 AM 6/11/2003 -0800, Sean M. Burke wrote: > >At 07:56 AM 2003-06-10 -0400, Richard Naugle wrote: > >>[...]I agree with Doc::US_DOD[...] > > > >It just occurred to me to wonder... looking back at your original request > >for module list inclusion, you said: > > > >>[...] Placing Military::STD2167A in the module list [I think you meant > >>putting it in CPAN -- S.B.] will make this document electronically > >>available to all developers and users. The POD in the module allows > >>electronic distribution and access. Paragraphs may be cited from other > >>PODs by L<Military::STD2167A/xxxx> link. Easy electronic access provides > >>capabilities that are impossible with a hard copy. > > > >Why not just put them at some URL and have L<http://somehost/whatever#xxxx> > >links? > > Carrying this logic follow: > > All the Pod/*.pod should be moved to http://cpan.perl.org and all Perl > distributions that reference them changed to L<http://whatever> > > Active State should move their Docs/*.pod out of their distribution and put > it on a web site and reference them with L<http:://whatever>
In both those cases the docs are shipped with, and complement, actual code. And many of those docs do have L<http:://whatever#xxxx> links to further external documentation. I think there might be _some_ value in having STD2167A itself as a pod module on CPAN and in the module list. But it's a borderline case. I wouldn't want that to lead to a flood, as it seems to have done. Tim.
