Repository navigation
Creation of STIXCIQIdentity3_0 and its children entities does not emit the "Entity.created.from_obj" signal #356
Description
Activity
Hi @stevefranchak!
Thanks for reporting this. It appears the markings don't get applied to this extension because their children need binding objects and new API objects that implement the newTypedFieldchanges. Thus, anyCIQIdentity3_0Instancechildren would not be captured bystixmarxand will not be marked.Thanks for responding, @emmanvg!
Is this something that your team is planning on updating? I could try figuring it out but wanted to check with you first. (And I'll make sure to include tests this time - that was my bad.)
@stevefranchak, unfortunately we don't see this as being high priority; instead we are focusing most of our efforts towards STIX 2. I would certainly appreciate a PR if you or anyone is willing to extend the current functionality.
Keep in mindstix-ciqidentity:CIQIdentity3_0Instanceextension leverages the CIQ Specification which is extensive. Here is a link to the XSD schemas.
It appears that the
from_objmethod of theSTIXCIQIdentity3_0class and classes for child nodes ofstix-ciqidentity:Specificationdo not call up tomixbox.entities.Entity.from_obj.mixbox.entities.Entity.from_objemits aEntity.created.from_objsignal.stixmarx.parser.MarkingParsercreates its set of entities to use for processing by subscribing its_handle_entity_createdcallback to theEntity.created.from_objsignal. As a result, since this signal is not sent for any entities of and includingstix-ciqidentity:Specification, these entities are not marked by stixmarx. I'm creating this as an issue against python-stix because theCIQIdentity3_0Instanceimplementation is contained in this project.