Open nscheiber-champ opened 2 weeks ago
To be further discussed, what I don't really like with CXML definition is that it's very vague ... IMO it makes sense to have an otherIdentifier in cases like that.
Proposal to create a specific PartyIdentifier with description (with an open code list) and textual value. This allows to limit the usage of otherIdentifiers in this context.
Ok with the proposal, next step is to identify the first items for the code list that would go with next release.
In current CXML mapping, the ram:AccountID tag of consignor, consignee, freight forwarder is mapped to Party#otherIdentifiers.
This makes conversion from 1R to CIMP and CXML difficult, as you need to match strings in OtherIdentifier#otherIdentifierType. I assume that many mappings will put different things there, eg. "ffw account number", "ACCOUNT NUMBER", etc..
As mitigation, I suggest to add a new property Party#accountNumber to avoid having to match strings and ease mapping.