Lib/xml - Revision history

Hzwakenberg at 15:38, 30 July 2024

2024-07-30T15:38:55Z

← Older revision		Revision as of 17:38, 30 July 2024
Line 64:		Line 64:
	Namespaces are not yet natively implemented in Liberty Eiffel, but they will be added later ('''contributions welcome!!''')		Namespaces are not yet natively implemented in Liberty Eiffel, but they will be added later ('''contributions welcome!!''')

−	The idea is to implement some new kind of XML_CALLBACK that takes the ~~semi-colon~~ in nodes names into account.	+	The idea is to implement some new kind of XML_CALLBACK that takes the semicolon in nodes names into account.

	Schema validation (therefore using namespaces) may be set by calling <tt>[[library_class:XML_CALLBACKS\|XML_CALLBACKS]].set_validator</tt>.		Schema validation (therefore using namespaces) may be set by calling <tt>[[library_class:XML_CALLBACKS\|XML_CALLBACKS]].set_validator</tt>.

Hzwakenberg at 15:37, 30 July 2024

2024-07-30T15:37:21Z

← Older revision		Revision as of 17:37, 30 July 2024
Line 16:		Line 16:
	In this case, you have to inherit from [[library_class:XML_CALLBACKS\|<tt>XML_CALLBACKS</tt>]] and implement its many deferred features.		In this case, you have to inherit from [[library_class:XML_CALLBACKS\|<tt>XML_CALLBACKS</tt>]] and implement its many deferred features.

−	During the parsing, the [[library_class:XML_PARSER\|XML parser]] calls that class to tell it it enters a node, finds some attribute, some text, and so on. Errors are also reported.	+	During the parsing, the [[library_class:XML_PARSER\|XML parser]] calls that class to tell it, it enters a node, finds some attribute, some text, and so on. Errors are also reported.

	=== Tree interface ("DOM") ===		=== Tree interface ("DOM") ===

Hzwakenberg: /* XML parsing */

2018-09-04T20:50:15Z

XML parsing

← Older revision		Revision as of 22:50, 4 September 2018
Line 2:		Line 2:
	== XML parsing ==		== XML parsing ==

−	XML is used a lot these days, ~~including~~ by the library itself (the [[library_class:STORABLE\|storable]] [[library_class:REPOSITORY\|repository]] uses it, see [[lib/storage]]).	+	XML is used a lot these days, even by the library itself (the [[library_class:STORABLE\|storable]] [[library_class:REPOSITORY\|repository]] uses it, see [[lib/storage]]).

	=== The parser ===		=== The parser ===

Dkearns: s/LibertyEiffel/Liberty Eiffel/

2016-07-03T06:48:45Z

s/LibertyEiffel/Liberty Eiffel/

Hzwakenberg: type

2016-06-12T18:20:16Z

type

← Older revision		Revision as of 20:20, 12 June 2016
Line 64:		Line 64:
	Namespaces are not yet natively implemented in LibertyEiffel, but they will be added later ('''contributions welcome!!''')		Namespaces are not yet natively implemented in LibertyEiffel, but they will be added later ('''contributions welcome!!''')

−	The idea is to implement some new kind of ~~XML_CALLBACKS~~ that takes the semi-colon in nodes names into account.	+	The idea is to implement some new kind of XML_CALLBACK that takes the semi-colon in nodes names into account.

	Schema validation (therefore using namespaces) may be set by calling <tt>[[library_class:XML_CALLBACKS\|XML_CALLBACKS]].set_validator</tt>.		Schema validation (therefore using namespaces) may be set by calling <tt>[[library_class:XML_CALLBACKS\|XML_CALLBACKS]].set_validator</tt>.

Hzwakenberg at 10:44, 7 September 2014

2014-09-07T10:44:00Z

← Older revision		Revision as of 12:44, 7 September 2014
Line 1:		Line 1:
		+	[[Category: Library]]
	== XML parsing ==		== XML parsing ==

Hzwakenberg at 10:34, 7 September 2014

2014-09-07T10:34:01Z

← Older revision		Revision as of 12:34, 7 September 2014
Line 1:		Line 1:
	== XML parsing ==		== XML parsing ==

−	XML is used a lot ~~those~~ days, including by the library itself (the [[library_class:STORABLE\|storable]] [[library_class:REPOSITORY\|repository]] uses it, see [[lib/storage]]).	+	XML is used a lot these days, including by the library itself (the [[library_class:STORABLE\|storable]] [[library_class:REPOSITORY\|repository]] uses it, see [[lib/storage]]).

	=== The parser ===		=== The parser ===
