You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please document the relationship between the API and the XSD. Is the API all or partially generated as STIX is? Given an API object or method can I deterministically know the corresponding XSD element. And the reverse - Given a XSD type or property can I deterministically know the corresponding API object or method?
The text was updated successfully, but these errors were encountered:
The python-cybox API is generated the same way as the python-stix API. There are the generateDS-generated bindings, and the corresponding higher-level "API" objects. the "API" layer is designed to map to the binding layer (using a couple naming conventions I can lay out in more detail), and the binding layer is responsible for parsing XML and also exporting XML. (The XSDs were the input to generateDS, but are otherwise not involved in python-cybox).
I agree we've been looooooooooooong overdue for some better documentation on the rationale behind some of the design decisions in python-cybox.
@CoryCasanave : If you can describe a bit more about what you're trying to do, I might be able to provide more detailed information. Feel free to email [email protected] or just respond on here. 😄
Please document the relationship between the API and the XSD. Is the API all or partially generated as STIX is? Given an API object or method can I deterministically know the corresponding XSD element. And the reverse - Given a XSD type or property can I deterministically know the corresponding API object or method?
The text was updated successfully, but these errors were encountered: