[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti] i18n (RE: MVP Discussion) - An Updated Proposal
So STIX is supposed to be about how to transmit the data in a structured form. So if you had in your database the original Indicator and a bunch of translations, and you got a request for the Indicator in say en-us, then you would have two options (based on your legal contracts and terms of use agreements). 1) Issue a new indicator under your identity space, and just include the en-us text. As the example below 2) Republish the original ja version along with the en-us translation. You may or may not decide to include the de translation. Thoughts???? “indicators": [ { "type": “indicator", "id": "indicator--a1201df6-c352-4a81-9c7c-5a6f896a4eAA", "revision": 1, "created_at": "2015-12-03T13:13Z", "created_by_ref": "identity--69a17e1b-bb45-4657-9a9d-96db3faccdDD", "lang”:"en-us", "title": "Dridex something or other 121", “description": "some sort of description" }, Thanks, Bret Bret Jordan CISSP Director of Security Architecture and Standards | Office of the CTO Blue Coat Systems PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050 "Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."
|
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]