/**@class java.time.ZoneId
 implements java.io.Serializable

@extends java.lang.Object

 A time-zone ID, such as {@code Europe/Paris}.
 <p>
 A {@code ZoneId} is used to identify the rules used to convert between
 an {@link java.time.Instant} and a {@link java.time.LocalDateTime}.
 There are two distinct types of ID:
 <ul>
 <li>Fixed offsets - a fully resolved offset from UTC/Greenwich, that uses
  the same offset for all local date-times
 <li>Geographical regions - an area where a specific set of rules for finding
  the offset from UTC/Greenwich apply
 </ul>
 Most fixed offsets are represented by {@link java.time.ZoneOffset}.
 Calling {@link #normalized}() on any {@code ZoneId} will ensure that a
 fixed offset ID will be represented as a {@code ZoneOffset}.
 <p>
 The actual rules, describing when and how the offset changes, are defined by {@link ZoneRules}.
 This class is simply an ID used to obtain the underlying rules.
 This approach is taken because rules are defined by governments and change
 frequently, whereas the ID is stable.
 <p>
 The distinction has other effects. Serializing the {@code ZoneId} will only send
 the ID, whereas serializing the rules sends the entire data set.
 Similarly, a comparison of two IDs only examines the ID, whereas
 a comparison of two rules examines the entire data set.

 <h3>Time-zone IDs</h3>
 The ID is unique within the system.
 There are three types of ID.
 <p>
 The simplest type of ID is that from {@code ZoneOffset}.
 This consists of 'Z' and IDs starting with '+' or '-'.
 <p>
 The next type of ID are offset-style IDs with some form of prefix,
 such as 'GMT+2' or 'UTC+01:00'.
 The recognised prefixes are 'UTC', 'GMT' and 'UT'.
 The offset is the suffix and will be normalized during creation.
 These IDs can be normalized to a {@code ZoneOffset} using {@code normalized()}.
 <p>
 The third type of ID are region-based IDs. A region-based ID must be of
 two or more characters, and not start with 'UTC', 'GMT', 'UT' '+' or '-'.
 Region-based IDs are defined by configuration.
 The configuration focuses on providing the lookup from the ID to the
 underlying {@code ZoneRules}.
 <p>
 Time-zone rules are defined by governments and change frequently.
 There are a number of organizations, known here as groups, that monitor
 time-zone changes and collate them.
 The default group is the IANA Time Zone Database (TZDB).
 Other organizations include IATA (the airline industry body) and Microsoft.
 <p>
 Each group defines its own format for the region ID it provides.
 The TZDB group defines IDs such as 'Europe/London' or 'America/New_York'.
 TZDB IDs take precedence over other groups.
 <p>
 It is strongly recommended that the group name is included in all IDs supplied by
 groups other than TZDB to avoid conflicts. For example, IATA airline time-zone
 region IDs are typically the same as the three letter airport code.
 However, the airport of Utrecht has the code 'UTC', which is obviously a conflict.
 The recommended format for region IDs from groups other than TZDB is 'group~region'.
 Thus if IATA data were defined, Utrecht airport would be 'IATA~UTC'.

 <h3>Serialization</h3>
 This class can be serialized and stores the string zone ID in the external form.
 The {@code ZoneOffset} subclass uses a dedicated format that only stores the
 offset from UTC/Greenwich.
 <p>
 A {@code ZoneId} can be deserialized in a Java Runtime where the ID is unknown.
 For example, if a server-side Java Runtime has been updated with a new zone ID, but
 the client-side Java Runtime has not been updated. In this case, the {@code ZoneId}
 object will exist, and can be queried using {@code getId}, {@code equals},
 {@code hashCode}, {@code toString}, {@code getDisplayName} and {@code normalized}.
 However, any call to {@code getRules} will fail with {@code ZoneRulesException}.
 This approach is designed to allow a {@link java.time.ZonedDateTime} to be loaded and
 queried, but not modified, on a Java Runtime with incomplete time-zone information.

 @implSpec
 This abstract class has two implementations, both of which are immutable and thread-safe.
 One implementation models region-based IDs, the other is {@code ZoneOffset} modelling
 offset-based IDs. This difference is visible in serialization.

 @since 1.8
*/
var ZoneId = {

/** A map of zone overrides to enable the short time-zone names to be used.
 <p>
 Use of short zone IDs has been deprecated in {@code java.util.TimeZone}.
 This map allows the IDs to continue to be used via the
 {@link #of(String, Map)} factory method.
 <p>
 This map contains a mapping of the IDs that is in line with TZDB 2005r and
 later, where 'EST', 'MST' and 'HST' map to IDs which do not include daylight
 savings.
 <p>
 This maps as follows:
 <ul>
 <li>EST - -05:00</li>
 <li>HST - -10:00</li>
 <li>MST - -07:00</li>
 <li>ACT - Australia/Darwin</li>
 <li>AET - Australia/Sydney</li>
 <li>AGT - America/Argentina/Buenos_Aires</li>
 <li>ART - Africa/Cairo</li>
 <li>AST - America/Anchorage</li>
 <li>BET - America/Sao_Paulo</li>
 <li>BST - Asia/Dhaka</li>
 <li>CAT - Africa/Harare</li>
 <li>CNT - America/St_Johns</li>
 <li>CST - America/Chicago</li>
 <li>CTT - Asia/Shanghai</li>
 <li>EAT - Africa/Addis_Ababa</li>
 <li>ECT - Europe/Paris</li>
 <li>IET - America/Indiana/Indianapolis</li>
 <li>IST - Asia/Kolkata</li>
 <li>JST - Asia/Tokyo</li>
 <li>MIT - Pacific/Apia</li>
 <li>NET - Asia/Yerevan</li>
 <li>NST - Pacific/Auckland</li>
 <li>PLT - Asia/Karachi</li>
 <li>PNT - America/Phoenix</li>
 <li>PRT - America/Puerto_Rico</li>
 <li>PST - America/Los_Angeles</li>
 <li>SST - Pacific/Guadalcanal</li>
 <li>VST - Asia/Ho_Chi_Minh</li>
 </ul>
 The map is unmodifiable.
*/
SHORT_IDS : "null",
/**Gets the system default time-zone.
 <p>
 This queries {@link TimeZone#getDefault()} to find the default time-zone
 and converts it to a {@code ZoneId}. If the system default time-zone is changed,
 then the result of this method will also change.
@return {Object {java.time.ZoneId}} the zone ID, not null
@throws DateTimeException if the converted zone ID has an invalid format
@throws ZoneRulesException if the converted zone region ID cannot be found
*/
systemDefault : function(  ) {},

/**Gets the set of available zone IDs.
 <p>
 This set includes the string form of all available region-based IDs.
 Offset-based zone IDs are not included in the returned set.
 The ID can be passed to {@link #of}(String) to create a {@code ZoneId}.
 <p>
 The set of zone IDs can increase over time, although in a typical application
 the set of IDs is fixed. Each call to this method is thread-safe.
@return {Object {java.util.Set}} a modifiable copy of the set of zone IDs, not null
*/
getAvailableZoneIds : function(  ) {},

/**Obtains an instance of {@code ZoneId} using its ID using a map
 of aliases to supplement the standard zone IDs.
 <p>
 Many users of time-zones use short abbreviations, such as PST for
 'Pacific Standard Time' and PDT for 'Pacific Daylight Time'.
 These abbreviations are not unique, and so cannot be used as IDs.
 This method allows a map of string to time-zone to be setup and reused
 within an application.
@param {String} zoneId  the time-zone ID, not null
@param {Object {java.util.Map}} aliasMap  a map of alias zone IDs (typically abbreviations) to real zone IDs, not null
@return {Object {java.time.ZoneId}} the zone ID, not null
@throws DateTimeException if the zone ID has an invalid format
@throws ZoneRulesException if the zone ID is a region ID that cannot be found
*/
of : function(  ) {},

/**Obtains an instance of {@code ZoneId} from an ID ensuring that the
 ID is valid and available for use.
 <p>
 This method parses the ID producing a {@code ZoneId} or {@code ZoneOffset}.
 A {@code ZoneOffset} is returned if the ID is 'Z', or starts with '+' or '-'.
 The result will always be a valid ID for which {@link ZoneRules} can be obtained.
 <p>
 Parsing matches the zone ID step by step as follows.
 <ul>
 <li>If the zone ID equals 'Z', the result is {@code ZoneOffset.UTC}.
 <li>If the zone ID consists of a single letter, the zone ID is invalid
  and {@code DateTimeException} is thrown.
 <li>If the zone ID starts with '+' or '-', the ID is parsed as a
  {@code ZoneOffset} using {@link java.time.ZoneOffset#of(String)}.
 <li>If the zone ID equals 'GMT', 'UTC' or 'UT' then the result is a {@code ZoneId}
  with the same ID and rules equivalent to {@code ZoneOffset.UTC}.
 <li>If the zone ID starts with 'UTC+', 'UTC-', 'GMT+', 'GMT-', 'UT+' or 'UT-'
  then the ID is a prefixed offset-based ID. The ID is split in two, with
  a two or three letter prefix and a suffix starting with the sign.
  The suffix is parsed as a {@link java.time.ZoneOffset#of(String) java.time.ZoneOffset}.
  The result will be a {@code ZoneId} with the specified UTC/GMT/UT prefix
  and the normalized offset ID as per {@link java.time.ZoneOffset#getId()}.
  The rules of the returned {@code ZoneId} will be equivalent to the
  parsed {@code ZoneOffset}.
 <li>All other IDs are parsed as region-based zone IDs. Region IDs must
  match the regular expression <code>[A-Za-z][A-Za-z0-9~/._+-]+</code>
  otherwise a {@code DateTimeException} is thrown. If the zone ID is not
  in the configured set of IDs, {@code ZoneRulesException} is thrown.
  The detailed format of the region ID depends on the group supplying the data.
  The default set of data is supplied by the IANA Time Zone Database (TZDB).
  This has region IDs of the form '{area}/{city}', such as 'Europe/Paris' or 'America/New_York'.
  This is compatible with most IDs from {@link java.util.TimeZone}.
 </ul>
@param {String} zoneId  the time-zone ID, not null
@return {Object {java.time.ZoneId}} the zone ID, not null
@throws DateTimeException if the zone ID has an invalid format
@throws ZoneRulesException if the zone ID is a region ID that cannot be found
*/
of : function(  ) {},

/**Obtains an instance of {@code ZoneId} wrapping an offset.
 <p>
 If the prefix is "GMT", "UTC", or "UT" a {@code ZoneId}
 with the prefix and the non-zero offset is returned.
 If the prefix is empty {@code ""} the {@code ZoneOffset} is returned.
@param {String} prefix  the time-zone ID, not null
@param {Object {ZoneOffset}} offset  the offset, not null
@return {Object {java.time.ZoneId}} the zone ID, not null
@throws IllegalArgumentException if the prefix is not one of
     "GMT", "UTC", or "UT", or ""
*/
ofOffset : function(  ) {},

/**Obtains an instance of {@code ZoneId} from a temporal object.
 <p>
 This obtains a zone based on the specified temporal.
 A {@code TemporalAccessor} represents an arbitrary set of date and time information,
 which this factory converts to an instance of {@code ZoneId}.
 <p>
 A {@code TemporalAccessor} represents some form of date and time information.
 This factory converts the arbitrary temporal object to an instance of {@code ZoneId}.
 <p>
 The conversion will try to obtain the zone in a way that favours region-based
 zones over offset-based zones using {@link TemporalQueries#zone()}.
 <p>
 This method matches the signature of the functional interface {@link TemporalQuery}
 allowing it to be used as a query via method reference, {@code ZoneId::from}.
@param {Object {TemporalAccessor}} temporal  the temporal object to convert, not null
@return {Object {java.time.ZoneId}} the zone ID, not null
@throws DateTimeException if unable to convert to a {@code ZoneId}
*/
from : function(  ) {},

/**Gets the unique time-zone ID.
 <p>
 This ID uniquely defines this object.
 The format of an offset based ID is defined by {@link java.time.ZoneOffset#getId()}.
@return {String} the time-zone unique ID, not null
*/
getId : function(  ) {},

/**Gets the textual representation of the zone, such as 'British Time' or
 '+02:00'.
 <p>
 This returns the textual name used to identify the time-zone ID,
 suitable for presentation to the user.
 The parameters control the style of the returned text and the locale.
 <p>
 If no textual mapping is found then the {@link #getId() full ID} is returned.
@param {Object {TextStyle}} style  the length of the text required, not null
@param {Object {Locale}} locale  the locale to use, not null
@return {String} the text value of the zone, not null
*/
getDisplayName : function(  ) {},

/**Gets the time-zone rules for this ID allowing calculations to be performed.
 <p>
 The rules provide the functionality associated with a time-zone,
 such as finding the offset for a given instant or local date-time.
 <p>
 A time-zone can be invalid if it is deserialized in a Java Runtime which
 does not have the same rules loaded as the Java Runtime that stored it.
 In this case, calling this method will throw a {@code ZoneRulesException}.
 <p>
 {@link java.time.ZoneOffset} will always return a set of rules where the offset never changes.
@return {Object {java.time.zone.ZoneRules}} the rules, not null
@throws ZoneRulesException if no rules are available for this ID
*/
getRules : function(  ) {},

/**Normalizes the time-zone ID, returning a {@code ZoneOffset} where possible.
 <p>
 The returns a normalized {@code ZoneId} that can be used in place of this ID.
 The result will have {@code ZoneRules} equivalent to those returned by this object,
 however the ID returned by {@code getId()} may be different.
 <p>
 The normalization checks if the rules of this {@code ZoneId} have a fixed offset.
 If they do, then the {@code ZoneOffset} equal to that offset is returned.
 Otherwise {@code this} is returned.
@return {Object {java.time.ZoneId}} the time-zone unique ID, not null
*/
normalized : function(  ) {},

/**Checks if this time-zone ID is equal to another time-zone ID.
 <p>
 The comparison is based on the ID.
@param {Object {Object}} obj  the object to check, null returns false
@return {Boolean} true if this is equal to the other time-zone ID
*/
equals : function(  ) {},

/**A hash code for this time-zone ID.
@return {Number} a suitable hash code
*/
hashCode : function(  ) {},

/**Outputs this zone as a {@code String}, using the ID.
@return {String} a string representation of this time-zone ID, not null
*/
toString : function(  ) {},


};