September 2025

This month's highlights:

✓ Country name formatting standardized (including Marriott’s special adjustment).

✓ Context code recognition changed from case-sensitive to case-insensitive.

✓ Mandatory 2-decimal-place precision for policy-related numerical data.

✓ Spoken language data inconsistencies fixed (default value, format, value loss).

✓ U.S. state name processing logic updated from V3 standards.

✓ Facility content mapping optimized (reuse + exception handling).

Country Name Format Standardization

| Update | Country Name Format 

Standardization of country name formatting is implemented to ensure global consistency.

• Adjustment Rule: Shortened/non-standard country names are converted to full standard names (e.g., "USA" → "United States of America").
  If the country name is blank, the system will fill according to the country code.
• Special Case: Marriott’s country name has no multiple variants but did not comply with the new standard—now updated to align with the full standard format.

Context Code Sensitivity Adjustment

| Update | Context Code Recognition

Context code handling is updated from case-sensitive to case-insensitive to simplify data processing.

• Values with different letter cases (e.g., "Code1" and "code1") are now recognized as identical.

Tips: We recommend using all upper-case.

Policy Compliance

| New | Policy-Related Numerical Precision 

A mandatory specification is introduced: All policy-related numerical data (e.g., pricing, tax values) must maintain a precision of 2 decimal places (formatted as "XX.XX").

• Existing unstandardized data (e.g., "200", "35.5") will be auto-converted to 2 decimal places during migration.
• Ensures consistency across policy calculations and reporting.

Language Data

| Fixed | Spoken Language Data Consistency

Key inconsistencies in spoken language data are resolved to align DistributorAPI and GHR.

• Resolved Issues:
  1. Default Return Value Mismatch: DistributorAPI currently returns PrimaryLangInd="false" by default; while GHR has no corresponding data for this field.
  2. Inconsistent Language Values: Discrepancies in format (e.g., "EN-US" vs. "English") are fixed, and critical values (e.g., Language.3.Code="FR-FR") are no longer lost.
• Reference Standard: Official spoken language guide: https://content-nexus.derbysoftsec.com/content-collection-service/objects?key=/content/collection/adapter/standard/library/spoken_languages.json
• Example:

  <Languages>
    <Language Language="Bosnian" PrimaryLangInd="false"/>
    <Language Language="English" PrimaryLangInd="false"/>
    <Language Language="Spanish" PrimaryLangInd="false"/>
    <Language Language="German" PrimaryLangInd="false"/>
  </Languages>

Location Data

| Update | U.S. State Name Processing

U.S. state name handling is revised—V3 previously applied special processing for U.S. state names; this logic is updated to align with migration standards.

• V3-specific special tags are removed; state names are now stored as full standard names.

Content Mapping

| Update | Meeting Room/Restaurant Content Mapping 

Facility content mapping is optimized for consistency, with reuse logic and exception handling.

• Content Reuse: The system reuses existing meeting room/restaurant content for applicable hotels.
• Mapping Exception: If mapping fails, content is assigned to the hotel-level (instead of individual facility-level).
• Example