Authors can define their own markup language and use it from within XDIME documents. A binding policy contains a binding definition and a corresponding implementation that together are applied to custom elements in an input document to transform them into other elements, either built-in or other custom elements that will be further transformed by other bindings. Refer to the topic entitled About reusable components for further information.
Authors can define their own markup language and use it from within XDIME documents. A binding policy contains a binding definition and a corresponding implementation that together are applied to custom elements in an input document to transform them into other elements, either built-in or other custom elements that will be further transformed by other bindings. Refer to the topic entitled About reusable components for further information.
Each policy must reference a single binding definition. The binding definition may have a number of corresponding binding implementations, each of which can be associated with a variant.
The URL control in the Metadata section of the editor must point to an XML file containing the binding definition. The URL control in the Variant Content section must point to an XML file containing the binding implementation for the selected variant.
Each project can have a set of binding policies that can be applied to elements from within the project. Refer to the topic entitled bindings for further information.
MCS policies can be imported to a JDBC database to get optimum performance. MCS automatically embeds the external files containing a binding definition and its implementation(s) within the corresponding binding policy during importing to a JDBC repository, and they stay embedded when exporting the policies from the repository. Note that the Mobile Portal Toolkit editor only supports editing of a binding definition and implementation(s) that are external to the policy and therefore any exported binding policies will no longer be editable in Mobile Portal Toolkit. For the same reason binding policies cannot be edited collaboratively as that requires storing the policies in a JDBC repository.