UML14 — Inconsistency regarding guards on forks

This applies to UML 1.4.1. ad/02-06-05. There seems inconsistency as to whether forks can have guards.
The notation, section 3.9.4, states: "In Activity Diagrams, transitions outgoing from forks may have guards. This means the region initiated by a fork transition might not start, and therefore is not required to complete at the corresponding join. The usual notation and mapping for guards may be used on the transition outgoing from a fork."

However this seems contradicted by Section 2.12.2.7, PseudoState, which states: "fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices. The segments outgoing from a fork vertex must not have guards."

Is this a real inconsistency or do activity diagrams really override the constraint on Pseudostates in State Machines?

No Data Available