CIQ Specifications are rich and my application does not need such complexity to define, say name and address of a customer. What do I do?
This is the statement we commonly hear from people who look at it. But the main point they miss is that the specification aims at application and industry independency, i.e. not specific to a particular application area, and hence is rich in nature. But version 3.0 allows users the option to customize the specifications to meet their application specific requirements without touching the CIQ core schemas, but at the same time maintain compatibility and conformity with the specifications. For example, take address specification (xAL). If a user wants to just use free text address lines and a few of the address entities (e.g. locality, and postcode), they can define business constraint rules outside of the core schema that ignores the unwanted address entities. See “CIQ TC – Name, Address and Party Specifications” document of version 3.0 specifications that explains how to do this.
Related Questions
- I have received a Show Cause Notice asking explanation, why the present address information disclosed in the application form contradicts the information in the police report. What should I do?
- How can I customise Name and Address CIQ Specifications, i.e., I want a simplified version (light weight) of xNL and xAL specifications?
- Is there a low cost way to port my customer’s existing PL/N application to run on a Windows Mobile machine?
