Namespace cleanup

[gtback]

DO NOT MERGE!

I'm just opening a pull request so we can talk about things in this branch.

[bworrell]

Maybe we could just move this after the DEFAULT_STIX_PREFIX_TO_NAMESPACE assignment below, and use that to create this dictionary?

[gtback]

STIX_NAMESPACES is just the stix.mitre.org and data-marking.mitre.org namespaces (not CybOX, MAEC, Extensions, etc.). It's used in the STIX core binding, otherwise we can just get rid of it entirely (I didn't look into how it's used there.)

[bworrell]

So far this is looking pretty cool to me! I'm wondering if NamespaceInfo should be moved to mixbox and generalized a bit. It has a _BASELINE_NAMESPACES class attribute which contains namespaces that CybOX/MAEC don't care about.

Then mixbox.Entity could be refactored to use NamespaceInfo for namespace gathering. I think it'd be awesome if we could define one approach namespace/schemalocation collection for all the APIs to use.

[gtback]

Yes, ultimately NamespaceInfo should be moved to mixbox. There's some overlap with the functionality I was intending for NamespaceSet, and was on the fence about whether to merge them together or keep them separate.

Entity should be modified to use NamespaceInfo (either directly or as part of EntityParser). Getting the code out of python-stix and into mixbox is the first step.

[landscape-bot]

Repository health decreased by 9% when pulling a08cb12 on namespace-cleanup into 8618b0f on master.

• 269 new problems were found (including 250 errors and 3 code smells).
• 10 problems were fixed (including 0 errors and 4 code smells).