ISSUE-227: Terminology issues [wsc-xit]

ISSUE-227: Terminology issues [wsc-xit]

http://www.w3.org/2006/WSC/track/issues/227

Raised by: Thomas Roessler
On product: wsc-xit

Terminology issues raised in recent last call comments:

LC-2256:

"user agent" -- The draft uses the term "user agent" for conformance  
levels and uses the term "web user agent" elsewhere. For the kind of  
requirements the draft makes most other specifications simply use "user  
agent". It would be nice if the draft could align with that. In case the  
deviation is found necessary for some reason it should be consistently  
used. In section 7.4 the term "browser" is also sometimes used. Is that  
intentional?

"web page" -- The definition of Web page seems to include that it cannot  
be embedded so I wonder what "top-level Web page" in section 4 means. If  
this document is indeed aimed at browser vendors (and it sure seems like  
it) it might be good to align terminology with HTML5. For what you want  
here the term "top-level browsing context" would be appropriate. Unlike  
"web page" that term is also defined in a lot more detail so that there  
can be no doubt as to what is meant.

"chrome" -- technically scrollbars and such are also part of this, but  
should probably be excluded for most purposes here since positioning  
something over an element with a scrollbar is fine.

LC-2257:

The term "chrome" seems undefined, in the document it seems to be implicitly equivalent to the user interface.
FYI: The View Modes specification [1] (currently approaching FPWD) tries to define what chrome is, mentions scrollbars etc.

4.2.1
The term "widget" is used. In order not to confuse a potential reader (aka W3C Widgets), I suggest to change "widget" to "control" or "UI component".

Received on Monday, 21 September 2009 11:18:27 UTC