Page
A page is defined by the following WSDL:
A page contains all the properties that any publishable asset would contain. A page also specifies the configuration set relationship and the choice between structured data or xhtml for the page content.
Structured Data Definition
When a page contains a structured data definition, it will have a structured-data complexType nested inside of it, and it will not contain xhtml due to the choice element. Here is the WSDL for the structured-data complexType:
The structured-data type is a composite for specifying the structured data definition relationship (definitionId or definitionPath) as well as the actual structured data content (structuredDataNodes).
Structured data (property structuredDataNodes, WSDL complexType structured-data-nodes) is represented as a series of nodes (property structuredDataNode, WSDL complexType structured-data-node) that each have a type, identifier, and some content depending on that type.
A single structured-data-node is defined in the following WSDL:
First, the type property is another complexType, structured-data-type:
The most common type is "text", which means a node simply contains text content. This corresponds to text boxes, text areas, WYSIWYGs, radio buttons, checkboxes, dropdowns, and date choosers in the Cascade Server web interface. When this is the structured data node type, the "text" property of the node will be used.
Next is an asset node type. This is for specifying a relationship in the structured data. The analog in the Cascade Server web interface is a block, file, link, or page chooser. In this case only one of the blockId, blockPath, fileId, filePath, pageId, pagePath, symlinkId or symlinkPath fields would be filled in to specify an asset relationship.
Finally is the group node type. When this node type is specified, this node is the "head" of another chain of structured data nodes; thus, it is possible to nest structured data nodes inside one another. To accomplish this nesting, simply specify another structuredDataNodes element (WSDL complexType structured-data-nodes), much as if you were specifying the structured data for a page.
Here is an example of part of a SOAP request containing structured data: