Procedures for OpenTravel Code List Updates

The following procedures are to be used by OpenTravel members who would like a new code added to the existing code list. Non-members should submit a comment via the OpenTravel specification comment form available on www.opentravel.org.

1. Send an e-mail to the appropriate workgroup distribution list, providing the following information:
   • The code list name (e.g., Address Use Type)
   • The code list 3-letter code (e.g., AUT)
   • The new code name (the actual code value will be assigned later by the code list manager) (e.g., Weekdays)
   • The OpenTravel message and element path where the new code is to be used (e.g., OTA_PkgBookRQ/ContactDetail/Address/@Type)
   • The reason for the new code, if it is not apparent (this item is optional)
2. Allow two weeks for questions and comments from the workgroup. At the end of this period if there is agreement on (or no objections to) the codes requested, send the same e-mail requesting the codes to the code list manager (codelist@opentravel.org), copying the workgroup mailing list indicating that there have been no objections.
3. The code list manager will review the request and, if there are no issues, assign a code value to the new code and distribute the new codes to the member requesting the code. If there is an issue (e.g., a code seems to already exist for the requested code), the code list manager may question the request by sending an e-mail to the work group distribution list.
4. The code list manager will update the code list and post a revised version on the OpenTravel wiki. Where possible, initiators should consolidate code requests from their workgroups before submitting them to the code list manager rather than sending individual requests.