- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Tue, 10 Jan 2017 07:25:10 +0100
- To: KETELS Kris <Kris.KETELS@swift.com>, "public-payments-wg@w3.org" <public-payments-wg@w3.org>
On 2017-01-09 14:06, KETELS Kris wrote: <snip> > ISO 20022 is far more than a syntax, let alone XML. > It is a modeling methodology and a repository of conceptual semantic concepts, > BusinessProcesses, BusinessTransactions and messages. Its layered design makes > its logical models syntax independent, allowing for the generation of XML, ASN1 > and now also JSON from that same logical model, fostering thus interoperability > between different syntaxes. We are as we speak extending ISO 20022 to model > following RESTful architectural design principles. A difference with REST compared to "traditional" messaging using XML is that REST (de-facto) is bound to HTTP. That is, the meaning (semantics) of a message is defined by no only by the message data, but by the URL, HTTP header parameters, and HTTP verb (GET, PUT, POST, PATCH). This greatly complicates signed messages: http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html That there are no standards for even serializing (storing) REST based messages isn't entirely surprising. I'm planning to write a rationale why I (in spite of seeing the REST-word everywhere), didn't go for that in the Saturn proof-of-concept system: https://test.webpki.org/webpay-merchant/home Well, maybe I'm just a general "misfit" since I didn't adopt IETF's JSON-based security standards either: https://cyberphone.github.io/doc/security/jsonsignatures.html OTOH, I believe the IETF were a bit blocked by legacy stuff (Open ID) that was already established on a massive scale in addition to being unaware of the updated JavaScript standard which turned out to be 100% compatible with my core idea (predictive serialization) although I were told these idea was wrong :-) Anders > > BTW I have no clue why you attach the note 'XML must die' to SWIFT MX ISO 20022. > > Please be informed about a standard before judging it. I would happily inform you or give you a crash course on what ISO 20022 is really about. > > regards > Kris Ketels > > > > -----Original Message----- > From: Anton Tveretin [mailto:tveretinas@yandex.ru] > Sent: 07 January 2017 22:34 > To: DISPATCH list; public-payments-wg@w3.org > Subject: NGMTP Class 9 Questions & Answers > > Hello All, > I have published a small memo for the format of payment documents. This is not the actual specification. > Direct URL: http://www.fit-rulez.narod.ru/ngmtp/ngmtp_c9_qa.html > In the past, both work groups showed interest in these. > Regards, > Anton > >
Received on Tuesday, 10 January 2017 06:26:04 UTC