I was wondering what the roadmap for the collada specification looks like.
I just wrote up a bit of code to implement the 1.3 spec assuming that the xml would still be mostly usable moving forward (it is extensible markup language).
Anyway, the spec changed the library tag considerably, and while I agree that it changed for the better in some regards…
Library with an attribute of geometries to Library_Geometries
I was wondering are there any other major breaking changes to renaming of already used tags (especially tags with attributes) in the plans…
ie.) is it going to be just plain Geometries with sub geometry elements later. What’s the use of the Library word in front of Geometries now except as a pointer to the data that used to be contained in that same tag.
As long as you the design philosophy in the document remains consistent we can more easily plan for changes.
Adding elements and attributes is easy enough to handle. Renaming existing elements based on the parent element and their attribute is annoying, and will get out of hand if done through minor version changes.
Again, I’m glad that you made this change because it is better and should have been done in the original spec. I just want to avoid the problems listed above as much as possible.