The policy framework spec says the @name attribute is a QName and even gives
an example where the namespace prefix is used:
<intent name="acme:messageProtection"
constrains="sca:binding"
requires="confidentiality integrity">
<description>
Protect messages from unauthorized reading or
modification.
</description>
</intent>
It is ambiguous to me whether 'acme' can refer to a different namespace than
the targetNamespace. However in my mind it seems conceptually wrong to
construct a definitions.xml file with a given targetNamespace and then make
definitions for another namespace.
I don't think there's a clear way to define qualifiers in one namespace that
extend intents in another namespace.
