/** Interface representing a snapshot of a time zone entity. OCS Time Zone Service will rely on the time zone definitions provided by the public domain "TZ Database[TZDB]" maintained at the National Institute of Health (NIH) by Arthur David Olson. The "TZ Database" is the most up to date and reliable source of information for time zone information. The database can be access at this link.

A time zone is a geographical region within which the same local time is used.

• TimeZoneRule: A TimeZone node defines all the rules that defines the transition between standard time and daylight saving time and vice versa. A time zone have at least one time zone rule.
• Name: The Name attribute of TimeZone entity will be set to the TZ Database timezone identifier (e.g., America/Los_Angeles).
• CountryCode: The CountryCode attribute specifies the upper-case, two-letter country code as defined by [ISO-3166]
• Aliases: The TimeZone node defines the aliases used for this particular time zone in different namespaces (e.g., for time zone "America/NewYork", its alias name is "America/NewYork" in the TZDB namespace, "Eastern Standard Time" in Microsoft Windows [MSFT] namespace). A TimeZone may have only one alias per namespace.
• Coordinates: Defines the longitude and latitude of this time zone.

The following attributes are part of the BASIC projection: CollabId, Name, ModifiedOn, TimeZone Rules.

There are also some methods provided by this interface.

• getHandle() It will return a TimeZoneHandle, which is a pointer to the underlying TimeZone object. The load() operation of the handle will return this TimeZone object to which the handle referred.
• getTimeZoneRule(Date) Given a UTC date time, it will return the TimeZoneRule that takes effect on this given date.
• getUTCOffsetRaw(Date) Given a UTC date time, it will return the UTCOffsetRaw for the given date in this time zone.

Below are examples in JSON and XML formats. All examples are shown with all inherited members. Quoting when required is part of the examples, but you must obviously populate with your own data.

<xs:complexType name="timeZone">
    <xs:complexContent>
        <xs:extension base="tns:entity">
            <xs:sequence>
                <xs:element maxOccurs="unbounded" minOccurs="0"
                    name="aliases" nillable="true" type="tns:timeZoneAlias"/>
                <xs:element maxOccurs="unbounded" minOccurs="0"
                    name="bonds" nillable="true" type="tns:bond"/>
                <xs:element name="common" type="xs:boolean"/>
                <xs:element minOccurs="0" name="coordinates" type="tns:coordinates"/>
                <xs:element minOccurs="0" name="countryCode" type="xs:string"/>
                <xs:element name="defaultCommon" type="xs:boolean"/>
                <xs:element maxOccurs="unbounded" minOccurs="0"
                    name="rules" nillable="true" type="tns:timeZoneRule"/>
            </xs:sequence>
        </xs:extension>
    </xs:complexContent>
</xs:complexType>

        

The following data represents the references to timeZone