5.3 Exposing attributes that don not directly map ...

1st para, last sentence: "User agents MAY also expose the WAI-ARIA data through this API even when there is a direct mapping to an accessibility API." Now look down to the second paragraph of section 4.4 Role mapping. It says "the entire role string MUST also be available for parsing". Also see rule #5 in the following list. The MUST statements in 4.4 seem to conflict with the MAY statement in 4.3. 

5.4 Role mapping

2nd paragraph: "The user agent MUST expose roles so that the standard role mechanism of the accessibility API provides the best-fit widget role, yet the entire role string MUST also be available for parsing." This is another statement that seems to me should not use the RFC2119 MUST structure. The rules for compliance are provided in the following list and the mapping table. I'd like to change this to "The user agent exposes roles according to the following rules and the Role Mapping Table." Any objections?

bullet #5: requires the entire role string to be passed. But in the role mapping table in 4.4.1, look at one of the ones that doesn't have a direct mapping, like "banner". We specify how to pass that particular role. But really, the requirement is to pass the entire role string. So should we strip all of these out of the table or am I seeing confusion where UA developers won't?