Line 13:		Line 13:
	[http://www.saxproject.org/ SAX] means "Simple API for XML". LibertyEiffel's API is not exactly identical; nonetheless it resembles the API found in other languages.		[http://www.saxproject.org/ SAX] means "Simple API for XML". LibertyEiffel's API is not exactly identical; nonetheless it resembles the API found in other languages.

−	In ~~that~~ case, you have to inherit from [[library_class:XML_CALLBACKS\|<tt>XML_CALLBACKS</tt>]] and implement its many deferred features.	+	In this case, you have to inherit from [[library_class:XML_CALLBACKS\|<tt>XML_CALLBACKS</tt>]] and implement its many deferred features.

	During the parsing, the [[library_class:XML_PARSER\|XML parser]] calls that class to tell it it enters a node, finds some attribute, some text, and so on. Errors are also reported.		During the parsing, the [[library_class:XML_PARSER\|XML parser]] calls that class to tell it it enters a node, finds some attribute, some text, and so on. Errors are also reported.
Line 29:		Line 29:
	=== Small Comparison SAX vs. DOM ===		=== Small Comparison SAX vs. DOM ===

−	Using one or the other is not only a matter of taste, but it also depends on where you put your priorities. In a ~~word~~, it is performance ~~vs.~~ simplicity.	+	Using one or the other is not only a matter of taste, but it also depends on where you put your priorities. In other words, you have to evaluate performance against simplicity.

	{\| cellspacing="10px" width="100%"		{\| cellspacing="10px" width="100%"

Hzwakenberg at 17:58, 5 September 2014

2014-09-05T17:58:19Z

← Older revision		Revision as of 19:58, 5 September 2014
Line 1:		Line 1:
−	[[Category:Smarteiffel]]
	== XML parsing ==		== XML parsing ==

Hzwakenberg: /* Namespaces and other advanced features */

2014-08-02T18:29:04Z

Namespaces and other advanced features

← Older revision		Revision as of 20:29, 2 August 2014
Line 62:		Line 62:
	== Namespaces and other advanced features ==		== Namespaces and other advanced features ==

−	Namespaces are not yet natively implemented in ~~SmartEiffel~~, but they will be added later ('''contributions welcome!!''')	+	Namespaces are not yet natively implemented in LibertyEiffel, but they will be added later ('''contributions welcome!!''')

	The idea is to implement some new kind of XML_CALLBACKS that takes the semi-colon in nodes names into account.		The idea is to implement some new kind of XML_CALLBACKS that takes the semi-colon in nodes names into account.

Hzwakenberg: /* Validation */

2014-08-02T18:27:15Z

Validation

← Older revision		Revision as of 20:27, 2 August 2014
Line 56:		Line 56:
	== Validation ==		== Validation ==

−	To validate an XML file, ~~SmartEiffel~~ provides a DTD parser. The XML parser may parse the provided DTD and validate your file.	+	To validate an XML file, LibertyEiffel provides a DTD parser. The XML parser may parse the provided DTD and validate your file.

	The parser recognizes any kind of DTD: inlined, in a file or on the network. You may also use a cache that locally provides network DTDs (see [[library_class:XML_DTD_PUBLIC_REPOSITORY\|<tt>XML_DTD_PUBLIC_REPOSITORY</tt>]]).		The parser recognizes any kind of DTD: inlined, in a file or on the network. You may also use a cache that locally provides network DTDs (see [[library_class:XML_DTD_PUBLIC_REPOSITORY\|<tt>XML_DTD_PUBLIC_REPOSITORY</tt>]]).

← Older revision		Revision as of 08:48, 3 July 2016
Line 12:		Line 12:
	=== Events interface ("SAX") ===		=== Events interface ("SAX") ===

−	[http://www.saxproject.org/ SAX] means "Simple API for XML". ~~LibertyEiffel~~'s API is not exactly identical; nonetheless it resembles the API found in other languages.	+	[http://www.saxproject.org/ SAX] means "Simple API for XML". Liberty Eiffel's API is not exactly identical; nonetheless it resembles the API found in other languages.

	In this case, you have to inherit from [[library_class:XML_CALLBACKS\|<tt>XML_CALLBACKS</tt>]] and implement its many deferred features.		In this case, you have to inherit from [[library_class:XML_CALLBACKS\|<tt>XML_CALLBACKS</tt>]] and implement its many deferred features.
Line 20:		Line 20:
	=== Tree interface ("DOM") ===		=== Tree interface ("DOM") ===

−	[http://www.w3.org/DOM/ DOM] means "Document Object Model". ~~LibertyEiffel~~'s DOM implementation is not endorsed by W3C but its API is equivalent.	+	[http://www.w3.org/DOM/ DOM] means "Document Object Model". Liberty Eiffel's DOM implementation is not endorsed by W3C but its API is equivalent.

	To use an [[library_class:XML_TREE\|XML tree]], you have to give it to the [[library_class:XML_PARSER\|XML parser]]. The tree builds itself when called back by the parser's events.		To use an [[library_class:XML_TREE\|XML tree]], you have to give it to the [[library_class:XML_PARSER\|XML parser]]. The tree builds itself when called back by the parser's events.
Line 56:		Line 56:
	== Validation ==		== Validation ==

−	To validate an XML file, ~~LibertyEiffel~~ provides a DTD parser. The XML parser may parse the provided DTD and validate your file.	+	To validate an XML file, Liberty Eiffel provides a DTD parser. The XML parser may parse the provided DTD and validate your file.

	The parser recognizes any kind of DTD: inlined, in a file or on the network. You may also use a cache that locally provides network DTDs (see [[library_class:XML_DTD_PUBLIC_REPOSITORY\|<tt>XML_DTD_PUBLIC_REPOSITORY</tt>]]).		The parser recognizes any kind of DTD: inlined, in a file or on the network. You may also use a cache that locally provides network DTDs (see [[library_class:XML_DTD_PUBLIC_REPOSITORY\|<tt>XML_DTD_PUBLIC_REPOSITORY</tt>]]).
Line 62:		Line 62:
	== Namespaces and other advanced features ==		== Namespaces and other advanced features ==

−	Namespaces are not yet natively implemented in ~~LibertyEiffel~~, but they will be added later ('''contributions welcome!!''')	+	Namespaces are not yet natively implemented in Liberty Eiffel, but they will be added later ('''contributions welcome!!''')

	The idea is to implement some new kind of XML_CALLBACK that takes the semi-colon in nodes names into account.		The idea is to implement some new kind of XML_CALLBACK that takes the semi-colon in nodes names into account.