Framework-level interface defining read-write access to a temporal object, such as a date, time, offset or some combination of these. !(p) This is the base interface type for date, time and offset objects that are complete enough to be manipulated using plus and minus. It is implemented by those classes that can provide and manipulate information as {@linkplain TemporalField fields} or {@linkplain TemporalQuery queries}. See {@link TemporalAccessor} for the read-only version of this interface. !(p) Most date and time information can be represented as a number. These are modeled using {@code TemporalField} with the number held using a {@code long} to handle large values. Year, month and day-of-month are simple examples of fields, but they also include instant and offsets. See {@link ChronoField} for the standard set of fields. !(p) Two pieces of date/time information cannot be represented by numbers, the {@linkplain hunt.time.chrono.Chronology chronology} and the {@linkplain hunt.time.ZoneId time-zone}. These can be accessed via {@link #query(TemporalQuery) queries} using the static methods defined on {@link TemporalQuery}. !(p) This interface is a framework-level interface that should not be widely used _in application code. Instead, applications should create and pass around instances of concrete types, such as {@code LocalDate}. There are many reasons for this, part of which is that implementations of this interface may be _in calendar systems other than ISO. See {@link hunt.time.chrono.ChronoLocalDate} for a fuller discussion of the issues.