Altova Mailing List Archives

Re: [xml-dev] standalone and XML Schema

From: ht@---.--.--.-- (----- -. --------)
To: "Jesper Tverskov" <jesper@--------.-->
Date: 1/31/2006 5:30:00 PM
Hash: SHA1

Jesper Tverskov writes:

> As I read the XML spec, the Standalone Document Declaration is only
> relevant, or could be relevant, when a DTD is used.
> I am just wandering since XML Schema can also have e.g. default values for
> attributes.

> Is it correct that the Standalone Document Declaration is only relevant when
> a DTD is used, and that the standalone pseudo-attribute is irrelevant when
> the XML instance documents point to an XML Schema?

I think your analysis is correct -- XML 1.1 make no reference to W3C
XML Schema, and W3C XML Schema makes no reference to the 'standalone'
pseudo-attribute. . .

- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@i...
[mail really from me _always_ has this .sig -- mail without it is forged spam]
Version: GnuPG v1.2.6 (GNU/Linux)



These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.