(Alexander Wolfe) The speculation as to whether Microsoft intends to patent XML technology is over. Microsoft has been granted United States patent 6,687,897 for “XML script automation.” The patent, award by the U.S. Patent and Trademark Office on February 3, appears to deal with basic XML f
Tag: JSON / JAVA / XML
XSLT as an analysis tool
(Chuck White) XSLT is meant to change the form of XML, but you can also use it to perform analysis. In this tutorial, the second in a series, the MindMap team creates a system that enables them to pass parameters that not only determine the properties to analyze but also change the desired criteria
Create Versatile Web Services From Stored Procedures
(Roger Jennings) Web services are a moving target and Microsoft’s SQLXML 3.0 is no exception. If you downloaded the code from my January 2002 FTPOnline article, “Generate XML Web Services from Stored Procedures,” and the SQLXML 3.0 Beta bits within two weeks of its publication, the sample SQLXML3 Wi
Web Architecture Review: Representation
(Kendall Grant Clark) In this column I shall examine the third of the three key architectural principles of the AWWW, which it calls “data formats” but which I choose to call “representation”, following the first two principles, identification and interaction.
Exporting Access 2003 Data to XML
For those of you who are already familiar with XML in Access 2002, note that the enhanced XML support in Access 2003 enables you to specify XSL (Extensible Stylesheet Language) transform files when importing data from, or exporting data to, XML. When importing, the transform is applied to data as so
Validating XML
(Nicholas Chase) In the creation of a database, a data model and integrity constraints can create certainty in the structure and content of the data. But how do you enforce that kind of control when your data is just text in hand-editable files? Fortunately, validating files and documents can ma
Competing Claims and Interaction Types
(Kendall Grant Clark) In this week’s XML-Deviant column I am continuing my slog through the W3C TAG’s Architecture of the World Wide Web (AWWW). In last week’s column I examined some of the key issues surrounding the second of the AWWW’s key architectural principles, namely, interaction. I will conc
Why XML 1.1?
(Eric van der Vlist) I’d better say it right now, though XML 1.1 and namespaces in XML 1.1 do not include that many changes compared to XML 1.0 and namespaces in XML 1.0, these changes are enough to break the compatibility: a well formed XML 1.1 document isn’t necessarily a well formed XML 1.0 docum
Chapter 5: Reading XML
(Elliotte Rusty Harold) Writing XML documents is very straightforward, as I hope Chapters 3 and 4 proved. Reading XML documents is not nearly as simple. Fortunately, you don’t have to do all the work yourself; you can use an XML parser to read the document for you. The XML parser exposes the content
Namespace Myths Exploded
(Ronald Bourret) The XML namespaces recommendation is tantalizingly vague about, or omits altogether, a number of apparently important points. In practice, this is not a problem—the points are not actually important and the recommendation does what it was designed to do: provide a two-part naming sy
