Re: [webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377)

So far, I do not feel any trouble by using the term of "deep" in the Shadow DOM spec.

When I have to consider a closed shadow tree, I am using "unclosed node" or "unclosed tree" in defining the behavior of a closed tree. That seems successful, so far. I do not have any trouble.

"composed" might be confusing because the Shadow DOM spec has a well defined concept of "composed tree". "*in a document deeply*" and "*in a composed tree*" are different concept.

But, I am fine with using *composed* here because it sounds more intuitive, I think.

Thus, the candidates would be:

1. *in a composed document*

    It might be confusing, due to the existing concept of *composed tree*. We might want to rename *composed tree* to something else, e.g. *flattened tree*, if we use "in a composed document".

2. *in a document deeply*.
3. *connected to a document*



---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/377#issuecomment-179204289