If the data starts as a "side table" of some kind, it could later be merged into the parts with a one-time batch process if desired; similarly if the data were on the parts themselves it could be extracted. My guess is that a side table would be much easier for initial prototyping - it would let a few developers get started with connection data without interfering with the main library.
Since official parts aren't going to have their coordinate origins change there isn't a risk of the connection file getting out of date if it only targets official parts.
Question:
1. Are there any pre-made lego parts that translate in more than one dimension? I can't think of one off-hand but maybe there's an obscure one out there...
It does look like there are ball & sockets where the maximum angle of deflection varies by direction, e.g. it looks to me like 63082 with 2508 can rotate more horizontally than vertically.
Since official parts aren't going to have their coordinate origins change there isn't a risk of the connection file getting out of date if it only targets official parts.
Question:
1. Are there any pre-made lego parts that translate in more than one dimension? I can't think of one off-hand but maybe there's an obscure one out there...
It does look like there are ball & sockets where the maximum angle of deflection varies by direction, e.g. it looks to me like 63082 with 2508 can rotate more horizontally than vertically.