TRANS13 — bug with NonTxTargetPolicy

The table in the spec that talks about the interaction of the OTS
Policy and NonTxTargetPolicy is something like:

> Target object Called with Called with
> OTS policy / a transaction no transaction
> NonTxTargetPolicy
> -------------------------------------------------------------------
> FORBIDS / raise dispatch request
> PREVENT INVALID_TRANSACTION
>
> FORBIDS / dispatch request dispatch request
> PERMIT WITHOUT transaction

Furthermore the the OTS specification defines a non-transactional object
as one that either has a FORBIDS policy or no OTSPolicy at all.

Consider the case of FORBIDS/PERMIT. FORBIDS says that transactional
requests may not be invoked. PERMIT however, says that requests can be
dispatched to non-transactional objects outside of the context of a
transaction.

There is a conflict here. In effect, the verbage in the spec says that
PERMIT overrides FORBIDS – and that's wrong and contrary to my
understanding of what the intent of this was.

I think the source of the problem is this:

"A non-transactional object has an IOR that either contains a
TAG_OTS_POLICY component with a value of FORBIDS or does not contain a
TAG_OTS_POLICY component at all."

An object with FORBIDS should never receive transactional requests.
I think more properly the PERMIT/PREVENT policy should only affect those
objects that have no OTSPolicy at all.

see below