ARTS needs your feedback to determine the impact of separating the POSlog schema into the following independent schemas:

1. Retail Transaction and Customer Order Transaction

2. Control Transaction

3. Tender Control Transaction

4. Foodservice Transaction

5. Forecourt Transaction

6. Inventory Control Transaction

Issues with Current Structure:

The schema is extremely large, pushing the limits of support and maintenance.
It is, in reality, six loosely-related, independent schemas, and versioning of each schema through feedback and development results in versioning all schemas — even those with no respective changes. This seriously affects all implementations.
From an interface viewpoint, the current schema requires an application to subscribe to all messages instead of only those which have direct relevance. For example, a loss prevention application must subscribe to and evaluate all messages to receive only the control transaction messages.
The conformance program requires an applicant to pass 30% of all use cases. Many vendors of more narrowly-focused applications find that there aren’t enough use cases pertinent to their product to clear the 30% hurdle and be certified POSlog conformant.

Architectural Impact:

Normal end users who need Retail Transactions, Tender Control Transactions and Control Transactions would need to subscribe to three message streams instead of one.
It would allow greater flexibility to end users allowing them to pick and choose those components relevant to their needs.

To determine the "right" direction, we are seeking your guidance.

Please respond to the following short survey.

Yes No