XmlDoc API serialization options - Revision history

JAL at 20:38, 13 March 2014

2014-03-13T20:38:22Z

← Older revision		Revision as of 20:38, 13 March 2014
Line 635:		Line 635:
	followed by an end tag), not with a single empty-element tag.		followed by an end tag), not with a single empty-element tag.
	</ul>		</ul>

			==See also==
			<ul>
			<li>For additional discussion about serialization, see [[XmlDoc API#Transport: receiving and sending XML\|Transport: receiving and sending XML]].</li>
			</li>

	[[Category: Janus SOAP]]		[[Category: Janus SOAP]]

JAL at 20:36, 11 March 2014

2014-03-11T20:36:40Z

← Older revision		Revision as of 20:36, 11 March 2014
Line 635:		Line 635:
	followed by an end tag), not with a single empty-element tag.		followed by an end tag), not with a single empty-element tag.
	</ul>		</ul>

			[[Category: Janus SOAP]]

JAL: /* Character references */

2014-03-11T15:54:35Z

Character references

← Older revision		Revision as of 15:54, 11 March 2014
Line 625:		Line 625:
	</p>		</p>

	The differences (green font) from no-option <var>Serial</var> include:		The differences (<span class="boldGreen">green</span> font) from no-option <var>Serial</var> include:
	<ul>		<ul>
	<li>The greater-than symbol (<tt>></tt>) within a text node is serialized		<li>The greater-than symbol (<tt>></tt>) within a text node is serialized

JAL: /* Character references */

2014-03-11T15:52:39Z

Character references

← Older revision		Revision as of 15:52, 11 March 2014
Line 625:		Line 625:
	</p>		</p>

	The differences from no-option <var>Serial</var> ~~(green font)~~ include:		The differences (green font) from no-option <var>Serial</var> include:
	<ul>		<ul>
	<li>The greater-than symbol (>) within a text node is serialized		<li>The greater-than symbol (<tt>></tt>) within a text node is serialized
	as <code>&gt;</code>.		as <code>&gt;</code>.
	<li>Attribute values are enclosed in double-quotation marks (<code>"</code>).		<li>Attribute values are enclosed in double-quotation marks (<code>"</code>).

JAL: /* Canonicalization */

2014-03-10T18:01:06Z

Canonicalization

Show changes

JAL: /* EBCDIC serialization of untranslatable Unicode characters */

2014-03-10T17:40:06Z

EBCDIC serialization of untranslatable Unicode characters

← Older revision		Revision as of 17:40, 10 March 2014
Line 256:		Line 256:
	</p>		</p>

	('''Note:''' prior to version 8.0 of the <var class="product">Sirius Mods</var>, the <var>Serial</var> method did not convert non-translatable Unicode characters to character references; the result was, instead, a request cancellation.)		<p class="note">'''Note:''' prior to version 8.0 of the <var class="product">Sirius Mods</var>, the <var>Serial</var> method did not convert non-translatable Unicode characters to character references; the result was, instead, a request cancellation. </p>

	However~~, with default serialization options~~, when an untranslatable		However, when an untranslatable Unicode character occurs in a context other than <var>Element</var> or <var>Attribute</var> value
	Unicode character occurs in a context other than <var>Element</var> or <var>Attribute</var> value		(that is, a name, comment, or PI), and the default serialization options are in effect, character encoding is '''not''' used.
	(that is, a name, comment, or PI), character encoding is '''not''' used.		Because it is an <var>Element</var> name, for example, the following statements result in a
	Because it is an ~~element~~ name, for example, the following statements result in a
	request cancellation:		request cancellation:
	<p class="code"> %doc:AddElement('&#x2122;':U)		<p class="code"> %doc:AddElement('&#x2122;':U)
Line 278:		Line 277:
	<p class="output"> <&#x2122;/>		<p class="output"> <&#x2122;/>
	</p>		</p>
	'''Note:'''		<blockquote class="note">
			<p>'''Note:'''
	The result with <var>CharacterEncodeAll</var> can be misleading.		The result with <var>CharacterEncodeAll</var> can be misleading.
	Request cancellation is avoided, but it can produce a serialization ~~which~~ is <b>not</b> equivalent to the portion of the <var>XmlDoc</var> ~~which~~ was serialized.		Request cancellation is avoided, but it can produce a serialization that is <b>not</b> equivalent to the portion of the <var>XmlDoc</var> that was serialized. </p>

	The serialized result above is not a legal XML document,		The serialized result above is not a legal XML document,
Line 301:		Line 301:
	</nowiki></p>		</nowiki></p>

	This may lead you to believe that the two Comment nodes in the <var>XmlDoc</var> are identical, but the first one contains the 8 characters <code>&#x2122;</code>, whereas the second comment contains a single Unicode "trademark" character (<~~code~~>™</~~code~~>).		This may lead you to believe that the two Comment nodes in the <var>XmlDoc</var> are identical, but the first one contains the 8 characters <code>&#x2122;</code>, whereas the second comment contains a single Unicode "trademark" character (<b>™</b>).
			</blockquote>

	==Serialization and the "xml:space" attribute==		==Serialization and the "xml:space" attribute==

JAL at 01:18, 8 March 2014

2014-03-08T01:18:11Z

Show changes

JAL: /* EBCDIC serialization of untranslatable Unicode characters */

2012-11-06T19:45:24Z

EBCDIC serialization of untranslatable Unicode characters

← Older revision		Revision as of 19:45, 6 November 2012
Line 283:		Line 283:

	The serialized result above is not a legal XML document,		The serialized result above is not a legal XML document,
	because the ampersand (<~~code~~>&</~~code~~>) is not a legal name character.		because the ampersand (<tt>&</tt>) is not a legal name character.
	Similarly, for		Similarly, for
	an untranslatable Unicode character added to a document		an untranslatable Unicode character added to a document

JALWiccan: 1 revision

2012-11-06T18:22:52Z

1 revision

← Older revision	Revision as of 18:22, 6 November 2012
(No difference)

JAL2: /* EBCDIC serialization of untranslatable Unicode characters */

2012-11-06T18:22:37Z

EBCDIC serialization of untranslatable Unicode characters

← Older revision		Revision as of 18:22, 6 November 2012
Line 403:		Line 403:
	as entity and hexadecimal character references:		as entity and hexadecimal character references:
	<ul>		<ul>
	<li>The ampersand (&) is serialized as <code>&~~amp;amp;~~</code>		<li>The ampersand (&) is serialized as <code>&</code>
	<li>The less-than symbol (<) is serialized as <code>&lt;</code>		<li>The less-than symbol (<) is serialized as <code>&lt;</code>
	<li>The carriage return (CR) character is serialized as <code>&#xD;</code>		<li>The carriage return (CR) character is serialized as <code>&#xD;</code>
Line 418:		Line 418:
	<ul>		<ul>
	<li>The less-than symbol (<tt><</tt>) is serialized as <code>&lt;</code>		<li>The less-than symbol (<tt><</tt>) is serialized as <code>&lt;</code>
	<li>The ampersand (<tt>&</tt>) is serialized as <code>&~~amp;amp;~~</code>		<li>The ampersand (<tt>&</tt>) is serialized as <code>&</code>
	<li>The carriage return (CR) character is serialized as <code>&#xD;</code>		<li>The carriage return (CR) character is serialized as <code>&#xD;</code>
	</ul>		</ul>