The Extensible Markup Language (XML) is an open, general-purpose specification for creating markup languages. Its primary purpose is to help information systems share structured data, particularly via the Internet, and it is used both to encode documents and to serialize data. It is used in a wide variety of technical communication document formats, including Microsoft Word, OpenOffice, XHTML, DITA, DocBook, and RSS, among others.
While computing the Mathematical Sciences is similar to other scientific areas, often the researcher lacks the resources to carry out those computations. Grid computing and web services provide some possibilities for solutions but they do not address the increasing demand for computing resources and ad hoc computation networks. This paper describes a solution to this that uses peer-to-peer technologies to build ad hoc networks of computational agents that all speak XML to carry out computations.
This presentation is for beginning to intermediate users of DITA. It's based on my experience with projects on which I'm project manager, information architect, and writer.
Conflict resolution is required wherever we have multiple concurrent changes to a single information set. In practical terms this applies, for example, to concurrent editing environments, to replicated database instances which are being updated independently, to address-book changes on a PDA that must be merged into a master database that has itself been changed. Resolving these conflicts very often requires human intervention. This paper looks at the use of XML forms of various types to reduce the drudgery involved and to take advantage some of the greatest strengths of XML, using pipelining and easily-understood representations to allow a decision-maker to work with minimal drag.
Panellists talk about two vendor-neutral programming interfaces for content-management systems. Joel Amoussou discusses JSR 170, a vendor-neutral Java API designed to work across many different content management systems. Michael Wechner discusses Neutron, an Open Content Management User Interface based on XML.
For years you've been hearing about how structured authoring and XML-based workflows can help technical authors reuse content more efficiently. By converting all of your topics to an XML standard, investing in a CMS, and building custom DTDs and XSLT translations, you can avoid having to maintain duplicate content. The downside? Months of time invested in research, evaluation, and conversion only to be followed by a steep learning curve as your team adjusts to a new workflow.
XML considers four characters to be whitespace: the carriage return, the linefeed, the tab, and the spacebar space. Microsoft operating systems put both a carriage return and a linefeed at the end of each line of a text file, and people usually refer to the combination as the "carriage return". XSLT stylesheet developers often get frustrated over the whitespace that shows up in their result documents -- sometimes there's more than they wanted, sometimes there's less, and sometimes it's in the wrong place. Over the next few columns, we'll discuss how XML and XSLT treat whitespace to gain a better understanding of what can happen, and we'll look at some techniques for controlling how an XSLT processor adds whitespace to the result document.
Converting an Atom document to JSON might, at first, appear to be a fairly straightforward task. Atom is, after all, just a bit of XML and XML-to-JSON conversion tools are widely available. However, the Atom format is more than just a set of XML elements and attributes. A number of subtle details can make proper handling of Atom difficult. This article describes those issues and demonstrates a mechanism implemented by the Apache Abdera project to convert Atom documents into JSON and produces a result that is readable, usable, and complete.
You’re told that you need to move your content to XML. You have loads and loads of unstructured content. It’s in FrameMaker, Word, other desktop publish applications, or even more fun: it’s on paper.
Although managing costs is important anytime, it is especially important in today's economic reality where budgets are shrinking drastically. Getting your money's worth as well as what you need to support your data should be a core factor of any data project. The two biggest cost factors are the type of conversion work you need done and how much of it you'll need. This article focuses on how your goals for your project relate to the output format you choose, and how that format impacts costs. While some outputs, like XML, provide higher capabilities, they also cost more to create.
I have recently converted some user documents from MS Word to XML for a medical device company with the intent that they would be looking at authoring their future end-user documentation (printed, embedded, and online) in XML. I want to share with you some of the triumphs and challenges we had met along the way.
Outlines pitfalls that are often encountered by authors, programmers and localizers when first using XML, as well as ways to avoid these problems. Following Zydron’s advice can save developers time, money and headaches, and can help them reach out effectively to the world.
Translating XML documents presents many opportunities as well as challenges. There are clear do's and don'ts when it comes to designing your documents regarding translation. You can use also use XML to your advantage to reduce costs and increase quality. One of the most exciting ways to do this is via the use of the XML Text Memory Namespace - xml:tm.
There are several tools that can help you generate an XML Schema document from either an instance or a DTD. This hack shows you how to get the job done with little fuss.
EPUB 3.0, which is the latest revision of the industry-standard XML e-book format, jumps into modern web technology by embracing HTML5 and CSS3. It retains its focus on XML-driven toolkits by requiring XHTML serialization and adding supplementary XML vocabularies, such as MathML and SVG. EPUB 3 offers a variety of options for developing advanced, digital-native publications. In this article, learn to create rich-layout pages using some new features in EPUB 3.
Now we come to the point of actually producing documents using structural markup—either eXtensible Markup Language (XML) or Standard Generalized Markup Language (SGML). Our sequence of topics illustrates the recommended steps to follow when you first implement structural markup: Learn about it and convince yourself and your organization of its benefits, identify your specific goals and expectations, and spend plenty of time selecting or designing your document structures. Only then should you get down to the specifics of how to produce XML or SGML documents. If you simply try to drop in an XML editor to replace your current word processing application, you will be lucky to avoid total disaster.
By organizing information around the goals that users are trying to accomplish, you can provide task-based information that truly addresses user needs. This article walks through the steps for creating more useful information navigation by implementing information development best practices with examples in the Darwin Information Typing Architecture (DITA).
Recently I have received more and more questions about the Rich Site Summary (RSS) format and its use for Web masters. The short answer is that RSS is a great way for any Web site to advertise their content in an always up-to-date fashion.
So you know all about reading and parsing XML files, and even checking if they're well-formed and valid. Now, take a step into more advanced territory with this expose of two objects that let you dynamically create well-formed XML documents in your ASP.NET scripts.
Critique is the first example of a new approach to contextual collaboration: Documentspaces. Documentspaces are places within a document in which teams can meet and work, synchronously or asynchronously, to create, review, and publish content.
The rules for finding schema components when validating a document using W3C's XML Schema 1.0 are widely misunderstood. This presentation will the rules for constructing a schema and describe the reasoning behind the design.