Hi Greg and MacED,
okay, the problem with the file size is known to me too.
The issues you named about readability and complexity. I think I understand what you mean, after I took a look at following example from MatML:
But why is robustness an issue?
@MacED: Good point with JSON. I like the JSON format.
But no matter how the universal FE format is represented, the starting point must be an universal FE knowledge data base, that can be edited by us. For example, the structure of the data base could look like that (written in JSON format):
{
"FE": {
"Node": {
"ID",
"Coordinates": [x, y, z],
"CoordinateSystemByID": ID,
"CoordinateSystemByEulerAngles": [xy yz zx]
}
"Element": {
"ID"
"ElementTypeID"
"MaterialID",
"GeometricPropertyID"
}
"ElementType": {
"Dimension": {
"3D": {
"Geometry": {
"Point",
"Line",
"Area",
"Volume"
}
}
"2D": {
"Geometry": {
}
}
}
"Physics": {
"Strucutral",
"Fluid"
}
"Midnodes": "1"
}
"CoordinateSystem": {
"ID": ID,
"EulerAngles": [xy yz zx]
}
}
}
This is just a quick example, that I wrote in few minutes. I think there are some logical errors in the structure. For example, I don't know how to specify in JSON that the value of a property "Geometry" can have one of the values Point, Line, Area, Volume.
But the idea matters. Perhaps now is more clear what the universal FE data base should be in my opinion. You can see that the programming language is not that important. The structure is.
So that's why I'm wondering what collaborative tools are there in order to create and maintain that in an collaborative manner.
