Question on behalf of @marcus-stellar-pool:
What A12 model-based document mappings, so mappings from/to A12 documents to/from other formats, exist?
I know:
- CDM: A12 ← → A12
- Insurance CFI A12 ← JSON (Working on the other way)
- Double document model + calculated fields (Andreas Brieg told me about it.)
- Apache Camel, though more template tham modeling as it is not directly A12
Answer on behalf of @andreas-fresh-mesa:
There are, probably multiple, projects with implementations of A12 ← → Excel.
In regard to Apache Camel, you could also take a look at GitHub - schibsted/jslt: JSON query and transformation language or GitHub - IBM/JSONata4Java: Open Source Java version of JSONata. Both allow processing JSON, which you can integrate without the Camel overhead by leveraging the A12 JSON serialization. Also you do not have the compile time dependency of model and transformation.
Answer on behalf of @martin-binary-cloud:
We have used a generic A12 ← → Java Pojos mapping in different projects. The mapping is not model-based, but could easily be modified and does not have to be fixed at compile time as annotations in the model could be used to represent the mapping information.
Answer on behalf of Joseph Held:
We map A12 data in the datapool to relational tables.
Answer on behalf of @marcel-calm-dew :
We have a (more or less generic) model-based A12 → Cosmo JSON converter. It has some special features but the basics are there.