|
Data Instance Conformance Evidence
- Mandatory:
- Log files and/or screen captures from a 3rd party validating parser showing the instance validates against all applicable IMS schema(s)
- Optional:
- One or more descriptions of proven interoperability in customer settings between applications claiming conformance to the relevant IMS Specification
Application Import Conformance Evidence
- Mandatory:
- Evidence of support for semantics consisting of:
- One or more screen captures with an XML instance file showing that the application correctly renders the IMS information model in the user interface
- Any other clear evidence of this requirement
- Optional:
- One or more descriptions of proven interoperability in customer settings between applications claiming conformance to the relevant IMS Specification
Application Export Conformance Evidence
- Mandatory:
- Evidence that the application supports the semantics as defined within the applicable IMS information model(s)
- Evidence that the exported instance validates against applicable IMS XML Schema(s) consisting of one or more XML instance files with associated log files or screen captures from a 3rd party validating parser
- Evidence that the application does not modify an imported Data Instance except when intended, consisting of one or more Data Instances, screenshots of their access within the application, and the exported Data Instances. Please also include evidence that the imported and exported Data Instances are conformant as per the Data Instance Evidence Schedule.
- Optional:
- One or more descriptions of proven interoperability in customer settings between applications claiming conformance to the relevant IMS Specification
Service Behavior Conformance Evidence
- Mandatory:
- Optional:
- One or more relevant code segments
- One or more event logs of relevant transactions
- One or more descriptions of proven interoperability in customer settings between applications claiming conformance to the relevant IMS Specification
|