Olivier Berger <[email protected]> wrote on 04/02/2010 03:57:52 AM: > Le lundi 29 mars 2010 à 09:56 -0400, Steve K Speicher a écrit : > > "Wolf, Timo" <[email protected]> wrote on 03/29/2010 08:11:13 AM: > > > > > > When saving a link in RTC, RTC tries to store a back link to the > > > Provider side, using the property > > "oslc_cm:relatedChangeManagement" . > > > > > > I actually figured out what is going on and implemented the Provider > > > part, but I did not find anything about > > > oslc_cm:relatedChangeManagement in the OSLC spec. > > > Is this missing or can you give me a link to the related spec in V1 > > or V2? > > > > > > > This property 'oslc_cm:relatedChangeManagement' is a proprietary > > extension added by the RTC 2.0 product (not part of OSLC-CM V1). You > > may inquiry on a http://jazz.netforum for details on it. > > > > We are looking at providing this property in a V2 specification, > > looking to complete this work soon: > > http://open-services.net/bin/view/Main/CmResourceDefinitionsV2 > > So shouldn't RTC use a custom prefix for such a proprietary extension ?
The recommendation is to add custom properties in a non-OSLC namespace. > Should there be some versioning also in such prefixes to distinguish > between V1, V2, etc ? We are working on our versions on the V2 ChangeRequest definition now. But would expect the namespaces to evolve to include increased version strings. Thanks, Steve Speicher | IBM Rational Software | (919) 254-0645
