We're going to get stuck in the same cycle of custom software built on weak standards that hobbled SGML development, unable to reach a low-cost commodity solution because we wanted to keep the standards flexible. I see what you mean. It's really too bad that I licensed XLinkFilter under MPL instead of BSD, because you have to expose your logic to the world if you use it, making it harder to build those profitable proprietary custom solutions. You can either ignore the suggested connections, or you can be happy that someone specified the connections in a language you can understand. Linking can just as easily have roughtly eauivalent generality.
Generality is good, but ambiguity is a vice.
XML is extremely unambiguous, though very general. XLink is both general and extremely ambiguous. Ambiguity in this case is a vice.