Hi All,
To address the OP, I would say that the parallel-plane zone must be perpendicular to the datum axis "all around" and not just in the view shown. I guess that my tendency to agree with Paul outweighs my tendency to disagree with Dave ;^). None of the examples in '94 or '09 deal with this specific case, and the "applies only to the view on which it is specified" stuff seems to only be applied to cylindrical considered features.
The side conversations have brought out some interesting issues. I think that there were several questionable things in Y14.5's orientation tolerance examples, and most (but not all) were fixed in '09.
The two examples in '94 (Fig. 6-28 and Fig. 6-37) in which the orientation control "applies only to the view on which it is specified" were deleted in '09. Hooray! The "view" cannot be rigorously defined on a real part. These two examples also had a parallel-plane zone for a cylindrical feature which doesn't make sense to me (see below).
Let's look at Fig. 6-31 in '94 (Fig. 6-7 in '09). The Parallelism tolerance zone is specified as two parallel planes, but I think that this is a flawed concept. It's true that the axis can lie anywhere in a volume between two parallel planes 0.12 apart. But to me it's a cylindrical zone that can freely translate and can also rotate in the direction "parallel" to the datum plane. I know that this is subtle distinction, but I have no problem spitting hairs ;^). To be consistent, the tolerance zone in Fig. 6-31 should be specified as cylindrical as it is in Fig. 6-32.
The Angularity examples were improved in '09 with the addition of location controls. But I still have one problem with Fig. 6-6. The Angularity tolerance is supposed to be a refinement of the location tolerance, but because only one datum feature is referenced the Position tolerance is only controlling orientation anyway. So we have an orientation tolerance RFS refining a Position tolerance at MMC that is only controlling orientation. Some would say that the Position tolerance in 6-6 is illegal, because it doesn't locate the feature ;^). But we beat that one to death a few days ago.
Evan Janeshewski
Axymetrix Quality Engineering Inc.