Data Model Incompatibility Differing Data Type Facets List Transformations

Mapping Connector Fields to Hub Fields 8-9 address lines. Although this does not necessarily mean that data loss can occur, special transformation processing may be necessary to prevent data loss.

8.3.4 Record Collisions

The types of record collisions that result in data loss are as follows: ■ Engine Merge Collision: The collisions that occur when the Engine merges changes from multiple records can cause the loss of data for the record that does not win the collision merge competition. ■ Connector PIM Collision: The collisions that occur when a connector writes changes to a PIM Server that conflict with new PIM record changes can cause data loss. At some point, a change is overwritten, resulting in a loss of data. 8-10 Administrators Guide for Oracle Business Data Synchronization Server 9 Synchronizing the Calendar Domain 9-1 9 Synchronizing the Calendar Domain This chapter describes how BDSS synchronizes Calendar domain records. This chapter includes the following topics: ■ Overview of Calendar Synchronization Support ■ Transforming Custom Calendar Fields ■ Supporting Calendar Synchronization in Hub Schema ■ Creating Custom Calendar Fields ■ Data Side Effects Caused by Synchronizing ICAL Fields

9.1 Overview of Calendar Synchronization Support

With the exception of the record data format- and attendee-related processing, the Calendar domain synchronizes in the same way as any other domains. However, the record data format for the Calendar domain is different than the record data format of other domains. That is, the other domains represent a domain record as a XML document where each field of the record is represented as a node in the XML document. For the Hub Calendar domain, a record is still a XML document, but instead of each field being a separate node in the document, there is a single node whose value is a iCalendar ICAL message see RFC 2445: Internet Calendaring and Scheduling Core Object Specification, located at http:www.ietf.orgrfcrfc2445.txt. The embedded ICalendar message contains the individual field names and values.

9.1.1 Transforming Calendar Records

The Hub Calendar domain has only one field, ICalBody. The value for ICalBody is VCALENDAR content that conforms to RFC 2445. The Hub-to-PIM and PIM-to-Hub XSL files map this field. Example 9–1 Hub XML ?xml version=1.0 encoding=windows-1252 ? xsd:schema xmlns:xsd=http:www.w3.org2001XMLSchema Note: While ICAL is the widely accepted standard for exchanging calendar data, it is not defined in terms of XML and, to date, there are no standards that map ICAL-to-XML see the IETF draft for XCAL at http:www.ietf.orgold2009proceedings02marI-Dd raft-ietf-calsch-many-xcal-01.txt .