rfc2596.txt

RFC 的详细文档！

   matching entry contains

   objectclass: top
   objectclass: organization
   O: Software GmbH
   description: software
   description;lang-en: software products
   description;lang-de: Softwareprodukte
   postalAddress: Berlin 8001 Germany
   postalAddress;lang-de: Berlin 8001 Deutschland

   The server will return:

   description: software
   description;lang-en: software products
   description;lang-de: Softwareprodukte

3.6. Add Operation

   Clients MAY provide language codes in AttributeDescription in
   attributes of a new entry to be created, subject to the limitation
   that the client MUST NOT use language codes in the attribute value or
   values which form the RDN of the entry.




Wahl & Howes                Standards Track                     [Page 5]

RFC 2596             Use of Language Codes in LDAP              May 1999


   A client MAY provide multiple attributes with the same attribute type
   and value, so long as each attribute has a different language code,
   and at most one attribute does not have a language code option.

   Servers which support storing language codes in the DIT MUST allow
   any attribute it recognizes that has the Directory String syntax to
   have a language option associated with it. Servers SHOULD allow
   language options to be associated with other attributes.

   For example, the following is a legal request.

   objectclass: top
   objectclass: person
   objectclass: residentialPerson
   name: John Smith
   CN: John Smith
   CN;lang-en: John Smith
   SN: Smith
   streetAddress: 1 University Street
   streetAddress;lang-en: 1 University Street
   streetAddress;lang-fr: 1 rue Universite
   houseIdentifier;lang-fr: 9e etage

   If a server does not support storing language codes with attribute
   values in the DIT, then it MUST treat an AttributeDescription with a
   language code as an unrecognized attribute. If the server forbids the
   addition of unrecognized attributes then it MUST fail the add request
   with the appropriate result code.

3.7. Modify Operation

   A client MAY provide a language code in an AttributeDescription as
   part of a modification element in the modify operation.

   Attribute types and language codes MUST match exactly against values
   stored in the directory.  For example, if the modification is a
   "delete", then if the stored values to be deleted have a language
   code, the language code MUST be provided in the modify operation, and
   if the stored values to be deleted do not have a language code, then
   no language code is to be provided.

   If the server does not support storing language codes with attribute
   values in the DIT, then it MUST treat an AttributeDescription with a
   language code as an unrecognized attribute, and MUST fail the request
   with an appropriate result code.






Wahl & Howes                Standards Track                     [Page 6]

RFC 2596             Use of Language Codes in LDAP              May 1999


3.8. Diagnostic Messages

   Servers SHOULD use only printable ASCII characters in the
   errorMessage field, as not all clients will be able to display the
   full range of Unicode.

4. Differences from X.500(1997)

   X.500(1997) defines a different mechanism, contexts, as the means of
   representing language tags.  This section summarizes the major
   differences in approach.

   a) An X.500 operation which has specified a language code on a value
      matches a value in the directory without a language code.
   b) LDAP references RFC 1766, which allows for IANA registration of
      new tags.
   c) LDAP does not allow language codes in distinguished names.
   d) X.500 describes subschema administration procedures to allow
      language codes to be associated with particular attributes types.

5. Security Considerations

   There are no known security considerations for this document.  See
   the security considerations sections of [1] and [2] for security
   considerations of LDAP in general.

6. Acknowledgements

   This document is a product of the IETF ASID and LDAPEXT working
   groups.  Martin Duerst provided many valuable comments on an earlier
   version of this document.

7. Bibliography

   [1] Wahl, M., Howes, T. and S. Kille, "Lightweight Directory Access
       Protocol (v3)", RFC 2251, December 1997.

   [2] Wahl, M., Coulbeck, A., Howes, T. and S. Kille, "Lightweight
       X.500 Directory Access Protocol Attribute Syntax Definitions",
       RFC 2252, December 1997.

   [3] Alvestrand, H.,"Tags for the Identification of Languages", RFC
       1766, March 1995.

   [4] Bradner, S., "Key words for use in RFCs to Indicate Requirement
       Levels", BCP 14, RFC 2119, March 1997.





Wahl & Howes                Standards Track                     [Page 7]

RFC 2596             Use of Language Codes in LDAP              May 1999


8. Authors' Addresses

   Mark Wahl
   Innosoft International, Inc.
   8911 Capital of Texas Hwy Suite 4140
   Austin, TX 78759 USA

   EMail:  [e-mail]


   Tim Howes
   Netscape Communications Corp.
   501 E. Middlefield Rd
   Mountain View, CA 94043 USA

   Phone:  [phone]
   EMail:   [e-mail]


































Wahl & Howes                Standards Track                     [Page 8]

RFC 2596             Use of Language Codes in LDAP              May 1999


Full Copyright Statement

   Copyright (C) The Internet Society (1999).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Wahl & Howes                Standards Track                     [Page 9]