Based on number allow the usage of wildcards symbol (*) to indicates an unbounded number. Legal version number using maximum 3 digits and optional alpha, beta or rc version. Askia Design Page Root node of the ADP definition. Version number of the ADP format definition. (Not the version of the page but the version of the ADP format) Based version of the ADP. Compatibility version with Askia product. Meta-data of the ADP. Unique identifier of the ADP. Should be share accross version of the same ADP. User friendly name of the ADP. Version of the ADP. This version must contains at least one digit and maximum 3 digits separates with a dot period (ex: 1, 1.0, 1.0.1). It could also contains an extra version information such as 'alpha', 'beta' or 'rc' optionally follow by a number (ex: 1.alpha2, 1.0.beta10, 1.0.1.rc3). Release date of the ADP. Describes the ADP. Name of the ADP author(s). Name of the company who provide the ADP. URL to the author/company web site. URL to the help file of the ADP. List all possible ADP's outputs. A condition could be specify for each outputs to make it alternative. Indicates the id of default output to use when none of the output conditions matches. It is require as the latest output fallback. Enforce uniqueness of the output ids. The default output id should match one of the output id. Output of the ADP. Unique identifier of the output. It use on the defaultOutput attribute of the outputs element. Name of the dynamic HTML file to use as the master page. The master page HTML file must content custom Askia Tags such as: - <askia-head /> - <askia-form> / <askia-questions /> / </askia-form> - <askia-foot /> Describes the element AskiaScript condition to use the current element. Content of the specify output. File use to generate the content. Indicates the type of content. According to this type, the system will automatically generate the proper HTML fragment unless the <yield> is specify. Flash content. Will be inserted using <object /> tag. The content must be static or share. CSS content. Will be inserted using <link href /> tag when static or share or using the <style></style> tag when dynamic. HTML content. Will be inserted as it is or interpreted when it's dynamic. Javascript content. Will be inserted using the <script src /> tag when static or share or using <script></script> tag when dynamic. Image content. Will be inserted using the <img src /> tag. The content must be static or share. Video content. Will be inserted using the <video src /> tag. The content must be static or share. Audio content. Will be inserted using the <audio src /> tag. The content must be static or share. Arbitrary binary file. Will be inserted according to the specify <yield> tag. The <yield> should be specified using a binary content otherwize the system will not create an output. Text-based file. Will be inserted as it is or interpreted when it's dynamic. Indicate how the content will be treat and where the system should find the content file. The share content is always associated with a file and must be place in the /Resources/Share/ folder of the ADP. The share content will be extract in the resources folder of the survey /Resources/SurveyName/. This kind of content, could be share accross ADX component and will not be overrides when it already exist in the folder. The static content is always associated with a file and must be place in the /Resources/Static/ folder of the ADP. The static content will be extract in the resources folder of the ADP /Resources/SurveyName/ADPname/. The dynamic content could be file (text based) or in-line code define in the definition of the content. It could embed AskiaScript to execute. When the content is a file, it must be place in the /Resources/Dynamic folder of the ADP. The dynamic content will not be extract but load in memory. Indicates how and where the system must render the current content. The resource will not be rendered. But it's still available through HTTP request. The resource will be inserted in the <askia-head /> section of the master page. Mostly use for CSS stylesheet. The resource will be inserted in the <askia-foot /> section of the master page. Mostly use for javascript insertion. Additional attribute to add or to overwrite in the auto-generated tag. When <yield> is present the attribute is not take in account. Name of the attribute. Value of the attribute. This value could be dynamic, embed AskiaScript code. Dynamic string which indicates how the content must be rendered. It override the built-in HTML render by the system. Must be use for the non-manageed file, such as binary or text List of properties accessible through the user interface. Category of the properties. Unique id of the category. User friendly name of the category to show on the interface. Indicates if the category should be collapsed by default. Enforce uniqueness of the property ids. Property accessible through the user interface. Indicate if the property is visible in the user in Askia interface. Describes the aim of the property. Default value of the property. Unique id of the property to access on it using the AskiaScript. This id should not be a reserved id. See <globalproperty> User friendly name of the property to show on the interface. Type of the property. Property as string. The string could be validate against a regular expression using the pattern attribute. Property as number. The number could be restricted using the min/max/decimal attribute. Property as boolean. The value must be true or false. Property as color. The format of the color could be specify using the colorFormat attribute. Property as string. Indicate the name of a resource file already register. This file must be on the survey and accessible through the url ../Resources/[Survey name]/ Indicate if the value of the property could or not embed AskiaScript code. The static value is use as it is. The dynamic value will be evaluated before his usage. If the value return by the evaluation doesn't produce an expected value according to the min, max, decimal, pattern, fileExtension... then the default value will be used. Indicate if a value is require for this property. Use with the type string, the regular expression pattern will be use to validate the value entered. Use with the type number. Indicates the minimum allowed value. Use with the type number. Indicate the maximum allowed value. Use with the type number. Indicate the maximum number of decimal digits allowed. Use with the type color. Indicate the format of the color. Color in RGB format (Red, Green, Blue) (RR,GG,BB) Color in RGBA format (Red, Green, Blue, Alpha) (RR,GG,BB,AA) Color in Hexadecimal format (#rrggbb) Use with the type file. Indicate the allowed extension of the file. Default value of the property. Indicates the identifier of global property to use. This identifier implicitly specified the category, name, type, mode... of the property. his system property is automatically displayed in the interface. It allow user to indicates if he allow the back navigation inside the survey. category: 'General' name: 'Enable back navigation' type: 'boolean' description: 'Allow the back navigation' value: true mode: 'dynamic' REMARKS: An ADP developer could ignore this information or hard-code a default value and hide it using the `visible` attribute, but it’s strongly recommended to use it as much as possible. Enumerates all allowed values. Allowed choice. Value of the option. User friendly text of the option. Enforce the uniqueness of option value