I (and I suspect most other readers) DO actually appreciate you taking the time to discuss these formats online. Still, I can understand (and agree with) the reasons which are driving people to be somewhat abrasive in some of the posts. Microsoft has definitively proven that it will do whatever it can to lock its customers in and avoid competing on technical (and now price) merits.

This is a work in progress. If you are reading a local copy, the master copy might be newer. This document uses are relative links; if they don't work, please use the master copy. Please feel free to ask questions and/or provide answers; send email to the Docutils-users mailing list. Project members should feel free to edit the source text file directly.

Yes. The Document Assistant is a mobile and desktop XML editor but it hides all of XMLs complexity from the end user. The Document Assistant can edit any well formed XML document based on an imported DTD. The software is more sophisticated compared to the limited DTD standard and so it provides additional XML features for the developer and end user.

Data and document XML are two different ways of representing the same XML information. The Document Assistant software produces both Data and Document XML. Data XML stores all the information in a structured way which is machine readable so it can query, analyze or produce graphical information easily. In contrast, Document XML is used to represent information in a format that can be published and printed. English language is produced within the Document XML.

Here's some sample code for that: sub SaveXML dim mProps(0) as new com.sun.star.beans.PropertyValue mProps(0).Name = "FilterName" 'This works with 614 mProps(0).Value = "swriter: StarOffice XML (Writer)" oDesk = createUNOService("com.sun.star.frame.Desktop") 'For some reason, ActiveComponent no longer works: oComponent = oDesk.CurrentComponent() oComponent.storeAsUrl("file:///C|/Tmp/startemp.xml",_ mProps()) end sub

Mount it via /etc/vservers/vserver-name/fstab, make sure to set the option 'dev' e.g.: /dev/drbd0 / xfs rw,dev 0 0

p0 is the entire disk, including the boot sectors and all the partitions. The p1-p4 are the four possible fdisk partitions. Internally these are the 16th-20th positions in the slice table for the disk.This allows you to do a newfs on p0 and use the entire disk as a file system. The p0:M method is handled within the pcfs code, where 'M' is 'c' for a primary FAT partition and 'd'-'z' for logical FAT partitions within an extended partition.

XML is a meta-language optimized for use on the Internet. A meta-language provides a way to create other languages or vocabularies. Many applications use XML as a way of sharing data between otherwise incompatible systems.

The linking abilities of XML systems are much more powerful than those of HTML, so you'll be able to do much more with them. Existing HREF-style links will remain usable, but new linking technology is based on the lessons learned in the development of other standards involving hypertext, such as TEI and HyTime, which let you manage bidirectional and multi-way links, as well as links to a span of text (within your own or other documents) rather than to a single point.

Keep attribute and element names as short as possible (every character in attribute/element names get validated to see if it's legal). Reduce character count; smaller documents are parsed quicker. Avoid gratuitous use of whitespace because the parser must scan past it. Use attributes to reduce size. Processing an attribute-centric document is usually faster than parsing an element-centric one. Replace elements with attributes where it makes sense. Use elements to group.

It is not recommended. I made it work once, the major reason was trying to take advantage of DTD entities. It would be easily causing confusion. It would be hard to maintain stuff in the feature.

Use the XMLHTTPRequest object. See here for the documentation. Also look at this thread for some examples. Mayhem notes that this only works for XHTML compliant HTML, but he also offers a neat workaround for non-compliant pages.

Yes. Atomik Roundtrip maintains a link between the content in your QuarkXPress document and the source XML document. This means that if you make any copyedits or corrections to the content in QuarkXPress, with just one click you can update the source XML document(s) to reflect these changes.

A common way of specifying the structure of skmMenu is to bind an XML document to the menu control. To learn the precise structure of this XML document, refer to Examining the XML Structure.

How can I get my Xerces SAX-1 Parser to recognize namespaces or my W3C XML Schema? It seems like it only understands DTDs.

There are several methods to programmatically specify schema locations to be used in validation. For example, you can use the xml_schema::properties argument to parsing functions to specify schema locations instead of those specified with the xsi::schemaLocation and xsi::noNamespaceSchemaLocation attributes in XML documents. For more information refer to Section 5.1, "XML Schema Validation and Searching" in the C++/Tree Mapping Getting Started Guide.

To declare an XML namespace, you use an attribute whose name has the form: xmlns:<i>prefix</i> --OR-- xmlns These attributes are often called xmlns attributes and their value is the name of the XML namespace being declared; this is a URI reference. The first form of the attribute (xmlns:prefix) declares a prefix to be associated with the XML namespace. The second form (xmlns) declares that the specified namespace is the default XML namespace.

When people ask this question, they usually assume that validity is different for documents that use XML namespaces and documents that don't. In fact, it isn't -- it's the same for both. Thus, there is no difference between validating a document that uses XML namespaces and validating one that doesn't. In either case, you simply use a validating parser or other software that performs validation.