[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti-stix] Supporting translations in STIX
Writing normative text would help us a ton, thanks! I think we need two things: 1.
The row in the property table:
2.
A new 6.x section in the STIX Core document (sibling of versioning, object markings, etc.) with any other text we need (if any). I would say we either make the field optional with a default of “i-default” or we make it required and force people to say what language they’re providing. We don’t want to tie STIX to
TAXII but if there are transport considerations you think we should include at a more generic level we could do that in the 6.x section. I’d reach out to Bret and Mark on the TAXII side to include the Accept-Language stuff directly in those specs. Thanks again, John From:
Dave Cridland <dave.cridland@surevine.com> 2(a) for now. I'm assuming a IANA language tag here, with a default of "i-default" (from memory). I think translation objects will work, an alternate design might be to duplicate the entire object (reference and all), or have a relationship to indicate equivalent objects (which allows for both translations and more complex equivalences). We'd want TAXII to mention something about Accept-Language for HTTP, and maybe note about other l11n capabilities in other transports (eg, stream language in XMPP), and payload formats (Content-Language in HTTP, email, and stanza language tag in XMPP). I can knock out some formal normative text if you like. Dave. On 24 Jun 2016 16:28, "Wunder, John A." <jwunder@mitre.org> wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]