Paper: XML Matters: GUIs and XML configuration data
33465Paper: XML Matters: GUIs and XML configuration datahttp://www-106.ibm.com/developerworks/xml/library/x-matters34.html?ca=dgr-xw766x-matters34Operating systems -- and in particular their GUIs -- maintain structured, persistent data through a variety of mechanisms and in a variety of formats. Windows versions used INI files, then moved to a binary (and unified) registry; eariler versions of Mac OS had resource forks in the file system and a desktop file for its Finder; Linux and other UNIX-like systems typically used dotted, hidden files in home directories, with configuration detailed in dozens of incompatible ways between window managers and applications.XML > Tips and Tutorials > Introduction to XMLOct 17, 2006
The Java APIs for XML-Based Remote Procedure Call (JAX-RPC) protocol (see Resources) is Java-centric, not WSDL-centric. It contains a fairly elaborate set of rules for mapping WSDL names to Java-friendly names which follow the Java coding conventions. This is good because JAX-RPC users will be Java programmers. In fact, they may not even care that your Web service is a Web service. They probably do not know or care about WSDL and XML, and all the quirks that they bring to the table. All they may care about is that they can write Java code to call your service and expect the JAX-RPC APIs for your service to look familiar; in other words, to follow Java coding conventions.
XML started strong and has grown quite rapidly. It has proven itself a very valuable technology, but it can be an intimidating one, when one considers all the moving parts that fall under the term "XML". In this series of articles, I provide a summary of what I see as the most important XML technologies, and discuss how they each fit into the greater scope of things in the XML world. I also recommend tutorials and other useful resources for evaluating and learning to use each technology.
Because other articles in this issue of the Web Journal describe the motivations for XML and some of its goals, this article is intended to serve as a slightly more technical introduction to XML and as an overview of the specification. Throughout this document you will find references of the form [Section 1]; these are references to the XML language specification included in this issue. If you are interested in more technical detail about a particular topic, please consult the specification.
In my Thinking XML column, I frequently focus on how various industries are working toward semantic transparency, which is the shared meaning of at least the framework of what is communicated in an XML document. Either the industries do so by creating complete document formats along with the semantics of all the elements, attributes, and content, or they define terms and concepts discretely and individually, independently of the documents in which they would appear. I call these approaches top-down and bottom-up, respectively, and very active communities provide useful material on each.
Joining mailing list will entitle you
to receive occasional emails informing you of news and
updates to the site and any special offers that may be
of interest to you.