Draft of a Cohesive Model for Defining Representations, Context Items and similar items

[knelson-farmbeltnorth]

The below is an initial draft of a model to replace both the ADAPT Representation System and Context Item Definitions and related objects. It also intends to be a landing spot for what we refer to as Observation Codes.

The blue objects represent the definition of data types, centered on the Data Type Definition. The orange object is supplemental usage information, and the green objects are the primary example of the usage of the definitions within ADAPT.

The Data Type Definitions would exist in one published/formalized instance, and once within each ApplicationDataModel (optionally) for any custom definitions.

Due to the amount of discussion needed, I logged separate issues for the following:

88 DTD Object

89 Identifier Code

90 Presentations

91 Geo Political Contexts

92 Omitted Concepts

94 Custom Representations

[knelson-farmbeltnorth]

Following discussion of all of the sub items, we've arrived at the following. One remaining discussion item is the Data Type Definition Usages attribute on Logged Variables.

[knelson-farmbeltnorth]

Open issues:

1. "Data Type Representation" is suggested as an alternative to "DataType Definition."
2. @strhea We need to resolve the optional DataTypeDefinition usages above. I continue to feel it is an elegant solution compared to duplicating many of the data type definitions 5x/item. Can we review your specific concerns?

[knelson-farmbeltnorth]

Agreement in 24 May 2023 meeting to adopt "Data Type Representation." Also agreed, delete the above Data Type Definition usages and add "Actual", "Target" and "Control" types specifically to application and other machine controllable definitions.