A B2B application layer protocol for Interledger?

>From the discussion around payment to invoices there appears to be a number
of views that the current application layer protocol is not meeting the
needs of all B2B use cases.

Further, there is a suggestion that there are a number of existing
protocols and standards that we should be leveraging.

It's important to note that the Interledger architecture is layered,
intentionally, to resemble something like the OSI model for communications
protocols. At the lowest layers are very simple protocols that have a
specific purpose but these build up to an application layer where it is
possible to construct a number of application layer protocols that are
built on the lower layer primitives and fit for a particular purpose.

I'd compare these to communications stack protocols like HTTP and FTP.
These two protocols are built on the same underlying IP-based stacks but
were designed for very different purposes.

Right now OWPS is intended to be a very simple application layer protocol
primarily designed to handle P2P payments or very simple C2B payments (i.e.
1:1 payment to invoice). It has very specific design principles which may
not be appropriate for a lot of use cases (such as being operatorless).
This protocol may evolve but it's unlikely to ever be a rich protocol that
incorporates comprehensive stacks like ISO20022 or ebXML.

Rather than trying to turn OWPS into a protocol that can handle all use
cases I'd suggest there is scope for a more complex and rich application
layer protocol that is more targeted at "enterprise" use cases.

If there is a willingness within this group to begin developing another
application layer protocol that is focused on B2B and leverages existing
standards like ebXML. ISO20022 or UBL then that would be great.

It is a far larger task than the current group could take on but I'd
certainly support it and try to get involved as time allows.

Adrian