D.1 Overview of Custom Field Transformations

You can add custom fields to a set of XSDs that are not exposed to the Hub using the secondary translation method. To enable the Exchange 2007 Connector to synchronize with the Hub, you must create the following XSD files:

An XSD file that defines the custom field definitions for the Exchange 2007 Connector

An XSD file that defines the ICAL counterparts of the field definitions

An XSLT file that transforms the Exchange 2007 Field definitions into ICAL definitions

An XSLT file that transforms the ICAL field definitions into Exchange 2007 definitions

These files are considered secondary files because they are never exposed to the Hub. To enable the Exchange 2007 Connector to synchronize these fields, these XSD files are mapped to secondary XSL files.

D.5 Mapping Windows Time Zones to Java-Standard Time Zones

Example D-5 illustrates an the XSD that maps Microsoft Windows time zones to Java-standard time zones when building Hub Calendar records. Example D-6 illustrates the XLST file that transforms the time zone mappings.