Datatypes #3
Description
Currently Buggy doesn't care for datatypes and thus cannot automatically identify problems related with datatypes.
Buggy datatypes should be flexible. This means that a datatype is no fixed definition, but besides a semantic description, a datatype is generally a map or a Javascript Object. This allows for a simple name mapping between semantically identical datatypes that name their members differently.
It should be possible to extend datatypes with other definitions, if needed. E.g. one could extend a Point datatype that has only X and Y coordinates with R and PHI if a group uses these to calculate a problem.
This is partly already implemented as every data stream consists of a Javascript Object and the values are extracted via Select. The identification of equal types isn't possible now. In the beginning it would be sufficient to rely on user input for type identification as it is a semantic question that is usually best answered by the user itself.