Re: [cti] RE: Internationalization in STIX 2.1

Relationships do have a description property.

 

From: <> on behalf of "Taylor, Marlon" <>

Date: Wednesday, June 28, 2017 at 12:56 PM

To: John Wunder <>, "Masuoka, Ryusuke" <>, "" <>

Subject: RE: [cti] RE: Internationalization in STIX 2.1

 

Hi John,

Should relationship objects be excluded too?

- Marlon 

 

From:  on behalf of Wunder, John A.

Sent: Tuesday, June 27, 2017 10:20:08 AM

To: Masuoka, Ryusuke; 

Subject: Re: [cti] RE: Internationalization in STIX 2.1

Hi Ryu,

 

Yes, you’re right that the two options are either required (a normative MUST) or optional/recommended (a normative SHOULD).

 

You’re also right that the set of objects is the same for each: all objects except for bundle, observed-data, and sighting. So for option #1 (normative MUST), bundle would not have a lang field because it
 doesn’t have any text fields that can be translated, it’s just an id, spec_version, and the contents. Same for observed-data and sighting.

 

John

 

From: <> on behalf of "Masuoka, Ryusuke" <>

Date: Tuesday, June 27, 2017 at 3:27 AM

To: "" <>

Subject: [cti] RE: Internationalization in STIX 2.1

 

Hi, John,

 

Thank you for the compilation and the last i18n decision to make.

Please let me make sure about the two options of the decision.

 

- MUST = REQUIRED = SHALL

- SHOULD = RECOMMENDED = OPTIONAL

 

and the two options are the following.

 

(1) each top-level object in STIX MUST have the `lang` field populated

on every object (not including bundle, observed-data, and sighting,

which don’t
 have translatable fields)

 

(2) each top-level object in STIX SHOULD have the `lang` field populated

on every object (not including bundle, observed-data, and sighting,

which don’t
 have translatable fields)

 

[“(not including
 bundle...)” applies to (1) as well, right?]

 

Regards,

 

Ryu

 

From:  [mailto:]
On Behalf Of Wunder, John A.

Sent: Saturday, June 24, 2017 2:39 AM

To: 

Subject: [cti] Internationalization in STIX 2.1

 

Hey all,

 

One of the topics we’ve been grappling with for awhile in STIX 2.1 is internationalization. We want STIX content, specifically, to be translatable into different languages so that you can have publishers creating
 content in several languages, third party translation services for STIX content, and identification of which language specific content is in.

 

We’ve made a lot of progress towards that end. Here’s what we have:

 

Each top-level object will have a field called `lang` to indicate what language that content is in. That means that a campaign object could be published with
 a `lang` field of Japanese to indicate that the name, description, and other human text fields are in Japanese. (https://docs.google.com/document/d/1HRVFn2kAxBOTMbEb3KRu8tjMoHm-KRAI-2R8CTzGil4/edit#heading=h.xzbicbtscatx
 scroll down to `lang`)

A “granular language markings” capability, so that you can indicate that certain fields in the object are in English, while others are in Japanese. (https://docs.google.com/document/d/1HRVFn2kAxBOTMbEb3KRu8tjMoHm-KRAI-2R8CTzGil4/edit#heading=h.l6edgya0tyjq
 see new `lang` property on granular markings)

A separate “language-content” object that allows you to provide additional languages (translations) for that content. So you could publish a campaign in Japanese
 and then provide a language-content object with that same text in English. (https://docs.google.com/document/d/1HRVFn2kAxBOTMbEb3KRu8tjMoHm-KRAI-2R8CTzGil4/edit#heading=h.cfz5hcantmvx)

 

One thing we have no decided yet is whether each top-level object in STIX
MUST have the `lang` field populated on every object or SHOULD have the `lang` field populated on every object (not including bundle, observed-data, and sighting, which don’t have translatable fields). There have been previous discussions on Slack,
 e-mail, and at the face-to-face…you should be able to dig through the mailing lists to find it, the most recent one can be found in the Feb-Mar 2017 archives:

 

https://lists.oasis-open.org/archives/cti/201702/threads.html#00031

https://lists.oasis-open.org/archives/cti/201703/threads.html#00000

 

It seems like at this point we just need to have a ballot to resolve this. So, I move that the TC open a ballot to determine whether we feel the `lang` property should be required on each top-level object
 or optional on each top-level object (i.e. STIX Domain Objects, STIX Relationship Objects, data-marking objects).

 

John