EM CAP SC

Friends,  Please see the forwarded conversation from Eliot on how the language codes are now referenced.  We need to consider this and perhaps make an update in this regard for the CAP 1.2 errata.  If you agree, I will open a JIRA issue on the topic.  Elysa   From: Eliot Christian [mailto:eliot.j.christian@gmail.com] Sent: Tuesday, November 21, 2017 6:27 AM To: Elysa Jones <ElysaJones@yahoo.com> Subject: Re: How does CAP identify Papiamento?   Reading this article , it looks like language code reference to ISO 3066 in the CAP standard need to be updated. The article says: The latest RFC describing language tag syntax is  RFC 5646, Tags for the Identification of Languages , and it obsoletes the older RFCs  4646 ,  3066  and  1766 . You used to find subtags by consulting the lists of codes in various ISO standards, but now you can find all subtags in the  IANA Language Subtag Registry .     The language code for Papiamento is listed as "pap" in the IANA Language Subtag Registry, so updating the CAP standard would fix my immediate problem.       On Mon, Nov 20, 2017 at 5:09 AM, Eliot Christian < eliot.j.christian@gmail.com > wrote: Hi Elysa,   Apparently, ISO 639 does not have two-letter code for the language Papiamento, although its does provide a 3-letter code, "pap".   The CAP standard references RFC3066 for the value of the "language" element and that RFC only allows the ISO 639 two-letter codes for languages (plus an optional subtag to differentiate the language as used in a particular country). So, according to the CAP standard, one cannot provide a valid language value for  a CAP alert in Papiamento.   How was this handled in CAP servers implemented in countries where Papiamento is an official language (Aruba, Curacao)?   Eliot  

This also affects our other EDXL standards and specifications, EDXL-HAVE-v2.0 in particular at this time. So it should also be an agenda item for the next HAVE SC meeting next week and the next RIM SC meeting in two weeks. Cheers, Rex On 11/21/2017 5:29 AM, Elysa Jones wrote: Friends,  Please see the forwarded conversation from Eliot on how the language codes are now referenced.  We need to consider this and perhaps make an update in this regard for the CAP 1.2 errata.  If you agree, I will open a JIRA issue on the topic.  Elysa   From: Eliot Christian [ mailto:eliot.j.christian@gmail.com ] Sent: Tuesday, November 21, 2017 6:27 AM To: Elysa Jones <ElysaJones@yahoo.com> Subject: Re: How does CAP identify Papiamento?   Reading this article , it looks like language code reference to ISO 3066 in the CAP standard need to be updated. The article says: The latest RFC describing language tag syntax is  RFC 5646, Tags for the Identification of Languages , and it obsoletes the older RFCs  4646 ,  3066  and  1766 . You used to find subtags by consulting the lists of codes in various ISO standards, but now you can find all subtags in the  IANA Language Subtag Registry .     The language code for Papiamento is listed as pap in the IANA Language Subtag Registry, so updating the CAP standard would fix my immediate problem.       On Mon, Nov 20, 2017 at 5:09 AM, Eliot Christian < eliot.j.christian@gmail.com > wrote: Hi Elysa,   Apparently, ISO 639 does not have two-letter code for the language Papiamento, although its does provide a 3-letter code, pap .   The CAP standard references RFC3066 for the value of the language element and that RFC only allows the ISO 639 two-letter codes for languages (plus an optional subtag to differentiate the language as used in a particular country). So, according to the CAP standard, one cannot provide a valid language value for  a CAP alert in Papiamento.   How was this handled in CAP servers implemented in countries where Papiamento is an official language (Aruba, Curacao)?   Eliot   -- Rex Brooks Starbourne Communications Design Email: rexb@starbourne.com GeoAddress: 1361 Addison St. Apt. A Berkeley, CA 94702 Phone: 510-898-0670 Virus-free. www.avast.com

This also affects our other EDXL standards and specifications, EDXL-HAVE-v2.0 in particular at this time. So it should also be an agenda item for the next HAVE SC meeting next week and the next RIM SC meeting in two weeks. Cheers, Rex On 11/21/2017 5:29 AM, Elysa Jones wrote: Friends,  Please see the forwarded conversation from Eliot on how the language codes are now referenced.  We need to consider this and perhaps make an update in this regard for the CAP 1.2 errata.  If you agree, I will open a JIRA issue on the topic.  Elysa   From: Eliot Christian [ mailto:eliot.j.christian@gmail.com ] Sent: Tuesday, November 21, 2017 6:27 AM To: Elysa Jones <ElysaJones@yahoo.com> Subject: Re: How does CAP identify Papiamento?   Reading this article , it looks like language code reference to ISO 3066 in the CAP standard need to be updated. The article says: The latest RFC describing language tag syntax is  RFC 5646, Tags for the Identification of Languages , and it obsoletes the older RFCs  4646 ,  3066  and  1766 . You used to find subtags by consulting the lists of codes in various ISO standards, but now you can find all subtags in the  IANA Language Subtag Registry .     The language code for Papiamento is listed as pap in the IANA Language Subtag Registry, so updating the CAP standard would fix my immediate problem.       On Mon, Nov 20, 2017 at 5:09 AM, Eliot Christian < eliot.j.christian@gmail.com > wrote: Hi Elysa,   Apparently, ISO 639 does not have two-letter code for the language Papiamento, although its does provide a 3-letter code, pap .   The CAP standard references RFC3066 for the value of the language element and that RFC only allows the ISO 639 two-letter codes for languages (plus an optional subtag to differentiate the language as used in a particular country). So, according to the CAP standard, one cannot provide a valid language value for  a CAP alert in Papiamento.   How was this handled in CAP servers implemented in countries where Papiamento is an official language (Aruba, Curacao)?   Eliot   -- Rex Brooks Starbourne Communications Design Email: rexb@starbourne.com GeoAddress: 1361 Addison St. Apt. A Berkeley, CA 94702 Phone: 510-898-0670 Virus-free. www.avast.com

> Friends, Please see the forwarded conversation from Eliot on how the language codes are now referenced. > The language code for Papiamento is listed as "pap" in the IANA Language Subtag Registry, so updating the CAP standard > would fix my immediate problem. While there have been updates to RFC 3066 to add further code types, 3 letter codes are already allowed by that RFC and supported by the XML schema type for language. So there should be no changes needed to use "pap" in a valid CAP message. The RFC states that subtags may be 1 to 8 characters in length. The syntax of this tag in ABNF [RFC 2234] is: Language-Tag = Primary-subtag *( "-" Subtag ) Primary-subtag = 1*8ALPHA Subtag = 1*8(ALPHA / DIGIT) -- Jacob Westfall <jake@jpw.biz>