-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document design of DOM objects #292
Comments
Ideal target is SDFormat 1.8 release (Target: December 1, 2020) |
Relates #312 - on error behavior of XML parsing, should return |
We're close to December 1st 😄 Do we have an answer to this question? I'm asking in the context of #388. We use SDF DOM classes to store data inside |
there have been a few recent changes (such as #772) that imply some answers to the questions about the DOM object design, though we haven't formally documented answers to these questions yet |
Recent pull requests (such as #785, #838, #839, #840, #841) provide functionality to construct models, links, etc from DOM objects rather than editing XML strings, which would imply that the DOM is not simply a read-only interface. |
The Frame Semantics graphs are currently not updated by DOM API calls. It would be good to find a way to keep them in sync or decouple them in some way. |
Several questions about the design of libsdformat's DOM objects have come up in discussions with @EricCousineau-TRI over time, including the following:
The text was updated successfully, but these errors were encountered: