Re: [editorial] change of element names

[Sunil Kunisetty <Sunil.Kunisetty@oracle.com>]

 While at this, I also propose to rename the fault attribute for both ReplyRange
 and NonSequenceReply to faultCode.

 -Sunil

Sunil Kunisetty wrote:

>  I propose that all our Header element names start with the
>  prefix 'RM', i.e., Request element be renamed RMRequest,
>  PollRequest be renamed as RMPollRequest, and Response
>  be renamed RMResponse.
>
>  Reason being that the current names are too generic and
>  could be confusing (to manual readers). Not an issue for
>  tools though as they are all QNames.
>
>  Just to jot some memories, all our names indeed used to start
>  with this prefix a while back.
>
>  However, they were removed later as people felt it is redundant
>  as the namespace prefix (used in some of our examples) also
>  use the word 'rm'.
>
>  To me that's a flawed reasoning.
>
>  Namespace prefix is just a namespace prefix. We can't mandate
>  that consumers of this always use the prefix 'rm'.  Namespace
>  prefix is just a convenience alias mechanism.
>
>  It's valid and legal to use any prefix (foo:Request, xyz:InvalidMessageId
>  etc..) as long as the prefix is correctly defined to our namespace.
>
>  Infact, the usage of prefix is not always required if the default namespace
>  is defined to be RM namespace. As a matter of fact, the examples in
>  page 7-8-9 doesn't use any prefix for RM elements.
>
>  -Sunil