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


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-cap message

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

Subject: Re: [emergency-cap] FW: How does CAP identify Papiamento?

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

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