OK. Since writing my initial question, it has occurred to me that clients can get the members as resources via the Directory Version's inheritance from Object Version.
I'm not sure that I understand the purpose of the memberIdentifier property. Can you please explain it? Is it a quick way of determining the changes between directory versions? -- Paul Komar Jazz/RTC SCM Developer Rational Software IBM Software Group Littleton, MA From: Nick Crossley/Irvine/IBM@IBMUS To: [email protected] Date: 04/22/2010 03:41 AM Subject: Re: [oslc-scm] DirectoryVersion members Sent by: [email protected] A directory version might be found outside of any context in a number of ways: As one of the object versions associated with a change set, where that change set does not by itself confer any context As part of the result of a query As a link from some other service provider (perhaps a new directory version became associated with a requirement, or a test case) From a URL manually entered by the user, perhaps with some knowledge or guesses about the URL structure used by some provider Nick. From: Paul Komar/Lexington/IBM@IBMUS To: [email protected] Date: 04/21/2010 02:03 PM Subject: [oslc-scm] DirectoryVersion members Sent by: [email protected] Given that in the V1.0 specification, a DirectoryVersion is always referred to in the context of a configuration, why can't the members be Resources? -- Paul Komar Jazz/RTC SCM Developer Rational Software IBM Software Group Littleton, MA_______________________________________________ Oslc-Scm mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-scm_open-services.net. _______________________________________________ Oslc-Scm mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-scm_open-services.net
