Action-156: propose alternate resolution for issue-30

To make things clearer and more consistent (with regard to precendence 
rules) in both the WSDL 1.1 and WSDL 2.0 sections, I propose the following 
changes:

1) In section 3.4.4, change this:

"If a property is specified at multiple levels, the most specific setting 
MUST take precedence (URI first, then port, then service, then binding). "

to this:

"If a property is specified at multiple levels within the WSDL document, 
the most specific setting MUST take precedence (URI specified in the 
address element's location attribute first, then port, then service, then 
binding). "

2) In section 3.6.1.1, change this:

"Since the same property can be specified in multiple places, we need 
precedence rules, and in fact they are exactly as specified in section 
3.4.4 Specifying Properties In WSDL 1.1. The most-specific setting 
overrides less-specific ones, so endpoint wins over service, which wins 
over binding. 

to this:

"Since the same property can be specified in multiple places, we need 
precedence rules, and in fact they are similar to those specified in 
section 3.4.4 Specifying Properties In WSDL 1.1. The most-specific setting 
overrides less-specific ones (URI specified in the endpoint element's 
address element, then other properties set on the endpoint, then service, 
then binding)." 

This completes my work for Action-156.

Thanks,
Phil