Scott Babcock

@titusfortner The check for `platformVersion` is performed in the existing **DefaultSlotMatcher** [implementation](https://github.com/SeleniumHQ/selenium/blob/trunk/java/src/org/openqa/selenium/grid/data/DefaultSlotMatcher.java#L135-L150). This isn't a new feature being proposed in this RFC, but it may have been added for the...

Regarding the handling of `platformName`, each step is able to evaluate the entire set of defined capabilities. Filtering reduces the number of capabilities that must be evaluated on each step...

@VietND96 The `platformVersion` capability should be treated as an "identity" value, which means that it must be declared as `appium:platformVersion` under the specifications defined by this RFC. There would be...

The extension capability `appium:platformVersion` is totally W3C compliant. This value cannot be specified without its `appium:` prefix. Since this capability will be treated as an "identity" value, it will be...

@VietND96 **Appium** _works_ with **Grid** though **Relay**, but the way we've implemented extension capability support is inconsistent and inflexible. My [local-grid-parent](https://github.com/sbabcoc/local-grid-parent) project is able to stand up Grid instances that...

@titusfortner As currently implemented, all extension capabilities with "special" prefixes are ignored for slot matching (configuration options), while all other extension capabilities are considered for slot matching ("identity" values). This...

The merge operation enables the relay to define common configuration options (e.g. - BrowserStack access tokens) so the client doesn't need to specify these, or even know that they exist....

@diemol **Appium** and **Safari** both define "identity" values that **should** be considered for slot matching and configuration options that **should not** be considered for slot matching. In the **Appium** case,...

@diemol The core issue with custom matchers is that each hub can only specify one matcher. There's no mechanism to extend the default matcher; it can only be replaced. This...

@diemol The current mechanism forces arbitrary separations between hubs that support sessions from different vendors. Each vendor that requires matching behavior that deviates from "default" must be vended by a...