Feature name for DOM Overlay, and best practice for related attributes

We briefly discussed this in the last CG call, see minutes at
https://www.w3.org/2019/11/26-immersive-web-minutes.html#item03 and the
related issue https://github.com/immersive-web/dom-overlays/issues/6.

As requested in the call, does anyone have objections to using the feature
name "dom-overlay" for this feature?

We don't seem to have much precedent for how feature names should relate to
methods or attributes added to pre-existing entities such as XRSessionInit.
To avoid potential collisions with other future features, I've been using
the feature name as a prefix in the draft spec
<https://klausw.github.io/dom-overlays/index.html>, i.e.
{{XRSessionInit/domOverlay}} for the new initialization attribute, and
{{XRSession/domOverlayState}} for current properties. Are people OK with
using this approach for other features also, where appropriate?