7 INTERNET-DRAFT Editor: Kurt D. Zeilenga
8 Intended Category: Standard Track OpenLDAP Foundation
9 Expires in six months 1 March 2002
13 Language Tags and Ranges in LDAP
14 draft-zeilenga-ldap-rfc2596-01.txt
19 This document is an Internet-Draft and is in full conformance with all
20 provisions of Section 10 of RFC2026.
22 This document is intended to be, after appropriate review and
23 revision, submitted to the RFC Editor as a Standard Track document.
24 Distribution of this memo is unlimited. Technical discussion of this
25 document will take place on the IETF LDAP Extensions Working Group
26 (LDAPext) mailing list <ietf-ldapext@netscape.com>. Please send
27 editorial comments directly to the document editor
30 Internet-Drafts are working documents of the Internet Engineering Task
31 Force (IETF), its areas, and its working groups. Note that other
32 groups may also distribute working documents as Internet-Drafts.
33 Internet-Drafts are draft documents valid for a maximum of six months
34 and may be updated, replaced, or obsoleted by other documents at any
35 time. It is inappropriate to use Internet-Drafts as reference
36 material or to cite them other than as ``work in progress.''
38 The list of current Internet-Drafts can be accessed at
39 <http://www.ietf.org/ietf/1id-abstracts.txt>. The list of
40 Internet-Draft Shadow Directories can be accessed at
41 <http://www.ietf.org/shadow.html>.
43 Copyright 2002, The Internet Society. All Rights Reserved.
45 Please see the Copyright section near the end of this document for
50 It is often desirable to to be able to indicate the natural language
51 associated with values held in a directory and to be able to query the
52 directory for values which fulfill the user's language needs. This
53 document details the use of Language Tags and Ranges in the
54 Lightweight Directory Access Protocol (LDAP).
58 Zeilenga Language Tags and Ranges in LDAP [Page 1]
60 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-01.txt 1 March 2002
65 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
66 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
67 document are to be interpreted as described in BCP 14 [RFC2119].
70 1. Background and Intended Use
72 The Lightweight Directory Access Protocol (LDAP) [Roadmap] provides a
73 means for clients to interrogate and modify information stored in a
74 distributed directory system. The information in the directory is
75 maintained as attributes of entries. Most of these attributes have
76 syntaxes which are human-readable strings, and it is desirable to be
77 able to indicate the natural language associated with attribute
80 This document describes how language tags and ranges [RFC3066] are
81 carried in LDAP and are to be interpreted by LDAP implementations.
82 All implementations MUST be prepared to accept language tags and
83 ranges in the LDAP protocol.
85 This document replaces RFC 2596. Appendix A summaries changes made
88 Appendix B discusses differences from X.500(1997) "contexts"
91 Appendix A and B are provided for information purposes and are not a
92 normative part of this specification.
94 The remainder of this section provides a summary of Language Tags,
95 Language Ranges, and Attribute Descriptions.
100 Section 2 of BCP 47 [RFC3066] describes the language tag format which
101 is used in LDAP. Briefly, it is a string of ASCII alphabetic
102 characters and hyphens. Examples include "fr", "en-US" and "ja-JP".
103 Language tags are case insensitive. For example, the language tag
104 "en-us" is the same as "EN-US".
106 Section 2 of this document details use of language tags in LDAP.
114 Zeilenga Language Tags and Ranges in LDAP [Page 2]
116 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-01.txt 1 March 2002
119 Section 2.5 of BCP 47 [RFC3066] describes the language ranges.
120 Language ranges are used to specify sets of language tags.
122 A language range matches a language tag if it exactly equals the tag,
123 or if it exactly equals a prefix of the tag such that the first
124 character following the prefix is "-". The special tag "*" matches
127 Due to restrictions upon option naming in LDAP, this document uses a
128 different language range syntax. However, the semantics of language
129 ranges in LDAP is consistent with BCP 47.
131 Section 3 of this document details use of language ranges in LDAP.
134 1.3. Attribute Descriptions
136 This section provides an overview of attributes in LDAP. LDAP
137 attributes are defined in [Models].
139 An attribute consists of a type, a set of zero or more associated
140 tagging options, and a set of one or more values. The type and the
141 options are combined into the AttributeDescription.
142 AttributeDescriptions can also contain options which are not part of
143 the attribute, but indicate some other function such as the transfer
146 An attribute with one or more tagging options is a direct subtype of
147 each attribute of the same with all but one of the tagging options.
148 If the attribute's type is a direct subtype of some other type, then
149 the attribute is also a direct subtype of the attribute whose
150 description consists of the the supertype and all of the tagging
151 options. That is, CN;x-bar;x-foo is a direct subtype of CN;x-bar,
152 CN;x-foo, and name;x-bar;x-foo. Note that CN is a subtype of name.
154 If the attribute description contains an unrecognized option, the
155 attribute description is treated as an unrecognized attribute type.
157 As language tags are intended to stored with the attribute, they are
158 to treated as tagging options as described in Section 2. Language
159 range are used only to match against language ranges and are not
160 stored with the attribute. They are not treated tagging options (nor
161 as transfer options), but as described in Section 3.
164 2. Use of Language Tags in LDAP
166 This section describes how LDAP implementations MUST interpret
170 Zeilenga Language Tags and Ranges in LDAP [Page 3]
172 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-01.txt 1 March 2002
175 language tags in performing operations.
177 Servers which support storing attributes with language tag options in
178 the Directory Information Tree (DIT) SHOULD allow any attribute type
179 it recognizes that has the Directory String, IA5 String, or other
180 textual string syntax to have language tag options associated with it.
181 Servers MAY allow language options to be associated with other
184 Clients SHOULD NOT assume servers are capable of storing attributes
185 with language tags in the directory.
187 Implementations MUST NOT otherwise interpret the structure of the tag
188 when comparing two tag, and MUST treat them simply as strings of
189 characters. Implementations MUST allow any arbitrary string which
190 conforms to the syntax defined in BCP 47 [RFC3066] to be used as a
194 2.1. Language Tag Options
196 A language tag option associates a natural language with values of an
197 attribute. An attribute description MAY contain multiple language tag
198 options. An entry MAY contain multiple attributes with same attribute
199 type but different combinations of language tag (and other) options.
201 A language tag option conforms to the following ABNF [RFC2234]:
203 language-tag-option = "lang-" Language-Tag
205 where the Language-Tag production is as defined in BCP 47 [RFC3066].
206 This production and those it imports from [RFC2234] are provided here
209 Language-Tag = Primary-subtag *( "-" Subtag )
211 Primary-subtag = 1*8ALPHA
213 Subtag = 1*8(ALPHA / DIGIT)
215 ALPHA = %x41-5A / %x61-7A ; A-Z / a-z
217 DIGIT = %x30-39 ; 0-9
219 A language tag option is a tagging option [Models]. A language tag
220 option has no effect on the syntax of the attribute's values nor their
226 Zeilenga Language Tags and Ranges in LDAP [Page 4]
228 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-01.txt 1 March 2002
231 Examples of valid AttributeDescription:
235 SN;lang-de;lang-gem-PFL
236 O;lang-i-klingon;x-foobar
240 Notes: The last two have no language tag options. The x-foobar option
241 is fictious and used for example purposes.
246 If language tag options are present in an AttributeDescription in an
247 assertion, then for each entry within scope, the values of each
248 attribute whose AttributeDescription consists of the same attribute
249 type or its subtypes and contains each of the presented (and possibly
250 other) options is to be matched.
252 Thus for example a filter of an equality match of type
253 "name;lang-en-US" and assertion value "Billy Ray", against the
254 following directory entry
256 dn: SN=Ray,DC=example,DC=com
257 objectclass: top DOES NOT MATCH (wrong type)
258 objectclass: person DOES NOT MATCH (wrong type)
259 name;lang-en-US: Billy Ray MATCHES
260 name;lang-en-US: Billy Bob DOES NOT MATCH (wrong value)
261 CN;lang-en-US: Billy Ray MATCHES
262 CN;lang-en-US;x-foobar: Billy Ray MATCHES
263 CN;lang-en;x-foobar: Billy Ray DOES NOT MATCH (differing lang-)
264 CN;x-foobar: Billy Ray DOES NOT MATCH (no lang-)
265 name: Billy Ray DOES NOT MATCH (no lang-)
266 SN;lang-en-GB;lang-en-US: Billy Ray MATCHES
267 SN: Ray DOES NOT MATCH (no lang-,
270 (Note that "CN" and "SN" are subtypes of "name".)
272 It is noted that providing a language tag option in a search filter
273 AttributeDescription will filter out desirable values where the tag
274 does not match exactly. For example, the filter (name;lang-en=Billy
275 Ray) does NOT match the attribute "name;lang-en-US: Billy Ray".
277 If the server does not support storing attributes with language tag
278 options in the DIT, then any assertion which includes a language tag
282 Zeilenga Language Tags and Ranges in LDAP [Page 5]
284 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-01.txt 1 March 2002
287 option will not match as such it is an unrecognized attribute type.
288 No error would be returned because of this; a presence assertion would
289 evaluate to FALSE and all other assertions to Undefined.
291 If no options are specified in the assertion, then only the base
292 attribute type and the assertion value need match the value in the
295 Thus for example a filter of an equality match of type "name" and
296 assertion value "Billy Ray", against the following directory entry
298 dn: SN=Ray,DC=example,DC=net
299 objectclass: top DOES NOT MATCH (wrong type)
300 objectclass: person DOES NOT MATCH (wrong type)
301 name;lang-en-US: Billy Ray MATCHES
302 name;lang-en-US: Billy Bob DOES NOT MATCH (wrong value)
303 CN;lang-en-US;x-foobar: Billy Ray MATCHES
304 CN;lang-en;x-foobar: Billy Ray MATCHES
305 CN;x-foobar: Billy Ray MATCHES
306 name: Billy Ray MATCHES
307 SN;lang-en-GB;lang-en-US: Billy Ray MATCHES
308 SN: Ray DOES NOT MATCH (wrong value)
311 2.3. Requested Attributes in Search
313 Clients can provide language tag options in AttributeDescription in
314 the requested attribute list in a search request.
316 If language tag options are provided in an attribute description, then
317 only attributes in a directory entry whose attribute descriptions have
318 the same attribute type or its subtype and the provided language tags
319 options are to be returned. Thus if a client requests just the
320 attribute "name;lang-en", the server would return "name;lang-en" and
321 "CN;lang-en;lang-ja" but not "SN" nor "name;lang-fr".
323 Clients can provide in the attribute list multiple
324 AttributeDescription which have the same base attribute type but
325 different options. For example a client could provide both
326 "name;lang-en" and "name;lang-fr", and this would permit an attribute
327 with either language tag option to be returned. Note there would be
328 no need to provide both "name" and "name;lang-en" since all subtypes
329 of name would match "name".
331 If a server does not support storing attributes with language tag
332 options in the DIT, then any attribute descriptions in the list which
333 include language tag options are to be ignored, just as if they were
334 unknown attribute types.
338 Zeilenga Language Tags and Ranges in LDAP [Page 6]
340 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-01.txt 1 March 2002
343 If a request is made specifying all attributes or an attribute is
344 requested without providing a language tag option, then all attribute
345 values regardless of their language tag option are returned.
347 For example, if the client requests a "description" attribute, and a
348 matching entry contains the following attributes:
351 objectclass: organization
353 description: software
354 description;lang-en: software products
355 description;lang-de: Softwareprodukte
356 postalAddress: Berlin 8001 Germany
357 postalAddress;lang-de: Berlin 8001 Deutschland
359 The server would return:
361 description: software
362 description;lang-en: software products
363 description;lang-de: Softwareprodukte
368 Language tag options can be present in an AttributeDescription used in
369 a compare request AttributeValueAssertion. This is to be treated by
370 servers the same as the use of language tag options in a search filter
371 with an equality match, as described in Section 2.2. If there is no
372 attribute in the entry with the same subtype and language tag options,
373 the noSuchAttributeType error will be returned.
375 Thus for example a compare request of type "name" and assertion value
376 "Johann", against an entry containing the following attributes:
380 givenName;lang-de-DE: Johann
384 would cause the server to return compareTrue.
386 However, if the client issued a compare request of type "name;lang-de"
387 and assertion value "Johann" against the above entry, the request
388 would fail with the noSuchAttributeType error.
390 If the server does not support storing attributes with language tag
394 Zeilenga Language Tags and Ranges in LDAP [Page 7]
396 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-01.txt 1 March 2002
399 options in the DIT, then any comparison which includes a language tag
400 option will always fail to locate an attribute, and
401 noSuchAttributeType will be returned.
406 Clients can provide language options in AttributeDescription in
407 attributes of a new entry to be created.
409 A client can provide multiple attributes with the same attribute type
410 and value, so long as each attribute has a different set of language
413 For example, the following is a legal request.
415 dn: CN=John Smith,DC=example,DC=com
418 objectclass: residentialPerson
421 CN;lang-en: John Smith
423 SN;lang-en;lang-en-US: Smith
424 streetAddress: 1 University Street
425 streetAddress;lang-en: 1 University Street
426 streetAddress;lang-fr: 1 rue Universite
427 houseIdentifier;lang-fr: 9e etage
429 If a server does not support storing language tag options with
430 attribute values in the DIT, then it MUST treat an
431 AttributeDescription with a language tag option as an unrecognized
432 attribute. If the server forbids the addition of unrecognized
433 attributes then it MUST fail the add request with an appropriate
437 2.6. Modify Operation
439 A client can provide language tag options in an AttributeDescription
440 as part of a modification element in the modify operation.
442 Attribute types and language tag options MUST match exactly against
443 values stored in the directory. For example, if the modification is a
444 "delete", then if the stored values to be deleted have language tag
445 options, then those language tag options MUST be provided in the
446 modify operation, and if the stored values to be deleted do not have
450 Zeilenga Language Tags and Ranges in LDAP [Page 8]
452 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-01.txt 1 March 2002
455 any language tag option, then no language tag option is to be
458 If the server does not support storing language tag options with
459 attribute values in the DIT, then it MUST treat an
460 AttributeDescription with a language tag option as an unrecognized
461 attribute, and MUST fail the request with an appropriate result code.
464 3. Use of Language Ranges in LDAP
466 Since the publication of RFC 2596, it has become apparent that there
467 is a need to provide a mechanism for a client to request attributes
468 based upon set of language tag options whose tags all begin with the
469 same sequence of language sub-tags.
471 AttributeDescriptions containing language range options are intended
472 to be used in attribute value assertions, search attribute lists, and
473 other places where the client desires to provide an attribute
474 description matching of a range of language tags associated with
477 A language range option conforms to the following ABNF [RFC2234]:
479 language-range-option = "lang-" [ Language-Tag "-" ]
481 where the Language-Tag production is as defined in BCP 47 [RFC3066].
482 This production and those it imports from [RFC2234] are provided here
485 Language-Tag = Primary-subtag *( "-" Subtag )
487 Primary-subtag = 1*8ALPHA
489 Subtag = 1*8(ALPHA / DIGIT)
491 ALPHA = %x41-5A / %x61-7A ; A-Z / a-z
493 DIGIT = %x30-39 ; 0-9
495 A language range option matches a language tag option if language
496 range option less the trailing "-" matches exactly the language tag or
497 if the language range option (including the trailing "-") matches a
498 prefix of the language tag option. Note that the language range
499 option "lang-" matches all language tag options.
501 Examples of valid AttributeDescription containing language range
506 Zeilenga Language Tags and Ranges in LDAP [Page 9]
508 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-01.txt 1 March 2002
515 A language range option is not a tagging option. Attributes cannot be
516 stored with language range options. Any attempt to add or update an
517 attribute description with a language range option SHALL be treated as
518 an undefined attribute type and result in an error.
520 A language range option has no effect on the transfer encoding nor on
521 the syntax of the attribute values.
523 Servers SHOULD support assertion of language ranges for any attribute
524 which they allow to stored with language tags.
529 If a language range option is present in an AttributeDescription in an
530 assertion, then for each entry within scope, the values of each
531 attribute whose AttributeDescription consists of the same attribute
532 type or its subtypes and contains a language tag option matching the
533 language range option are to be returned.
535 Thus for example a filter of an equality match of type "name;lang-en-"
536 and assertion value "Billy Ray", against the following directory entry
538 dn: SN=Ray,DC=example,DC=com
539 objectclass: top DOES NOT MATCH (wrong type)
540 objectclass: person DOES NOT MATCH (wrong type)
541 name;lang-en-US: Billy Ray MATCHES
542 name;lang-en-US: Billy Bob DOES NOT MATCH (wrong value)
543 CN;lang-en-US: Billy Ray MATCHES
544 CN;lang-en-US;x-foobar: Billy Ray MATCHES
545 CN;lang-en;x-foobar: Billy Ray MATCHES
546 CN;x-foobar: Billy Ray DOES NOT MATCH (no lang-)
547 name: Billy Ray DOES NOT MATCH (no lang-)
548 SN;lang-en-GB;lang-en-US: Billy Ray MATCHES
549 SN: Ray DOES NOT MATCH (no lang-,
552 (Note that "CN" and "SN" are subtypes of "name".)
554 If the server does not support storing attributes with language tag
555 options in the DIT, then any assertion which includes a language range
556 option will not match as it is an unrecognized attribute type. No
557 error would be returned because of this; a presence filter would
558 evaluate to FALSE and all other assertions to Undefined.
562 Zeilenga Language Tags and Ranges in LDAP [Page 10]
564 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-01.txt 1 March 2002
567 3.2. Requested Attributes in Search
569 Clients can provide language range options in AttributeDescription in
570 the requested attribute list in a search request.
572 If a language range option is provided in an attribute description,
573 then only attributes in a directory entry whose attribute descriptions
574 have the same attribute type or its subtype and a language tag option
575 matching the provided language range option are to be returned. Thus
576 if a client requests just the attribute "name;lang-en-", the server
577 would return "name;lang-en-US" and "CN;lang-en;lang-ja" but not "SN"
580 Clients can provide in the attribute list multiple
581 AttributeDescription which have the same base attribute type but
582 different options. For example a client could provide both
583 "name;lang-en-" and "name;lang-fr-", and this would permit an
584 attribute whose type was name or subtype of name and with a language
585 tag option matching either language range option to be returned.
587 If a server does not support storing attributes with language tag
588 options in the DIT, then any attribute descriptions in the list which
589 include language range options are to be ignored, just as if they were
590 unknown attribute types.
595 Language range options can be present in an AttributeDescription used
596 in a compare request AttributeValueAssertion. This is to be treated
597 by servers the same as the use of language range options in a search
598 filter with an equality match, as described in Section 3.1. If there
599 is no attribute in the entry with the same subtype and a matching
600 language tag option, the noSuchAttributeType error will be returned.
602 Thus for example a compare request of type "name;lang-" and assertion
603 value "Johann", against the entry with the following attributes:
607 givenName;lang-de-DE: Johann
611 will cause the server to return compareTrue. (Note that the language
612 range option "lang-" matches any language tag option.)
614 However, if the client issued a compare request of type "name;lang-de"
618 Zeilenga Language Tags and Ranges in LDAP [Page 11]
620 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-01.txt 1 March 2002
623 and assertion value "Sibelius" against the above entry, the request
624 would fail with the noSuchAttributeType error.
626 If the server does not support storing attributes with language tag
627 options in the DIT, then any comparison which includes a language
628 range option will always fail to locate an attribute, and
629 noSuchAttributeType will be returned.
632 4. Discovering Language Option Support
634 A server SHOULD indicate that it supports storing attributes with
635 language tag options in the DIT by publishing OID.TDB as a value of
636 the supportedFeatures [FEATURES] attribute in the root DSE.
638 A server SHOULD indicate that it supports language range matching of
639 attributes with language tag options stored in the DIT by publishing
640 OID.TDB as a value of the supportedFeatures [FEATURES] attribute in
643 A server MAY restrict use of language tag options to a subset of the
644 attribute types it recognizes. This document does not define a
645 mechanism for determining which subset of attribute types can be used
646 with language tag options.
649 5. Security Considerations
651 Language tags and range options are used solely to indicate the native
652 language of values and in querying the directory for values which
653 fulfill the user's language needed. These options are not known to
654 raise specific security considerations. However, the reader should
655 consider general directory security issues detailed in the LDAP
656 technical specification [Roadmap].
661 This document is a revision of RFC 2596 by Mark Wahl and Tim Howes.
662 RFC 2596 was a product of the IETF ASID and LDAPEXT working groups.
664 This document borrows from a number of IETF documents including BCP
668 7. Normative References
670 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
674 Zeilenga Language Tags and Ranges in LDAP [Page 12]
676 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-01.txt 1 March 2002
679 Requirement Levels", BCP 14 (also RFC 2119), March 1997.
681 [RFC2234] D. Crocker, P. Overell, "Augmented BNF for Syntax
682 Specifications: ABNF", RFC 2234, November 1997.
684 [RFC3066] Alvestrand, H., "Tags for the Identification of Languages",
685 BCP 47 (also RFC 3066), January 2001.
687 [Roadmap] K. Zeilenga (editor), "LDAP: Technical Specification Road
688 Map", draft-ietf-ldapbis-roadmap-xx.txt, a work in
691 [Models] K. Zeilenga (editor), "LDAP: Directory Information Models",
692 draft-ietf-ldapbis-models-xx.txt, a work in progress.
694 [FEATURES] K. Zeilenga, "Feature Discovery in LDAP",
695 draft-zeilenga-ldap-features-xx.txt (a work in progress).
698 8. Informative References
700 [X.501] "The Directory: Models", ITU-T Recommendation X.501, 1997.
703 Appendix A. Differences from RFC 2596
705 This document adds support for language ranges, provides a mechanism
706 that a client can use to discover whether a server supports language
707 tags and ranges, and clarifies how attributes with multiple language
708 tags are to be treated. This document is a significant rewrite of RFC
712 Appendix B. Differences from X.500(1997)
714 X.500(1997) [X.501] defines a different mechanism, contexts, as the
715 means of representing language tags (codes). This section summarizes
716 the major differences in approach.
718 a) An X.500 operation which has specified a language code on a value
719 matches a value in the directory without a language code.
720 b) LDAP references BCP 47 [RFC3066], which allows for IANA
721 registration of new tags as well as unregistered tags.
722 c) LDAP supports language ranges.
723 d) LDAP does not allow language tags (and ranges) in distinguished
725 e) X.500 describes subschema administration procedures to allow
726 language codes to be associated with particular attributes types.
730 Zeilenga Language Tags and Ranges in LDAP [Page 13]
732 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-01.txt 1 March 2002
735 Copyright 2002, The Internet Society. All Rights Reserved.
737 This document and translations of it may be copied and furnished to
738 others, and derivative works that comment on or otherwise explain it
739 or assist in its implementation may be prepared, copied, published and
740 distributed, in whole or in part, without restriction of any kind,
741 provided that the above copyright notice and this paragraph are
742 included on all such copies and derivative works. However, this
743 document itself may not be modified in any way, such as by removing
744 the copyright notice or references to the Internet Society or other
745 Internet organizations, except as needed for the purpose of
746 developing Internet standards in which case the procedures for
747 copyrights defined in the Internet Standards process must be followed,
748 or as required to translate it into languages other than English.
750 The limited permissions granted above are perpetual and will not be
751 revoked by the Internet Society or its successors or assigns.
753 This document and the information contained herein is provided on an
754 "AS IS" basis and THE AUTHORS, THE INTERNET SOCIETY, AND THE INTERNET
755 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
756 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
757 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
758 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
786 Zeilenga Language Tags and Ranges in LDAP [Page 14]