Proposal: formalize datetime profile as a feature of OCSF schema definition #969
Labels
framework
Structures, conventions, requirements, data types, etc.
non_breaking
Non Breaking, backwards compatible changes
Background
Today, the
datetime
profile is a "special" profile:This means that:
This intent of this proposal is to formalize the mechanisms behind the
datetime
profile into a feature of profiles themselves. This would allow thedatetime
profile to be defined in the OCSF schema definition language.Proposal
Add a new feature to profiles that allows them to define the behavior of the
datetime
profile. The behavior is:timestamp_t
on a schema, add a siblingdatetime_t
field with the suffix_dt
.As a feature of profiles, these three attributes could be codified under a new top-level property or
$special_property
.The intent of this change would be to be non-breaking. That is, it should not modify any of the actual schemas, only the way this profile is defined.
Example
This is a simple example of how this information could be codified. The names of these properties in the schema definition language below are just examples; all four can be renamed based on feedback.
I chose to go the
$special_property
route because I thought defining it underattributes
made sense, as it was manipulating attributes, similar to anattributes.$include
.Work
This section is intended to capture the work that would need to be done in order for this change to be enacted.
datetime
)datetime
profile itselfThe text was updated successfully, but these errors were encountered: