Skip to content
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

Relationship between API and XSD #221

Open
CoryCasanave opened this issue Nov 26, 2014 · 1 comment
Open

Relationship between API and XSD #221

CoryCasanave opened this issue Nov 26, 2014 · 1 comment
Labels

Comments

@CoryCasanave
Copy link

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?

@gtback gtback added the question label Feb 2, 2015
@gtback
Copy link
Contributor

gtback commented Feb 2, 2015

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. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants