- From: Erik Anderson <notifications@github.com>
- Date: Wed, 17 Feb 2016 08:37:19 -0800
- To: w3c/webpayments <webpayments@noreply.github.com>
- Message-ID: <w3c/webpayments/issues/95/185287825@github.com>
@fredMeignien, correct. Lets assume that Financial Services Context is ISO 20022. We can use naming within a WebPayments Context and show mapping to the ISO 20022 Context. Ultimately ISO 20022 BC and WebPayments BC can be dynamically mapped as the information enters/leaves one domain. @mattsaxon Lets try and solve common problems with common solutions. The issue of context is a known problem with ISO 20022. The ISO 20022 Work Group leader (and liaison to W3C) is pointed me in the direction of BC's. Anti-Corruption layer : Pragmatics vs Semantics. Age old argument. Static structure underlying dynamic behavior. On your list https://github.com/w3c/webpayments/wiki/ISO-20022-definitions-mapping-on-flows I argue each of those payment instruments will have different dynamic behaviors on the same underlying static data structures. I actually agree, simpler is easier, but with proper BoundContext's definitions we can automate the transformation between the WebPayments BC and the ISO 20022 BC as required by the the domain specific payment instrument. Simpler for whom? Ourselves or the 30 years of legacy technologies/standards that need to adapt for the usage over the web? I dont believe we need to go off the deep end of theory but there are practical solutions to these problems exist. Proper BC's and pragmatics will allow us to model the flows of information and its mappings for everyone's needs. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/95#issuecomment-185287825
Received on Wednesday, 17 February 2016 16:38:22 UTC