Entitiy Algorithm:
1) The fileds problemTypes and application areas has following structure:
{ "id": string, "name": string, "children": [ { "id": string, "name": string, "children": [] }]
So, if the user choose application area e.g. "Natural Science" the whole tree including all children are published in the topic.
This information is irrelevant for JSON->RDF Mapping, because this data is already saved RDF Triple Store.
2) Also the field "Implementations" contains the full information about specific implementations, what is reduntant since we become also topics if an implementation is created/modified.
Suggestion:
For complex fields, such as "publications", "requiredComputeResourceProperties", "sketches", "problemTypes", "applicationAreas","tags", "implementations", "discussionTopics", "learningMethods", "algorithmRelations" publish in topics an json array with json objects having following structure:
{ "id": string, "name": string, },
e.g. {...., "problemTypes": [ { "id": "1a0f1b4d-ca15-474b-826c-474614f2ddb1", "name": "Machine Learning Problem" }, { "id": "1a0f1b4d-ca15-474b-826c-474614f2ddb4", "name": "Graph Problem" } ], ...}
Same suggestion for entites "Implementation" and "Data Pool".
Entitiy Algorithm:
1) The fileds
problemTypesandapplication areashas following structure:{ "id": string, "name": string, "children": [ { "id": string, "name": string, "children": [] }]So, if the user choose application area e.g. "Natural Science" the whole tree including all children are published in the topic. This information is irrelevant for JSON->RDF Mapping, because this data is already saved RDF Triple Store. 2) Also the field "Implementations" contains the full information about specific implementations, what is reduntant since we become also topics if an implementation is created/modified.Suggestion: For complex fields, such as
"publications", "requiredComputeResourceProperties", "sketches", "problemTypes", "applicationAreas","tags", "implementations", "discussionTopics", "learningMethods", "algorithmRelations"publish in topics an json array with json objects having following structure:{ "id": string, "name": string, }, e.g.{...., "problemTypes": [ { "id": "1a0f1b4d-ca15-474b-826c-474614f2ddb1", "name": "Machine Learning Problem" }, { "id": "1a0f1b4d-ca15-474b-826c-474614f2ddb4", "name": "Graph Problem" } ], ...}Same suggestion for entites "Implementation" and "Data Pool".