Language Tags for the Multilingual Semantic Web
Log In / Register

Pattern for Language Tags

Language tags are required to adhere to the BCP 47 specification, where each sub-tag should come from a standard or registry. When encoding information that is not available in a standard or registry, the privateuse sub-tag is used. To allow for variable length and flexibility of content within this sub-tag, the following pattern is recommended.

Generate a language tag

Part Key 1 Key 2
language 0 0 = User-defined
1 = Glottocode
otherlect 1 0 = User-defined
1 = Glottocode
timeperiod 2 0 = one year only, BC
1 = one year only, AD
2 = start:BC - end:BC
3 = start:BC - end:AD
4 = start:AD - end:AD
region 3 0 = Geohashed latitude and longitude coordinates - polygon
1 = Geohashed latitude and longitude coordinates - point only
2 = URI to GeoJSON-LD
3 = Code from ISO 3166
4 = Identifier from GeoNames
uri 4 0 = URI shortcode from https://londisizwe.org/language-tags/

Part Key 1 Key 2
language 0 0 = User-defined
1 = Glottocode
otherlect 1 0 = User-defined
1 = Glottocode
timeperiod 2 0 = one year only, BC
1 = one year only, AD
2 = start:BC - end:BC
3 = start:BC - end:AD
4 = start:AD - end:AD
region 3 0 = Geohashed latitude and longitude coordinates - polygon
1 = Geohashed latitude and longitude coordinates - point only
2 = URI to GeoJSON-LD
3 = Code from ISO 3166