XPathOrder (obsolete XmlDoc property) - Revision history

JALWiccan: 1 revision

2012-06-19T20:49:50Z

1 revision

← Older revision	Revision as of 20:49, 19 June 2012
(No difference)

Goff: xpath expression

2012-06-19T20:49:48Z

xpath expression

← Older revision		Revision as of 20:49, 19 June 2012
Line 13:		Line 13:
	'''Note:'''		'''Note:'''
	As described in the [[??]] refid=unxpord page=no.		As described in the [[??]] refid=unxpord page=no.
	below, the XPathOrder property is invalid as of ''Sirius Mods'' version 7.3.		below, the XPathOrder property is invalid as of <var class="product">Sirius Mods</var> version 7.3.
	===Syntax===		===Syntax===
	%curr = doc:XPathOrder		%curr = doc:XPathOrder
Line 35:		Line 35:
	===Usage Notes===		===Usage Notes===
	<ul>		<ul>
	<li>Pror to ''Sirius Mods'' version 7.3, the XPathOrder property was available (with a		<li>Pror to <var class="product">Sirius Mods</var> version 7.3, the XPathOrder property was available (with a
	default value of <tt>Unicode</tt>) to allow EBCDIC ordered string comparisons		default value of <tt>Unicode</tt>) to allow EBCDIC ordered string comparisons
	in XPath.		in XPath.

	As of ''Sirius Mods'' 7.3, only Unicode ordered string comparisons are used, and the		As of <var class="product">Sirius Mods</var> 7.3, only Unicode ordered string comparisons are used, and the
	XPathOrder property is '''invalid''', in observance of the following conclusions		XPathOrder property is '''invalid''', in observance of the following conclusions
	about ordered string comparisons in XPath:		about ordered string comparisons in XPath:

Goff: xpath expression

2011-05-22T09:28:17Z

xpath expression

← Older revision		Revision as of 09:28, 22 May 2011
Line 10:		Line 10:

	This property indicates what kind of ordered comparison [[Janus SOAP]] uses for		This property indicates what kind of ordered comparison [[Janus SOAP]] uses for
	XPath expressions.		<var>[[XPath#XPath_syntax\|Xpath expressions]]</var>.
	'''Note:'''		'''Note:'''
	As described in the [[??]] refid=unxpord page=no.		As described in the [[??]] refid=unxpord page=no.

Dme at 20:13, 31 December 2010

2010-12-31T20:13:48Z

← Older revision		Revision as of 20:13, 31 December 2010
Line 2:		Line 2:
	[[Category:XmlDoc methods\|XPathOrder obsolete property]]		[[Category:XmlDoc methods\|XPathOrder obsolete property]]
	[[Category:XmlDoc API methods]]		[[Category:XmlDoc API methods]]
	~~[[Category:System methods]]~~
	<!--DPL?? Category:XmlDoc methods\|XPathOrder obsolete property: Collating sequence for XPath comparisons-->		<!--DPL?? Category:XmlDoc methods\|XPathOrder obsolete property: Collating sequence for XPath comparisons-->
	<!--DPL?? Category:XmlDoc API methods\|XPathOrder (obsolete XmlDoc property): Collating sequence for XPath comparisons-->		<!--DPL?? Category:XmlDoc API methods\|XPathOrder (obsolete XmlDoc property): Collating sequence for XPath comparisons-->

Admin: 1 revision

2010-12-07T00:33:26Z

1 revision

← Older revision	Revision as of 00:33, 7 December 2010
(No difference)

198.242.244.47: Created page with "Collating sequence for XPath comparisons XPathOrder obsolete property [[Category:XmlDoc API me..."

2010-12-07T00:13:33Z

Created page with "Collating sequence for XPath comparisons XPathOrder obsolete property [[Category:XmlDoc API me..."

New page

Collating sequence for XPath comparisons
[[Category:XmlDoc methods|XPathOrder obsolete property]]
[[Category:XmlDoc API methods]]
[[Category:System methods]]




XPathOrder is a member of the [[XmlDoc class]].


This property indicates what kind of ordered comparison [[Janus SOAP]] uses for
XPath expressions.
'''Note:'''
As described in the [[??]] refid=unxpord page=no.
below, the XPathOrder property is invalid as of ''Sirius Mods'' version 7.3.
===Syntax===
%curr = doc:XPathOrder

doc:XPathOrder = newvalue

====Syntax Terms====
<dl>
<dt>%curr
<dd>The XPathOrder enumeration value of doc's XPathOrder property.
Valid values are <tt>Unicode</tt> and <tt>EBCDIC,</tt> as described
in [[??]] page=no refid=unxpord., below.
<dt>doc
<dd>An XmlDoc object expression.
<dt>newvalue
<dd>The XPathOrder value (see below) to assign to
doc's XPathOrder property.

</dl>

===Usage Notes===
<ul>
<li>Pror to ''Sirius Mods'' version 7.3, the XPathOrder property was available (with a
default value of <tt>Unicode</tt>) to allow EBCDIC ordered string comparisons
in XPath.

As of ''Sirius Mods'' 7.3, only Unicode ordered string comparisons are used, and the
XPathOrder property is '''invalid''', in observance of the following conclusions
about ordered string comparisons in XPath:
<ul>
<li>They are only a feature of the XPath 2 recommendation, which became
a recommendation quite recently (January, 2007).
<li>Careful consideration and discussion with customers leads Sirius to believe
that ordered string comparisons are infrequently used.
<li>If they are used, it is felt that using the XPath 2 standard ordering
rules (that is, the Unicode code point) is the proper approach.
<li>It seems somewhat unlikely that the differences between Unicode and
EBCDIC comparisons would be material in most applications (for example, comparing
decimal digits and alphabetics, and upper- versus lower-case ordering issues).
</ul>
<li>The values of the XPathOrder property are of type Enumeration XPathOrder.
These values, and their meanings, are shown below.
The first example in [[??]] refid=xpoxmp page=no. below describes a case
where you need to be concerned about this property.
For more information about enumerations, see [[Enumerations]].
<dl>
<dt>Unicode
<dd>This is the initial value of the XPathOrder property.
This setting, which corresponds to the string comparison semantics
defined in the XPath Recommendation,
indicates that ordered comparisons in XPath are done with the Unicode
collating sequence.
<dt>EBCDIC
<dd>This setting, which corresponds to the string comparison semantics
performed in User Language,
indicates that ordered comparisons in XPath are done with the EBCDIC
collating sequence.
</dl>
</ul>
===Examples===
<ul>
<li>For example, given this document:
<pre>
<t>
<a a="a"/>

<A A="A"/>

</t>
</pre>

The following table shows the names of elements selected:
<pre>
XPath expression XPathOrder=Unicode XPathOrder=EBCDIC
---------------- ------------------ -----------------
/*/*[@* <= "a"] a A B a
/*/*[@* <= "A"] A a b A
</pre>
These ordering differences should only concern you if,
for example, your User Language application
depends on the ordering of uppercase versus lowercase
letters, and ordering operations of these strings are done
both in User Language expressions and in XPath expresssions.
<li>The following example obtains the string value of the XPathOrder property:
<pre>
%str = doc:XPathOrder:ToString
</pre>
</ul>
===Request-Cancellation Errors (for set method)===
<ul>
<li>newvalue is an invalid value.
</ul>