[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Numbering of Proposals
Simple point-based subclassing works for me: 12047.a 12047.b 12047.c or even a descriptive tag: 12047.mapref_core 12047.name_of_one_issue 12047.name_of_other_issue I don't see why either of these would not work fine for our current process. I don't anticipate any sorting based on number, but at least if we keep the base number, we know something of the heritage of the spinoffs. Regards, -- Don Day Chair, OASIS DITA Technical Committee IBM Lead DITA Architect Email: dond@us.ibm.com 11501 Burnet Rd. MS9033E015, Austin TX 78758 Phone: +1 512-838-8550 T/L: 678-8550 "Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?" --T.S. Eliot "Eliot Kimber" <ekimber@innodata -isogen.com> To "DITA TC list" 05/31/2007 10:25 <dita@lists.oasis-open.org> AM cc Subject [dita] Numbering of Proposals I'm working on writing up proposals for some of the issues for which I am champion of record. How should I number proposals? For example, issue 12047 (add mapref, etc. to mapgroup) should really be broken out into at least three separate proposals. How should I number them? Thanks, E. -- W. Eliot Kimber Professional Services Innodata Isogen 8500 N. Mopac, Suite 402 Austin, TX 78759 (214) 954-5198 ekimber@innodata-isogen.com www.innodata-isogen.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]