Regarding the resolution of this issue: http://open-services.net/bin/view/Main/OslcCoreV1Issues RESOLVED recommend renaming oslc:context to oslc:scope due to potential missunderstanding in ALM industry (RobertElves 03/30/2010) Response Done. We now use oslc:scope and describe it as "The scope of a resource is a link to the resource's ServiceProvider? ."
Since this property is a link to the ServiceProvider resource, why don't we just call it oslc:serviceProvider ? I think oslc:scope could still be misleading: change request is scoped to this iteration, etc. Robert, since you raised this issue what are your thoughts? Thanks, Steve Speicher | IBM Rational Software | (919) 254-0645
