jriegel wrote:OCC is not the problem. They have already a naming service, but tightly bundled with their document model OCAF. Its the TNaming package. I think there is a lot to learn...
No doubt. I have looked at the naming and document overviews. I am sure you can get something working, it just looks like an afterthought and not part of the modeling architecture. OCC is always the problem
. OCC is getting used because there is no alternative.
jriegel wrote:But the real holly grail in that regard is not only naming, its also sharing.
I understand what you are getting at. Don't we get sharing implicitly through the use of TopDS_Shape? But then we loose this through serialization as each feature writes out it's own brep structure?
Sorry for doing this in the pull requests forum. Feel free to shoot this thread over to the developers corner.