If a multi-value property P is encountered, then its treatment depends on the context within which the document view is being used:
Export: In the context of export, the repository may either ignore the multi-value property or serialize it as an attribute whose value is an XML Schema list type4 (i.e., a whitespace-delimited list of strings). If the latter approach is taken then:
Each value in the property is converted to a string according to standard conversion, see 6.2.6 Property Type Conversion. If the multi-value property contains no values, then it is serialized as an empty string.
All literal whitespace within each string is escaped, as well as any characters that should not be included as literals in any case, see 6.4.4 Escaping of Values.
The final attribute value is constructed by concatenating the resulting strings, with the addition of the space delimiter, into a single string. The order of concatenation must be the same as the order in which the values appear in the Value array returned by Property.getValues.
Furthermore, if multi-value property serialization is supported, then a mechanism must be adopted whereby upon re-import the distinction between multi- and single- value properties is not lost, see 6.4.4 Escaping of Values.
Note that this escaping of space literals does not apply to the value of jcr:xmltext/jcr:xmlcharacters when it is converted to XML text. In that case only the standard XML entity escaping is required, regardless of whether multi-value property serialization is supported (see 220.127.116.11 XML Text and 6.4.4 Escaping of Values).
XPath: In the context of an XPath query, the value array of property P is mapped to a pseudo list type attribute value. We call it a pseudo list type because space delimiters are not used and consequently space literals within individual values are not escaped, nor are the five special characters (&, <, > ,' and ") that would normally be escaped using predefined entity references. This is possible because the XML stream in the XPath context is virtual and therefore it need never be actually serialized. However, tests against multi-value properties in XPath using general comparison operators act as they would if the multi-value property were a list-type attribute, except that spaces and any of the five special characters occurring within value literals in the XPath statement are not escaped (see 18.104.22.168 Searching Multi-value Properties).