We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Noticed not all elements in the oasis ciq 3 are not be translated over to JSON.
<stixCommon:Identity xsi:type="stix-ciq:CIQIdentity3.0InstanceType"> <stix-ciq:Specification> <xpil:BirthInfo> <xpil:BirthPlaceDetails> <xal:FreeTextAddress> <xal:AddressLine> TEST23236 </xal:AddressLine> </xal:FreeTextAddress> </xpil:BirthPlaceDetails> <xpil:BirthInfoElement> TEST23236 </xpil:BirthInfoElement> </xpil:BirthInfo> <xpil:Accounts> <xpil:Account> <xpil:Organisation> <xnl:NameElement>TEST23235</xnl:NameElement> </xpil:Organisation> </xpil:Account> </xpil:Accounts> <xpil:PartyName> <xnl:OrganisationName> <xnl:NameElement>ACME CORP</xnl:NameElement> </xnl:OrganisationName> </xpil:PartyName> <xpil:Addresses> <xpil:Address> <xal:Country> <xal:NameElement xal:NameCode="US" xal:NameCodeType="ISO 3166-1 alpha-2"></xal:NameElement> </xal:Country> <xal:AdministrativeArea> <xal:NameElement xal:NameCode="US-DC" xal:NameCodeType="ISO 3166-2"></xal:NameElement> </xal:AdministrativeArea> </xpil:Address> </xpil:Addresses> <xpil:OrganisationInfo xpil:IndustryType="SECTOR_1 | SECTOR_2 | Chemical Sector | Dams Sector" ></xpil:OrganisationInfo> </stix-ciq:Specification> </stixCommon:Identity>
The text was updated successfully, but these errors were encountered:
The Identity object in STIX 2.x doesn't support a lot of the ciq content. Were you expecting the information to appear somewhere?
BTW - I assume you mean "aren't translated" in the summary of this issue?
Sorry, something went wrong.
No branches or pull requests
Noticed not all elements in the oasis ciq 3 are not be translated over to JSON.
The text was updated successfully, but these errors were encountered: