Some tools support/prefer the XformCommonAPI convention, to describe prim transforms.
Would there be any downsides to having it become an applied schema, making it easier for tools to identify primitives following that convention?
Thanks!
Well, the first problematic thing is that since USD does not provide a way to make attributes “non-overridable”, you could easily degrade a Xformable that claims that it is XformCommonAPI, when it isn’t really…