# `Feel.Extension.Camunda.TemporalFormats`
[🔗](https://github.com/FeeJai/BDM/blob/feel-v0.1.0/apps/feel/lib/feel/extension/camunda/temporal_formats.ex#L1)

The spellings of a time and of a date and time that Camunda reads and DMN 1.6 does not (D-81).

Camunda's FEEL reads `time("13:30")`, `@"2020-01-01T00:00Z"` and `date and time("2018-04-29T09:30:00+02:00[Europe/Berlin]")`,
which is the text that Java writes for a date and time in a zone, and the `T` before a time that
`time("T23:59:00")` has in its documentation. DMN 1.6 reads none of these, and a text that is none of its strings
is `null`, with an error. With this extension on they are read, as the DMN 1.6 string that they stand for
(`Feel.Value.Temporal.Spellings` has the rules), by `time(...)`, `date and time(...)` and `@"..."`, and each one that
was read as another spelling is reported once, as an `:info` with the code `:temporal_spelling`: a model that uses
it is one that an engine which follows only the specification does not read.

A text that DMN 1.6 reads is read as it was. This is an extension and not what the library does, because it
turns a `null` into a value, and a model can depend on the `null`: `date(input) = null` is how a decision
checks a string that came from outside.

It is `:camunda_temporal_formats`, and part of `:camunda`.

---

*Consult [api-reference.md](api-reference.md) for complete listing*