node

node can be used to configure a node, element or attribute in different ways, such as role, pretty name, placeholder and templates.

<x:node match="td">
  <x:role>tablecell</x:role>
  <x:name xml:lang="en">Cell</x:name>
  <x:name xml:lang="nl">Cel</x:name>
  <x:placeholder>{name}</x:placeholder>
  <x:templates>
    <x:template class="red">
      <p><?start?></p>
    </x:template>
  </x:templates>
</x:node>

node element

Namespace: http://www.xopus.com/xmlns/config

Allowed Children

enumeration
(Optional)
invalidValueMessage
(Optional)
inputType
(Optional)
lookup
(Optional)
name
(Optional)
placeholder
(Optional)
role
(Optional)
templates
(Optional)
uiGroup
(Optional)

Attributes

ignoreMixed
This attribute can be used to work around an issue that arises out of the use of block level elements, such as lists (<ol>, <ul>), tables (<table>), and paragraphs (<p>) inside mixed complexType elements (mixed="true"). See the mixed content page for more information. (Optional)
match
An XPath that selects elements and/or attributes that you want to configure. (Like the match attribute on XSLT templates.)
preferElementsOnlyParent
This attribute can be used to guide Xopus in the creation of new elements. Some schemas define mixed content elements that have the intention that the author uses either text with "inline" markup or a sequence of "block"-like elements. By setting this attribute to true on elements that should be kept out of mixed content, Xopus will try to insert such elements in an ancestor that is not mixed (i.e. an ancestor that has an elements-only model.) (Optional)

Parent Elements

nodeConfig

History

version event
Xopus 4.1 Introduction. (Case 196571)