[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti] i18n (RE: MVP Discussion)
What I would like to know, yes I am partial to this design, is how this design will NOT work for people. With some workflow analysis, and keeping with the identifier and versioning designs in STIX, I believe this, as represented by John-Mark, is the simplest and most straight forward solution. But if I am missing some really key point, please call it out. Personally I believe this design is straight forward enough and simple enough, that we could get this in the Summer 2016 release of STIX. However, as I said, if it is missing some key thing, please let me know so I can better understand. This solution does the following: 1) Provides a solution for single producer, a UI in a product can easily allow translations to be created under the covers for an object. 2) Provides a solution for third party translators. 3) Allows translations to be sent separate from the original file. 4) It does not require us to pre-identify every field that we want to translate and thus add UUIDs to all of the objects causing significant bloat on the wire and increased demands on processing. There are few elements that this design does not cover... a) Mixing languages in the same JSON object. This can be a good thing from a graph database standpoint and really simplifies the consumption of objects or request of the objects from a TAXII server. b) It is not very clean for translating deeply nested objects. I am sure we can figure out a solution for this, but the current example does not show one. However, given our design criteria for STIX 2.x, we are desperately trying to flatten the objects as much as possible, so this may or may not end up being an issue. 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]