[oslc-core] Need for a new specification phase/status: "deprecated"

[Steve K Speicher]

This was discussed at the Core WG meeting today [1] and there was 
consensus to add this.

[1] - http://open-services.net/bin/view/Main/OslcCoreMeetings20120418

Thanks,
Steve Speicher | IBM Rational Software | (919) 254-0645

> From: Steve K Speicher/Raleigh/IBM at IBMUS
> To: oslc-core at open-services.net, 
> Date: 04/10/2012 04:08 PM
> Subject: [oslc-core] Need for a new specification phase/status: 
"deprecated"
> Sent by: oslc-core-bounces at open-services.net
> 
> I'd like to introduce an addition to the Workgroup Best Practices 
document 
> [1] that provides an additional specification phase/status of 
> "deprecated".  The intent is to not leave certain specifications hanging 

> in some convergence or finalizing status forever.  We need to indicate 
> that the piece of work is not being further developed and implementation 

> expectations are set appropriately.
> 
> Proposal:
> "Deprecated: If there is a consensus within the workgroup that a 
> non-finalized Specification should no longer be developed and 
> implementations are not encouraged.  It is recommended that the 
workgroup 
> clearly mark this specification as such and indicate a possible way 
> forward, if one exists.  This can happen if the specification has not 
been 
> kept current with OSLC Core specification guidelines, then such a 
> Specification can left this state and not be further developed. Moving 
to 
> this state can happen from any phase in the Specification lifecycle"
> 
> I'd like to have feedback +/- on this proposal by April 18th (and 
discuss 
> if needed at the Core WG meeting).
> 
> [1] - 
> 
http://open-services.net/bin/view/Main/OslcWorkgroupPrinciplesandBestPractices

> 
> Thanks,
> Steve Speicher | IBM Rational Software | (919) 254-0645
> 
> 
> _______________________________________________
> Oslc-Core mailing list
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net
>