Seconded, thirded, whatever.
The US_DOD::* submissions must not be accepted.
The only use for documents and standards I can see when the document
contains some sort of structured data that can be programmatically
used, like for example the ISO 3166 country codes by Locale::Country.
There is a map
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 m
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 li
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.]
At 02:39 PM 6/6/2003 +0100, Tim Bunce wrote:
On Thu, Jun 05, 2003 at 07:18:21PM -0700, William R Ward wrote:
> Kurt Starsinic writes:
> >On Jun 05, Sean M. Burke wrote:
> >> At 06:20 PM 2003-06-05 -0700, William R Ward wrote:
> >> >I really hope the admins don't accept this new US_DOD:: top-level
>
I don't think any of these belong in the Module List. The main standard
was reasonable to include, just, maybe. But these others are not worth it.
Note that having a Module List entry is totally unrelated to L<...> working
in pod. And as someone else said recently (sorry, forgot who and can't find
These should not be here. If they're directly perl related, but only
docs, they should be in something like Docs::US::DOD::*, but as they're
not directly Perl related (and I assume available elsewhere on the net)
they should not be included in CPAN.
If they are included, please do not allow the
The following module was proposed for inclusion in the Module List:
modid: US_DOD::VDD
DSLIP: inpnn
description: Version Description Document (VDD) DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
The following module was proposed for inclusion in the Module List:
modid: US_DOD::SSDD
DSLIP: inpnn
description: System/Segment Design Document (SSDD) DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
simil
The following module was proposed for inclusion in the Module List:
modid: US_DOD::SRR
DSLIP: inpnn
description: System Requirements Review (SRR) DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
The following module was proposed for inclusion in the Module List:
modid: US_DOD::SPM
DSLIP: inpnn
description: Software Development Plan (SDP) DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
The following module was proposed for inclusion in the Module List:
modid: US_DOD::SDR
DSLIP: inpnn
description: System Design Review (SDR) DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
US_D
The following module was proposed for inclusion in the Module List:
modid: US_DOD::SCN
DSLIP: inpnn
description: Specification Change Notice (SCN)
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
U
The following module was proposed for inclusion in the Module List:
modid: US_DOD::IDD
DSLIP: inpnn
description: Interface Design Document (IDD) DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
The following module was proposed for inclusion in the Module List:
modid: US_DOD::HWCI
DSLIP: inpnn
description: Hardware Configuration Item (HWCI) DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
The following module was proposed for inclusion in the Module List:
modid: US_DOD::ECP
DSLIP: inpnn
description: Engineering Change Proposal (ECP)
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
U
The following module was proposed for inclusion in the Module List:
modid: US_DOD::CSCI
DSLIP: inpnn
description: Computer Software Configuration Item (CSCI)
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
sim
The following module was proposed for inclusion in the Module List:
modid: US_DOD::CRDL
DSLIP: inpnp
description: Computer Resources Integrated Support CRISD
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
sim
The following module was proposed for inclusion in the Module List:
modid: US_DOD::CRDL
DSLIP: inpnn
description: Contract Data Requirements List (CDRL) DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
simi
At 02:39 PM 2003-06-06 +0100, Tim Bunce wrote:
I think the key point was the ability to be able to refer to them
as links using pod L<...> clauses.
Hm. The voices in my head just asked me an interesting question: Why not
just use L links? I mean, I do realize that Pod::* is a bit
tatty and wil
Kurt Starsinic writes:
>On Jun 05, Sean M. Burke wrote:
>> At 06:20 PM 2003-06-05 -0700, William R Ward wrote:
>> >I really hope the admins don't accept this new US_DOD:: top-level
>> >domain. I think it should go under the Doc::US_DOD:: hierarchy. There is
>> >no Doc:: top-level hierarchy curre
On Jun 05, Sean M. Burke wrote:
> At 06:20 PM 2003-06-05 -0700, William R Ward wrote:
> >I really hope the admins don't accept this new US_DOD:: top-level
> >domain. I think it should go under the Doc::US_DOD:: hierarchy. There is
> >no Doc:: top-level hierarchy currently that I can find, so mak
At 06:20 PM 2003-06-05 -0700, William R Ward wrote:
I really hope the admins don't accept this new US_DOD:: top-level
domain. I think it should go under the Doc::US_DOD:: hierarchy. There is
no Doc:: top-level hierarchy currently that I can find, so making a new
place for all modules that are s
I really hope the admins don't accept this new US_DOD:: top-level
domain. I think it should go under the Doc::US_DOD:: hierarchy.
There is no Doc:: top-level hierarchy currently that I can find, so
making a new place for all modules that are solely documentation seems
like a better idea than maki
The following module was proposed for inclusion in the Module List:
modid: US_DOD::STD490A
DSLIP: Rdpnp
description: Specification Practices
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
US_DOD:
The following module was proposed for inclusion in the Module List:
modid: US_DOD::SVD
DSLIP: Rdpnb
description: Software Version Description DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
US
The following module was proposed for inclusion in the Module List:
modid: US_DOD::SUM
DSLIP: Rdpnb
description: Software User Manual DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
US_DOD::ST
The following module was proposed for inclusion in the Module List:
modid: US_DOD::STrP
DSLIP: Rdpnb
description: Software Transition Plan
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
US_DOD::S
The following module was proposed for inclusion in the Module List:
modid: US_DOD::STR
DSLIP: Rdpnp
description: Software Test Report DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
US_DOD::ST
The following module was proposed for inclusion in the Module List:
modid: US_DOD::STP
DSLIP: Rdpnp
description: Software Test Plan DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
US_DOD::STD2
The following module was proposed for inclusion in the Module List:
modid: US_DOD::STD
DSLIP: Rdpnp
description: Software Test Description DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
US_DO
The following module was proposed for inclusion in the Module List:
modid: US_DOD::STD
DSLIP: Rdpnp
description: Software Test Description DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
US_DO
The following module was proposed for inclusion in the Module List:
modid: US_DOD::SSS
DSLIP: Rdpnb
description: System/Subsystem Specification
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
US_D
The following module was proposed for inclusion in the Module List:
modid: US_DOD::SRS
DSLIP: Rdpnb
description: Software Requirements Specification DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
The following module was proposed for inclusion in the Module List:
modid: US_DOD::SPS
DSLIP: Rdpnb
description: Software Product Specification DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
The following module was proposed for inclusion in the Module List:
modid: US_DOD::SIP
DSLIP: Rdpnb
description: Software Installation Plan
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
US_DOD::
The following module was proposed for inclusion in the Module List:
modid: US_DOD::SIOM
DSLIP: Rdpnb
description: Software Input/Output Manual DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
U
The following module was proposed for inclusion in the Module List:
modid: US_DOD::SDP
DSLIP: Rdpnb
description: Software Development Plan DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
US_DO
The following module was proposed for inclusion in the Module List:
modid: US_DOD::SDD
DSLIP: Rdpnb
description: Software Design Description
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
US_DOD:
The following module was proposed for inclusion in the Module List:
modid: US_DOD::OCD
DSLIP: Rdpnb
description: Operational Concept Description DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
The following module was proposed for inclusion in the Module List:
modid: US_DOD::IRS
DSLIP: Rdpnb
description: Interface Requirements Specification DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar
The following module was proposed for inclusion in the Module List:
modid: US_DOD::FSM
DSLIP: Rdpnb
description: Firmware Support Manual DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
None
similar:
US_DOD:
The following module was proposed for inclusion in the Module List:
modid: US_DOD::DBDD
DSLIP: Rdpnp
description: Database Design Description DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
DIDs are something that
The following module was proposed for inclusion in the Module List:
modid: US_DOD::CPM
DSLIP: Rdpnb
description: COMPUTER PROGRAMMING MANUAL DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
Who in their right mind
The following module was proposed for inclusion in the Module List:
modid: US_DOD::COM
DSLIP: Rdpnb
description: Computer Operation Manual DID
userid: SOFTDIA (Samson Monaco Tutankhamen)
chapterid:3 (Development_Support)
communities:
none
similar:
US_DO
On Thu, Jun 05, 2003 at 07:18:21PM -0700, William R Ward wrote:
> Kurt Starsinic writes:
> >On Jun 05, Sean M. Burke wrote:
> >> At 06:20 PM 2003-06-05 -0700, William R Ward wrote:
> >> >I really hope the admins don't accept this new US_DOD:: top-level
> >> >domain. I think it should go under the
46 matches
Mail list logo
