The VDI standard hosted by NAMA shows CashCollection @amount to be as follows.

This would better map to a xs:decimal type in XML but currently Collections.xsd is using the type xs:string.

A Market message is expected to be able to be sent to share market information from a VMS to a MMS before a kiosk association has been established. Since a market message may not have a list of kiosks under the Kiosks element should not be required by Markets.xsd.

Draft 1.3 of the VDI standard states.

The web service should be implemented using SOAP 1.1 standard. Authentication should be implemented by adding standard HTTP 1.0 header as a SOAP header containing base64 encoded username and password.

The problem is that the actual production implementation uses _Basic HTTP Authentication- and NOT a SOAP basic concept such as mechanisms defined in ws-security 1.1. We should either make this clearer in the document and remove incorrect information about SOAP headers or we should consider a change the the implementation and ensure that the documentation matches.

For consistency and to match existing implementations, the @MarketId attribute should be changed to @MarketID.

In recent cases, the scenario has been presented where it would be useful to allow sales data for markets that are not specifically integrated to be sent to a VMS even though a MarketID value may not be available.

Due to the fact that the @MarketID attribute is noted as required in the standard our current validation based on the standard will flag such mms-sales messages as invalid.

The proposal is to change the @MarketID attribute to optional and specify in the comments that it should be provided if available.