Download JAR files tagged by specifications with all dependencies

Pact Specification ================== The [Pact Specification](https://github.com/bethesque/pact_specification) is a robust set of tests on the pact matching code aimed at ensuring pact library implementations across different languages have the same matching behaviour. Without adhering to these specifications there would be room for subtle issues to arise between consumers and providers using different libraries.

Pact Specification ================== The [Pact Specification](https://github.com/bethesque/pact_specification) is a robust set of tests on the pact matching code aimed at ensuring pact library implementations across different languages have the same matching behaviour. Without adhering to these specifications there would be room for subtle issues to arise between consumers and providers using different libraries.

Pact Specification ================== The [Pact Specification](https://github.com/bethesque/pact_specification) is a robust set of tests on the pact matching code aimed at ensuring pact library implementations across different languages have the same matching behaviour. Without adhering to these specifications there would be room for subtle issues to arise between consumers and providers using different libraries.

Pact Specification ================== The [Pact Specification](https://github.com/bethesque/pact_specification) is a robust set of tests on the pact matching code aimed at ensuring pact library implementations across different languages have the same matching behaviour. Without adhering to these specifications there would be room for subtle issues to arise between consumers and providers using different libraries.

A fully-conforming XML Schema 1.0 processor with partial support for the XML Schema 1.1 specifications (Part 1: Structures and Part 2: Datatypes). Xerces2 also provides a complete implementation of the following W3C Recommendations: * Extensible Markup Language (XML) 1.1 * Document Object Model (DOM) Level 3 Core * Document Object Model (DOM) Level 3 Load and Save * XML Inclusions (XInclude) Version 1.0

The standardization of KHQR code specifications will help promote wider use of mobile retail payments in Cambodia and provide consistent user experience for merchants and consumers. It can enable interoperability in the payment industry. A common QR code would facilitate payments among different schemes, e-wallets and banks and would encourage small merchants to adopt KHQR code as payment method. KHQR is created for retail or remittance in Cambodia and Cross-Border. It only requires a single QR for receiving transactions from any payment provider through Bakong including Bakong App.

The standardization of KHQR code specifications will help promote wider use of mobile retail payments in Cambodia and provide consistent user experience for merchants and consumers. It can enable interoperability in the payment industry. A common QR code would facilitate payments among different schemes, e-wallets and banks and would encourage small merchants to adopt KHQR code as payment method. KHQR is created for retail or remittance in Cambodia and Cross-Border. It only requires a single QR for receiving transactions from any payment provider through Bakong including Bakong App.

Virgil Security is presenting an implementation of the [Double Ratchet](https://signal.org/docs/specifications/doubleratchet/) algorithm, which is used by parties to exchange encrypted messages based on a shared secret key. The implementation includes: - **Virgil Perfect Forward Secrecy (PFS) service** – a standalone web-service that is dedicated to managing one-time keys and long-time keys that are based on their Identity Public Keys (public keys that are contained in user cards published on Virgil Cards service); - **Ratchet SDK** – interacts with PFS service for publishing and managing one-time keys and long-time keys and interacts with Virgil Cards service for retrieving user's indentity cards which the OTK and LTK are based on. The parties derive new keys for every Double Ratchet message so that previous private keys cannot be calculated from new ones. The parties that participate in the communication also send Diffie-Hellman public values attached to their messages. The results of Diffie-Hellman calculations are mixed into the derived keys so that the new private keys cannot be calculated from the previous ones.

Virgil Security is presenting an implementation of the [Double Ratchet](https://signal.org/docs/specifications/doubleratchet/) algorithm, which is used by parties to exchange encrypted messages based on a shared secret key. The implementation includes: - **Virgil Perfect Forward Secrecy (PFS) service** – a standalone web-service that is dedicated to managing one-time keys and long-time keys that are based on their Identity Public Keys (public keys that are contained in user cards published on Virgil Cards service); - **Ratchet SDK** – interacts with PFS service for publishing and managing one-time keys and long-time keys and interacts with Virgil Cards service for retrieving user's indentity cards which the OTK and LTK are based on. The parties derive new keys for every Double Ratchet message so that previous private keys cannot be calculated from new ones. The parties that participate in the communication also send Diffie-Hellman public values attached to their messages. The results of Diffie-Hellman calculations are mixed into the derived keys so that the new private keys cannot be calculated from the previous ones.

The MAJ API was written by Richard Cartwright, with the help and support of Guillaume Belrose and Fang Ren. To contact the author, please raise an issue. The software is provided AS IS with no warranty whatsoever. The MAJ API (pronounced madge) is a pure Java API for creating, reading, manipulating and writing MXF (SMPTE ST 377), AAF structured storage and Reg-XML (SMPTE ST 2001) files. MXF files are commonly used as a container for professional media file formats and AAF is supported by a number of professional video editing packages. MXF and Reg-XML are used as part of the Interoperable Mastering Format suite of specifications.