You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Modularization of the whole conversion process is a great idea. so that teams can innovate in specific areas without having to implement complete converters from scratch.
Draft list of modules:
input parser
input reader with streaming (batching, chunking)
transformation parser
transformation engine that applies all relevant maps on a chunk of input
Let's transfer to the best-practices repo, although IMO in languages should be an agreement, while optimizations and other techniques are part of each implementation/engine and related use-cases
dachafra
transferred this issue from kg-construct/mapping-challenges
Mar 14, 2022
issue: Should we, and if so, how do we make a distinction between language and tool features?
suggestion: Survival of the fittest?
The text was updated successfully, but these errors were encountered: