27.03.2013 Views

SPSS® 12.0 Command Syntax Reference

SPSS® 12.0 Command Syntax Reference

SPSS® 12.0 Command Syntax Reference

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

OMS 1135<br />

• The table contents as they are (or would be) displayed in a pivot table in the Viewer are<br />

contained in text attributes. For example:<br />

<br />

These text attributes can be affected by both output language (SET OLANG) and settings<br />

that affect the display of variable names/labels and values/value labels (SET TVARS and<br />

SET TNUMBERS). In this example, the text attribute value will differ depending on the output<br />

language, whereas the command attribute value remains the same regardless of output<br />

language.<br />

• Wherever variables or values of variables are used in row or column labels, the XML will<br />

contain a text attribute and one or more additional attribute values. For example:<br />

<br />

...<br />

For a numeric variable, there would be a number attribute instead of a string attribute. The<br />

label attribute is only present if the variable or values have defined labels.<br />

• The elements that contain cell values for numbers will contain the text attribute and<br />

one or more additional attribute values. For example:<br />

<br />

The number attribute is the actual, unrounded numeric value, and the decimals attribute indicates<br />

the number of decimal positions displayed in the table.<br />

• Since columns are nested within rows, the category element that identifies each column<br />

is repeated for each row. For example, since the statistics are displayed in the columns,<br />

the element appears three times in the XML: once for the<br />

male row, once for the female row, and once for the total row.<br />

Examples of using XSLT to transform OXML are provided in the Help system.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!