Suppose a directory src contains an object Main.java. In some SCM providers, the directory version object for a given version of src knows that Main.java is a member, but does not know which version of Main.java. The surrounding container - the configuration - knows which version of Main.java to use in that directory. In a different configuration, a different version of Main.java might be used in the same version of the src directory.
So, if all you know is a directory or directory version, you do not necessarily know which version to use for each member. However, you probably do know, or can find out, something about each possible member - perhaps the id of the version history in WebDAV terms. So the oslc_scm:memberIdentifier property is a way to access that knowledge. Hopefully it returns enough information so that you can see what was added or removed between two different versions of the same directory by comparing the memberIdentifier lists from those two different directory versions. For this type of provider, the member inheritance from ObjectVersion will only work if the containing configuration or baseline context is given. Nick. From: Paul Komar/Lexington/IBM To: Nick Crossley/Irvine/IBM@IBMUS Cc: [email protected] Date: 04/22/2010 10:34 AM Subject: Re: [oslc-scm] DirectoryVersion members 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
