indice-co / indice-co/EDI.Net

EDI Mapping

Open
#175 2 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
C#
Stars
490
Forks
173
PR merge metrics
No merged PRs in 30d

Description

We were looking at EDI.Net and it seems a good idea to translate the EDI messages using EDI DOM (i.e. the POCO classes). Could you suggest if we can do the mapping between the standards as easy? What would be the right way to go here? If we plan to use it for multiple clients who expect different variations of the output messages, what's the best way to develop that kind of 'extensions'?

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the repository's existing EDI DOM and POCO handling for EDIFact, X12, and TRADACOMS before defining a concrete mapping approach. The issue currently asks for architectural guidance on standards mapping and client-specific extensions, so done would require an agreed scope and acceptance criteria rather than a clearly specified code change.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.