Re: [cti-stix] Supporting translations in STIX

["Jordan, Bret" <bret.jordan@bluecoat.com>]

Personally I think if you are going to translate the name of the file you would do that in the description of the Observation or Incident.  You would not do it in CybOX itself.  CybOX should be just the facts, regardless of what the facts may be.

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." 

On Jun 28, 2016, at 17:38, John-Mark Gurney <jmg@newcontext.com> wrote:

Allan Thomson wrote this message on Fri, Jun 24, 2016 at 16:00 +0000:

The sighting points to an indicator that identifies the pattern, which may be in english. But the sighting also points to the observation of the captured information which is in non-english.

We should restrict using language for fields that are human generated
and human consumed..  CybOX data, though may be in a specific language
cannot be translated w/o changing the meaning of it..  If a file name
is in Japanese in an Observation (CybOX data), translating that would
change the meaning of the Observation, and not be helpful...  Labeling
that it's Japense also does not provide any advantage (that I can think
of)..

On 6/24/16, 8:53 AM, "Back, Greg" <gback@mitre.org> wrote:

Are there specific sub-components where we would potentially want to support a different language from the parent TLO (for now, given that we can always add it later)?

--
John-Mark

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail