Hello Willy.
I must say I'm really looking forward to time when snap data is standardized. I hoped for that in times of my contributions to SR3DB, already. However, there is no such standard yet, even not started (as far as I know). And my job is to make (real) models for exhibitions which are organized now - and so I need a help of a good editor with good snap data now. It's the only way how I can make my models in time. Every help is welcome and snap data is such a (big!) help.
The result is that I have to accept the risk that my work for any specific editor may be lost or isolated out of standard in future. I know about that risk and I even knew about much higher risk with SR3DB I helped with in past - because it was a private, closed-source project which could become inaccessible at any moment. And that happened, most of my work there is lost, as far as I know. But I have no other option than to accept this risk - that's why I contribute to all these editors and I continue to do so.
And the last note: the only work on SR3DB I made and it persists over the project death is my snap data contribution - as it is the public part of SR3DB, including at least the basics of the format specification. And the format specification/description was published by Sergio only because he saw so big interest of other people to contribute snap data. Otherwise you would have nothing to discuss for future standard about SR3DB now. So I believe it makes sense to contribute snap data to editors even before the standard is settled up - with all risks mentioned above.
I must say I'm really looking forward to time when snap data is standardized. I hoped for that in times of my contributions to SR3DB, already. However, there is no such standard yet, even not started (as far as I know). And my job is to make (real) models for exhibitions which are organized now - and so I need a help of a good editor with good snap data now. It's the only way how I can make my models in time. Every help is welcome and snap data is such a (big!) help.
The result is that I have to accept the risk that my work for any specific editor may be lost or isolated out of standard in future. I know about that risk and I even knew about much higher risk with SR3DB I helped with in past - because it was a private, closed-source project which could become inaccessible at any moment. And that happened, most of my work there is lost, as far as I know. But I have no other option than to accept this risk - that's why I contribute to all these editors and I continue to do so.
And the last note: the only work on SR3DB I made and it persists over the project death is my snap data contribution - as it is the public part of SR3DB, including at least the basics of the format specification. And the format specification/description was published by Sergio only because he saw so big interest of other people to contribute snap data. Otherwise you would have nothing to discuss for future standard about SR3DB now. So I believe it makes sense to contribute snap data to editors even before the standard is settled up - with all risks mentioned above.