Misbehaving with the <rule> syntax

Hi all,

Deep down I know this is probably bad, I'd just like to know how bad!

The goal is to have a rule as follows:

<rule urn:reason="abc">
  [..]
</rule>

Obviously if the rule matches 'abc' the content gets built.  However, I 
have linked that rule to an observes element so I can broadcast the 
"urn:reason" attribute value:

<rule urn:reason="abc">
  <observes element="ruleBroadcaster" attribute="urn:reason"/>
  [..]
</rule>

Only the "urn:reason" attribute value never gets forwarded to the <rule>

However, I have found that:

<rule reason="abc">
  <observes element="ruleBroadcaster" attribute="reason"/>
  [..]
</rule>

Works like a charm, as the <rule> just requests an assertion for the 
string "reason" which I can intercept and examine the resource for the 
passed predicate of "abc"

So I guess two questions:

1. How can I forward a namespace attribute via a <broadcaster> to <rule>
2. The fact that without the namespace this works like a charm as I am 
wrapping the HasAssertion() method. Have I found a "feature" or a "bug"?


Cheers,

Neil