The use and reuse of any data exchange model is greatly eased by providing adequate test data. This test data should also be made a part of the final asset uploaded to SEMIC. Thus users of your asset…
As the owner and developer of the asset, you should define criteria against which your solution can be proofed (using the test data). This is an auto-generated Asset Development Assistant. Please…
For an asset to enter the clearing process on SEMIC, a comprehensive documentation is required. As described above, this will make your solution easier to maintain and extend. This is an auto…
Pack a zip file containing: * all artefacts relevant to your asset (e.g. XML schema, UML-models, etc.) * documentation, preferably in English * test cases and test data (if available) * the licence…
Especially if you have reused an asset from SEMIC your feedback will be useful for any future user of this asset. So please leave your feedback detailing how you were able to use the asset, what…
Default values are often used in data sources, e.g. to signify unknown data elements. Using a date like 01/01/1970 is an example. If these default values are not adequately documented and/or different…
This type of conflict is closely related to data base design. It occurs when data from two different sources is to be integrated but is subject to different integrity constraints. Using different…
Whenever an amount is stored, it is important to be aware of the unit and scale this value is used with. E.g. German brokers give the values of their stocks in Euro with two decimal places. British…
The gravity of errors based on incorrect units and disparate scales makes testing indispensable. Prepare a set of test data and check for the accuracy of the exchanged data. This is an auto-generated…
If it is indispensable to maintain different units or scales of values, you must make sure that conversion is provided for accurately. This is an auto-generated Asset Development Assistant. Please…
A very common occurrence of this type of conflict is in date representation. A date given as 08/09/07 could be interpreted as 9 August 2007, 8 September 2007, or even 7 September 2008. Wherever the…
Data models are often radically different. This is partly due to differing requirements but to a large extent also due to personal preferences of the person modelling the data concepts. Especially the…
