|
Difference between
version 4
and
version 3:
| Line 14 was replaced by line 14 |
| - Because the DAP is rich in data stored in variations of the Structure data type this means that much of what is produced from DAP datasources will naturally map to a RecordToken. Currntly there is a RecordDisassembler Actor that can be used to break apart these record. Unfortunately it is very cumbersome for the user to configure. Beacuse of this Ilkay attempted to write an AutomatedRecordDisassembler Actor and immediatley ran into a wall because it was not possible for the Actor to determine the structure of the incoming RecordToken at design time. |
| + Because the DAP is rich in data stored in variations of the Structure data type this means that much of what is produced from DAP data sources will naturally map to a RecordToken. Currently there is a RecordDisassembler Actor that can be used to break apart these RecordTokens. Unfortunately it is very cumbersome for the user to configure. Beacuse of this Ilkay attempted to write an AutomatedRecordDisassembler Actor and immediatley ran into a wall because it was not possible for the Actor to determine the structure of the incoming RecordToken at design time. |
Back to O Pe NDAP Kepler Data Model Resolution,
or to the Page History.
|
