John-Paul,
I said location "constrainable", not location "constrained".
What you call a broad assumption includes no assumptions..? It is a statement that I believe if free of assumptions.
I would never apply profile of a line to accomplish the the same thing that parallelism of line elements could accomplish, so I think anyone arguing that Fig 8-27 shows a good practice is making things complicated. I would use profile with a customized datum reference frame only if the upper surface of the part were not a planar surface.
Fig. 6-2 shows a figure with the entire upper surface of the part having its orientation and form refined with a parallelism tolerance. That seems fine to me. The size tolerance also applied in the figure seems likely to be OK too. One could question whether the features included with the size tolerance constitute a valid feature of size, since the two surfaces are not fully opposed (one being smaller than the other), but I believe the design engineer needs to decide whether a feature such as this should be considered a feature of size. Somewhere between fully opposed and fully offset, the feature must transition from a feature of size to one that is not a feature of size... The line where that transition occurs needs to be determined by the design engineer, I believe.
Frank,
Your concern about the acceptance of GD&T and whether Y14.5 and other Y14 standards are becoming less relevant as they are developed further is valid for sure. We're all in an odd state where ambiguous specs are often tolerated by industry, the quality of measurement data is often low, many in the academic world view GD&T as "too easy" ("it lacks academic rigor", I've been told) and a drafting or manufacturing subject that isn't worthy of adequate coverage in their mechanical engineering curriculum, while industry views GD&T as "too hard" ("if I put that on the drawing no one will understand it"). There are things we could do to simplify the language a bit, such as reducing or eliminating the need to calculate where boundaries are. We could instead allow direct statement of the location and type of tolerance zone boundaries. We could clarify the orientation of line elements or cross-sections with more explicit notations.
We could also have some sort of certification for metrologists. Having an ASME GDTP certification may help a metrologist, but what about the need to iterate to establish a repeatable datum reference frame with a probing CMM, the need to verify repeatability of data in a standard way, and when and how to properly design fixtures to restrain parts for measurement.
Overall, I see "Mother nature" as the entity that requires the level of complexity in GD&T... Dealing with imperfect geometry in an explicit and complete way is not so easy (as most of those reading this know). I think especially upper level managers will always need convincing with regard to the need for GD&T in order to optimally design and produce physical products. Measuring a part with a pair of calipers seems so simple to them. I haven't encountered an electrical engineering subject which would be viewed as something that can be simplified to the point that someone stepping in off the street should be able to understand it. Our mechanical engineering subject of GD&T suffers from the apparent simplicity of "dimensions", I believe. Some academics and some managers in some industries "get it". When we can say that most "get it" then we will be past our current state of affairs & in a better place, I hope.
Pmarc,
Yes, I think two single segment feature control frames with position or profile could replace composite feature control frames. They're almost equal, except for how simultaneous requirements works (with "SIM REQT" being required to tie together patterns that are toleranced with separate composite feature control frames... no such need with a set of single segment feature control frames). Customized DRFs are better since they more explicitly state what they mean than composite FCFs do, and the method is also more flexible/powerful since even rotational degrees of freedom constraint can be selectively specified using the customized method... I will create a couple of examples and ask in a new topic what others think of setting aside composite in favor of customized. It makes sense to introduce customized drfs before composite would be set aside, but I don't know what is best with regard to the overlap time, when both are available in the standard.
Best Regards,
Dean