OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cti message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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: <cti@lists.oasis-open.org> on behalf of "Masuoka, Ryusuke" <masuoka.ryusuke@jp.fujitsu.com>
Date: Tuesday, June 27, 2017 at 3:27 AM
To: "cti@lists.oasis-open.org" <cti@lists.oasis-open.org>
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 dont 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 dont have translatable fields)

 

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

 

Regards,

 

Ryu

 

From: cti@lists.oasis-open.org [mailto:cti@lists.oasis-open.org] On Behalf Of Wunder, John A.
Sent: Saturday, June 24, 2017 2:39 AM
To: cti@lists.oasis-open.org
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:

 

 

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:

 

 

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

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]