But "Suspended" implies it could possibly start again. As you say, deprecated implies something replaces it but we can make it clear what each usage means by providing some supporting description. I just hesitate to create a number of these "parked" spec statuses when one with some explanation may suffice.
Thanks, Steve Speicher | IBM Rational Software | (919) 254-0645 > From: Arthur Ryman <[email protected]> > To: John Arwe/Poughkeepsie/IBM@IBMUS, > Cc: [email protected], [email protected] > Date: 04/19/2012 04:31 PM > Subject: Re: [oslc-core] Need for a new specification phase/status: "deprecated" > Sent by: [email protected] > > There should be a "Suspended" state. Deprecated implies that something > newer replaced it. > > Regards, > ___________________________________________________________________________ > > Arthur Ryman > > DE, Chief Architect, Reporting & > Portfolio Strategy and Management > IBM Software, Rational > > Toronto Lab | +1-905-413-3077 (office) | +1-416-939-5063 (mobile) > > > > > > From: > John Arwe <[email protected]> > To: > [email protected] > Date: > 04/16/2012 08:15 AM > Subject: > Re: [oslc-core] Need for a new specification phase/status: "deprecated" > Sent by: > [email protected] > > > > from> then such a Specification can left this state > to> then such a Specification can be left this state > "Abandoned" might be a more accurate term *for the spec state*, but no > emotional attachment to the choice. > Best Regards, John > > Voice US 845-435-9470 BluePages > Tivoli OSLC Lead - Show me the Scenario > _______________________________________________ > Oslc-Core mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-core_open-services.net > > > > > _______________________________________________ > Oslc-Core mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-core_open-services.net >
