Schema definition for data exchange of WCET, WCRT, stack data and activation. Copyright 2009 Symtavision Development Partnership. All rights reserved. Root element. Content model for the entity 'common'. Content model for the entity 'general'. Content model for the entity 'CPU'. Content model for the entity 'executable' based on dedicated type. Content model for the entity 'mode'. Content model for the entity 'request'. 'request' possibilities: BCET: covers 'best case execution time' analysis/trace for target code, WCET: covers 'worst case execution time' analysis/trace for target code, BCET-WCET: covers 'best case' + 'worst case execution time' analysis/trace for target code, Stack: covers 'stack' analysis, LoopTrace: covers determining the number of loop iterations based on traces, BCRT: covers 'best case response time' analysis/simulation, WCRT: covers 'worst case response time' analysis/simulation, BCRT-WCRT: covers 'worst case response time' analysis/simulation, Activation: covers activation event model, OS-Overhead: covers all OS overhead information Additional options to the entity 'request'. Content model for the entity 'response'. Content model for the timing response entities. Content model for the stack-usage response entities. Content model for the CallTrace response entities. Content model for the LoopTrace response entities. Content model for the activation ActivationType response entities. Content model for the OsOverheadType response entities (activate-/terminate task, context switch). Content model for the Standard-Event-Model entities consisting of period (must be >0.0), jitter (default: 0.0), minimum distance (default: 0.0), offset (default: 0.0, add also if synchronization is activated) Content model for the Pattern-Event-Model entities. Additionally to the 'StandardEventModel' attributes at least one event must be declared with an offset definition within range [0:period[. Content model for the Interrupt-Event-Model entities. Please make sure that upper and lower curve values in sequence are continuous ascending (next value must be equal or higher than previous value). This is the cookie section. It consists of several elements describing special data for owner use only. Elements should only be touched from owner only and can be ignored by other. This section contains multiple 'CookieElements' where each communication partner can place data as he wishes. There are three steps to follow: 1. define an own schema file importing this schema, 2. adding your used namespaces to written XML content, 3. write any data (namespace aware) to cookie child positions