Bryan Robbins

@philiphan is correct. The javadoc is inherited and is not accurate. The Default implementation only gets capabilities from the client properties file. We could explore an enhancement for key/value pairs...

I think the only thing missing from the list is the dataset description. That can include the row description (no need for them to be separate items in JSON object...

Hey @mauricio1990silva : any update on this? Will go ahead and include in 2.2 release for now.

Keep in dg-core for now.

In the meantime, it is possible to get a CSV of symbols for an exchange and use the CSV feature of the assign tag in the SCXML engine.

This could be a Transformer. Within model, add a placeholder. In transformer, populate value according to a given distribution. How will they describe the distribution? And how will this info...

Taking this out of 2.2 for now, as the effort seems a bit higher.

Feedback from 10/2 meeting: - Loading of a DDL should be its own operation. - How that plugs into an engine (SCXML or otherwise) is a separate problem. - How...

Some possibilities that were discussed: - If using the SCXML engine, the DDL could be loaded via a Custom Tag, like the CSV assign custom tag in the current SCXML...

Anything in particular? Are we talking Javadocs or the human-readable variety? https://github.com/FINRAOS/DataGenerator/tree/master/docs