A software version rule-based pattern matching mechanism specifies version compatibility of a particular remote component by identifying a set of compatible versions operable with a particular server, and comparing the versions to determine compatibility of a purported revision component with an existing server (central component). The mechanism employs a rule based syntax for defining a set of compatible versions associated with a candidate component, and processes a version specifier, or range string mask, indicative of the set of compatible versions. The target version, such as the candidate component version, is then compared with each of the compatible versions indicated by the version string mask. If a matching compatible version is found, then the corresponding component (module) is deemed compatible.