XML processing in Janus SOAP - Revision history

JAL: minor cleanup

2016-05-13T19:17:47Z

minor cleanup

← Older revision		Revision as of 19:17, 13 May 2016
Line 7:		Line 7:
	<var class="product">[[Janus SOAP]]</var> provides <var class="product">[[SOUL]]</var> programmers with a substantial set of facilities for processing eXtensible Markup		<var class="product">[[Janus SOAP]]</var> provides <var class="product">[[SOUL]]</var> programmers with a substantial set of facilities for processing eXtensible Markup
	Language (XML) documents.		Language (XML) documents.
	Among other benefits,		Among other benefits, this enables rich and automated Web services based on a shared and open Web infrastructure.
	this enables rich and automated Web services based on a shared and open Web infrastructure.
	The design of this XML support is based on various standards, such as XML and [[XPath]].		The design of this XML support is based on various standards, such as XML and [[XPath]].
	Many sections in this article refer to these and other standards,		Many sections in this article refer to these and other standards,
	for example, [[#Simple Object Access Protocol (SOAP)\|Simple Object Access Protocol (SOAP)]].		for example, [[#Simple Object Access Protocol (SOAP)\|Simple Object Access Protocol (SOAP)]].
	However, it is important to recognize:		However, it is important to recognize:
	<blockquote><var class="product">Janus SOAP</var> enables you to process <i><b>any XML document</b></i>, whether or not you are using		<blockquote><var class="product">Janus SOAP</var> enables you to process <i><b>any XML document</b></i>, whether or not you are using SOAP messages and envelopes.
	SOAP messages and envelopes.
	</blockquote>		</blockquote>

Line 551:		Line 549:
	<tr><th>&quot;</th>		<tr><th>&quot;</th>
	<td>double quotation mark (<tt>"</tt>)</td></tr>		<td>double quotation mark (<tt>"</tt>)</td></tr>

			<tr><th>&lsqb; <br>&rsqb;</th>
			<td>left and right square brackets (<tt>[</tt> <tt>]</tt>) <br>(as of Model 204 7.6)</td></tr>
	</table>		</table>

	<blockquote class="note">		<blockquote class="note">
	<p>'''Note:''' ~~As of <var class="product">Sirius Mods</var> version 7.6, you~~ can use any of the XHTML entities (listed at http://www.w3.org/TR/xhtml1/dtds.html#h-A2)		<p>'''Note:''' You can use any of the XHTML entities (listed at http://www.w3.org/TR/xhtml1/dtds.html#h-A2)
	to represent Unicode characters when converting from EBCDIC to Unicode.		to represent Unicode characters when converting from EBCDIC to Unicode.
	Character decoding must be in effect, however: you must be using		Character decoding must be in effect, however: you must be using
	the <var>[[U (String function)\|U]]</var> constant function or the <code>CharacterDecode=True</code>		the <var>[[U (String function)\|U]]</var> constant function or the <code>CharacterDecode=True</code> argument on the <var>[[EbcdicToUnicode (String function)\|EbcdicToUnicode]]</var> function. </p>
	argument on the <var>[[EbcdicToUnicode (String function)\|EbcdicToUnicode]]</var> function. </p>

	You can load into an <var>XmlDoc</var> a character represented by such an entity if you decode the entity reference before the character is processed by one of the XmlDoc API deserializing or direct storage methods. </blockquote>		You can load into an <var>XmlDoc</var> a character represented by such an entity if you decode the entity reference before the character is processed by one of the XmlDoc API deserializing or direct storage methods. </blockquote>

JAL: /* Syntax of document, element, Attribute, Comment, PI */

2014-03-11T19:59:12Z

Syntax of document, element, Attribute, Comment, PI

← Older revision		Revision as of 19:59, 11 March 2014
Line 467:		Line 467:
	[T21] CDEnd ::= ']]>'		[T21] CDEnd ::= ']]>'

	[U15] Comment ::= '<!--' ( (Char - '-') \| ('-' (Char - '-')) )* '-->'		[U15] Comment ::= '<!--' ( (Char - '-') \| ('-' (Char - '-')) )* '-->'

	[V16] PI ::= '<?' PITarget (S (Char* (Char* '?>' Char*) ))? '?>'		[V16] PI ::= '<?' PITarget (S (Char* (Char* '?>' Char*) ))? '?>'

JAL: /* Syntax of document, element, Attribute, Comment, PI */

2014-03-11T19:35:47Z

Syntax of document, element, Attribute, Comment, PI

← Older revision		Revision as of 19:35, 11 March 2014
Line 423:		Line 423:
	[D27] Misc ::= Comment \| PI \| S		[D27] Misc ::= Comment \| PI \| S

	[E3] S ::= (#x20 \| #x9 /* Whitespace */ \| #xD \| #xA)+		[E3] S ::= (#x20 \| #x9 /* Whitespace */ \| #xD \| #xA)+

	[F39] element ::= STag content ETag [Element Type Match] \| EmptyElemTag		[F39] element ::= STag content ETag [Element Type Match] \| EmptyElemTag
Line 473:		Line 473:
	[W17] PITarget ::= Name - (('X' \| 'x') ('M' \| 'm') ('L' \| 'l'))		[W17] PITarget ::= Name - (('X' \| 'x') ('M' \| 'm') ('L' \| 'l'))
	</p>		</p>

	====Char and Reference====		====Char and Reference====
	<p class="code">[CA2] Char ::= [#x1-#xD7FF] \| [#xE000-#xFFFD]		<p class="code">[CA2] Char ::= [#x1-#xD7FF] \| [#xE000-#xFFFD]

JAL at 19:20, 11 March 2014

2014-03-11T19:20:58Z

Show changes

JAL: /* Language identification */

2014-03-11T18:41:54Z

Language identification

← Older revision		Revision as of 18:41, 11 March 2014
Line 943:		Line 943:
	and attribute values of any element in an XML document.”		and attribute values of any element in an XML document.”

	~~In versions~~ of ~~<var class="product">Janus SOAP</var> prior to 6.8,~~ the <code>xml:lang=".."</code>		The only valid values of the <code>xml:lang=".."</code> attribute that <var class="product">Janus SOAP</var> accepts are the language identifier tags specified in IETF RFC 3066 (http://www.w3.org/TR/REC-xml/#RFC1766).
	attribute ~~was accepted regardless of its value.~~
	~~As of version 6.8, the only valid values of such attributes~~ are
	the language identifier tags specified in IETF RFC 3066
	(http://www.w3.org/TR/REC-xml/#RFC1766).

	==References==		==References==
	As mentioned, the XML support in <var class="product">Janus SOAP</var> is heavily oriented to the concepts and facilities defined by		As mentioned, the XML support in <var class="product">Janus SOAP</var> is heavily oriented to the concepts and facilities defined by

JAL at 18:17, 11 March 2014

2014-03-11T18:17:53Z

Dme at 19:49, 28 June 2013

2013-06-28T19:49:08Z

← Older revision		Revision as of 19:49, 28 June 2013
Line 9:		Line 9:
	Among other benefits,		Among other benefits,
	this enables rich and automated Web services based on a shared and open Web infrastructure.		this enables rich and automated Web services based on a shared and open Web infrastructure.
	The design of this XML support is based on various standards, such as XML and XPath.		The design of this XML support is based on various standards, such as XML and [[XPath]].
	Many sections in this article refer to these and other standards,		Many sections in this article refer to these and other standards,
	for example, [[#Simple Object Access Protocol (SOAP)\|Simple Object Access Protocol (SOAP)]].		for example, [[#Simple Object Access Protocol (SOAP)\|Simple Object Access Protocol (SOAP)]].

JAL at 15:53, 30 May 2013

2013-05-30T15:53:26Z

← Older revision		Revision as of 15:53, 30 May 2013
Line 1,024:		Line 1,024:

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

JAL: /* W3C standards */

2012-11-30T18:49:43Z

W3C standards

← Older revision		Revision as of 18:49, 30 November 2012
Line 997:		Line 997:
	<td>W3C Recommendation 04 February 2004: <br>http://www.w3.org/TR/REC-xml		<td>W3C Recommendation 04 February 2004: <br>http://www.w3.org/TR/REC-xml
	<p>		<p>
	This is referred to as the <i~~><b~~>W3C XML Recommendation~~</b>~~</i> throughout this article. </p></td></tr>		This is referred to as the <i>W3C XML Recommendation</i> throughout this article. </p></td></tr>
	<tr><th>Namespaces spec </th>		<tr><th>Namespaces spec </th>
	<td>http://www.w3.org/TR/REC-xml-names		<td>http://www.w3.org/TR/REC-xml-names

JAL: /* Normalized attribute value */

2012-11-30T18:47:10Z

Normalized attribute value

← Older revision		Revision as of 18:47, 30 November 2012
Line 897:		Line 897:

	=====Normalized attribute value=====		=====Normalized attribute value=====
	After replacing all CR-LF sequences, and all other CR instances,		After replacing all CR-LF sequences, and all other CR instances, by LF (as described in [[#Normalized line-end\|"Normalized line-end"]]),
	by LF (as described in [[#Normalized line-end\|Normalized line-end]]),
	attribute values have additional whitespace normalization.		attribute values have additional whitespace normalization.
	As specified in ~~“~~3.3.3 Attribute-Value Normalization~~”~~ of the <i~~><b~~>W3C XML Recommendation~~</b>~~</i>,		As specified in "3.3.3 Attribute-Value Normalization" of the <i>W3C XML Recommendation</i>,
	after the CR-LF normalization, every instance of a		after the CR-LF normalization, every instance of a whitespace character (tab and linefeed)
	whitespace character (tab and linefeed)
	in an attribute value is converted to a space character.		in an attribute value is converted to a space character.
	Leading and trailing spaces		Leading and trailing spaces are not stripped, nor are sequences of multiple spaces collapsed.
	are not stripped, nor are sequences of multiple spaces
	collapsed.

	This behavior only applies to deserialization; that is, there is no modification		This behavior only applies to deserialization; that is, there is no modification
	of whitespace characters in attribute values passed as the <~~i><b~~>value</~~b></i~~>		of whitespace characters in attribute values passed as the <var class="term">value</var>
	argument of the [[AddAttribute (XmlNode function)\|AddAttribute]] function..		argument of the <var>[[AddAttribute (XmlNode function)\|AddAttribute]]</var> function.
	Therefore the values of the ~~“~~FOO~~”~~ attribute created by the following two		Therefore the values of the <code>FOO</code> attribute created by the following two methods are different:
	methods are different:		<p class="code">* Get EBCDIC carriage return:
	<p class="code">		%c = $X2C('0D')
	* Get EBCDIC carriage return:
	%c = $X2C('0D')

	* Attribute value is space:		* Attribute value is space:
	%doc:LoadXml('<top FOO="' With %c With '"> <in/> </top>')		%doc:LoadXml('<top FOO="' With %c With '"> <in/> </top>')

	* Attribute value is carriage return:		* Attribute value is carriage return:
	%doc:AddAttribute('FOO', %c, '//')		%doc:AddAttribute('FOO', %c, '//')
	</p>		</p>

	Also, the normalization applies to the characters in the input		Also, the normalization applies to the characters in the input serialized string, not the values after entity substitution.
	serialized string, not the values after entity substitution.		Therefore the values of the <code>FOO</code> attribute created by the following two <var>LoadXml</var> invocations are different:
	Therefore the values of the ~~“~~FOO~~”~~ attribute created by the following two		<p class="code">* Get EBCDIC carriage return:
	LoadXml invocations are different:		%c = $X2C('0D')
	<p class="code">
	* Get EBCDIC carriage return:
	%c = $X2C('0D')

	* Attribute value is space:		* Attribute value is space:
	%doc:LoadXml('<top FOO="' With %C With '"/>')		%doc:LoadXml('<top FOO="' With %C With '"/>')
	%doc = New		%doc = New

	* Attribute value is carriage return - note CR		* Attribute value is carriage return - note CR
	* is the same in EBCDIC and ISO-10646:		* is the same in EBCDIC and ISO-10646:
	%doc:LoadXml('<top FOO="#x0D;"/>')		%doc:LoadXml('<top FOO="#x0D;"/>')
	</p>		</p>
	'''Note:'''
	Whitespace in an attribute (and in any type of node other than		'''Note:''' Whitespace in an attribute (and in any type of node other than
	a Text node child of an element) is '''not''' affected by the		a Text node child of an element) is '''not''' affected by the
	whitespace-handling options of [[LoadXml (XmlDoc/XmlNode function)\|LoadXml]],		whitespace-handling options of <var>[[LoadXml (XmlDoc/XmlNode function)\|LoadXml]]</var>,
	[[WebReceive (XmlDoc function)\|WebReceive]], and [[ParseXml (HttpResponse function)\|ParseXml]].		<var>[[WebReceive (XmlDoc function)\|WebReceive]]</var>, and <var>[[ParseXml (HttpResponse function)\|ParseXml]]</var>.

	===Language identification===		===Language identification===

← Older revision		Revision as of 18:17, 11 March 2014
Line 5:		Line 5:
	Comments with "&NSPRVSN" are places that could be revisited when "SOAP rule" support available		Comments with "&NSPRVSN" are places that could be revisited when "SOAP rule" support available
	-->		-->
	<var class="product">[[Janus SOAP]]</var> provides <var class="product">~~User Language~~</var> programmers with a substantial set of facilities for processing eXtensible Markup		<var class="product">[[Janus SOAP]]</var> provides <var class="product">[[SOUL]]</var> programmers with a substantial set of facilities for processing eXtensible Markup
	Language (XML) documents.		Language (XML) documents.
	Among other benefits,		Among other benefits,
Line 167:		Line 167:
	It gives you basic information about XML, explaining some of the concepts using the XmlDoc API (that is,		It gives you basic information about XML, explaining some of the concepts using the XmlDoc API (that is,
	the methods of the <var>XmlDoc</var>, <var>XmlNodelist</var>, and <var>XmlNode</var> classes).		the methods of the <var>XmlDoc</var>, <var>XmlNodelist</var>, and <var>XmlNode</var> classes).
	This approach gives you concrete examples which you can try in <var class="product">~~User Language~~</var>,		This approach gives you concrete examples which you can try in <var class="product">SOUL</var>,
	and which may make the abstract concepts easier to understand.		and which may make the abstract concepts easier to understand.

Line 338:		Line 338:
	of the deserialization functions (<var>[[LoadXml (XmlDoc/XmlNode function)\|LoadXml]]</var>,		of the deserialization functions (<var>[[LoadXml (XmlDoc/XmlNode function)\|LoadXml]]</var>,
	<var>[[WebReceive (XmlDoc function)\|WebReceive]]</var>, and <var>[[ParseXml (HttpResponse function)\|ParseXml]]</var>)		<var>[[WebReceive (XmlDoc function)\|WebReceive]]</var>, and <var>[[ParseXml (HttpResponse function)\|ParseXml]]</var>)
	— the information contained in the DTD is not used nor made available to the <var class="product">~~User Language~~</var> program.		— the information contained in the DTD is not used nor made available to the <var class="product">SOUL</var> program.

	Reflecting the absence of support for DTD, the productions in the syntax that follows are altered to remove those		Reflecting the absence of support for DTD, the productions in the syntax that follows are altered to remove those