document #331
Support binary calendar types with tick units other than seconds and milliseconds
| Status: | closed | Start date: | 01/23/2018 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | DFDL v2.0 | |||
| Document Type: | Proposed Recommendation |
Description
Currently DFDL binary timestamp representations are limited to 'binarySeconds' and 'binaryMilliseconds. Other 'tick' intervals have been observed in the real world, for example:
- Windows FILETIME - 100ns
- OPC-UA protocol - 100ns.
It would be useful for DFDL to be able to handle any 'tick' interval.
It would also be useful for DFDL to allow any length of binary timestamp - currently the lengths are fixed depending on the representation.
The other variable is epoch, but DFDL already allows the epoch start to be specified in a sufficiently flexible way.
These should be considered as candidate improvements for DFDL 2.0.
History
Updated by Michael Beckerle almost 3 years ago
- Target version set to DFDL v2.0
Updated by Michael Beckerle almost 2 years ago
- Status changed from submitted to closed
(Other formats not available in this archive.