Overview of Data Transformation

Mapping Connector Fields to Hub Fields 8-3 ■ xsd:nonNegativeInteger ■ xsd:unsignedLong ■ xsd:positiveInteger

8.2.1.2 Hub Schema Data Types

Hub domains are constructed using W3C schema data types. Note: Because xsd:dateTime generally allows the ISO 8601 date and time representations, all varieties of date and time can be specified in standard coordinated universal time UTC. All date and time Hub fields that are passed between the Engine and the connector must: 1. Be in UTC time and in the format of YYYY-MM-DDhh:mm:ss.fff. In this format: ■ YYYY is the 4 digit year, such as 2007. ■ MM is the month January is 01 and December is 12. ■ DD is the day of the month starting from 01. ■ hh is the hour of day in 24-hour clock time 00 through 23, inclusive. ■ mm is the minute of the hour 00 through 59, inclusive ■ ss is the second of the minute 00 through 59, inclusive. ■ fff are fractional seconds that is, milliseconds—000 through 999, inclusive. 2. All datetime PIM field values have a corresponding UTC offset field in the format of +HH:MM or -HH:MM: ■ + indicates a positive UTC offset. ■ - indicates a negative UTC offset. ■ HH is the UTC offset hour in 24-hour clock time 00 through 23, inclusive. ■ MM is the UTC offset minute 00 through 59, inclusive. By providing both the UTC date-time and UTC offset for each of the PIM date-time fields, a receiving connector can calculate a local time if the PIM server uses local time or it can use the UTC date-time if the PIM server uses UTC date-time for the field. 8-4 Administrators Guide for Oracle Business Data Synchronization Server Hub-Defined Data Types In addition to the native W3C XML Schema WXS data types, BDSS provides the XSDs for such common PIM data types as phone numbers and addresses. These data types have only basic restrictions. For example, HubPhoneNumber is restricted to a simple string, as illustrated in Example 8–1 . Example 8–1 Predefined Restrictions to a Hub-Defined Data Type ?xml version=1.0 encoding=windows-1252 ? xsd:schema xmlns:xsd=http:www.w3.org2001XMLSchema xmlns=http:xmlns.oracle.compsshubContactDomain elementFormDefault=qualified xsd:simpleType name=HubPhoneNumber xsd:restriction base=xsd:stringxsd:restriction xsd:simpleType xsd:schema Although BDSS does not define other restrictions, you can define more elaborate restrictions, if needed. The bold font in Example 8–2 illustrates additional restrictions to the length and format of the HubPhoneNumber data type. Example 8–2 Additional Restrictions to a Hub-Defined Data Type ?xml version=1.0 encoding=windows-1252 ? xsd:schema xmlns:xsd=http:www.w3.org2001XMLSchema xmlns=http:xmlns.oracle.compsshubContactDomain elementFormDefault=qualified xsd:simpleType name=HubPhoneNumber xsd:restriction base=xsd:stringxsd:restriction xsd:pattern value=[0-9]{0,2}\[0-9]{3}\[0-9]{3}\-[0-9]{4} Ext:[0-9]{4}? xsd:simpleType xsd:schema The Hub-defined data types include: ■ xsd:HubPercent ■ xsd:HubUnsignedLong ■ xsd:HubTokens ■ xsd:HubUtcOffest ■ xsd:HubPhoneNumber ■ xsd:HubAddress ■ xsd:HubState ■ xsd:HubCountry ■ xsd:HubEmailAddress ■ xsd:HubNamePrefix Caution: If you alter the Hub schemas or Hub schema data types, you must also make corresponding changes to the XSLT documents for each connector. The XSLT documents must change to ensure proper transformation between the Hub and PIM schema representations.