W3C home > Mailing lists > Public > xmlschema-dev@w3.org > January 2002

Re: XML document embedded in the appinfo element?

From: Jeni Tennison <jeni@jenitennison.com>
Date: Mon, 14 Jan 2002 15:07:11 +0000
Message-ID: <111628177391.20020114150711@jenitennison.com>
To: "David E. Cleary" <davec@progress.com>
CC: "Sven Wixner" <wixner@web.de>, xmlschema-dev@w3.org
Hi David,

>> If you wanted to check that the documentation in your schemas matched
>> the documentation schema that you'd created, it looks like you'd have
>> to make a copy of the schema for schemas and change the declarations
>> for xs:documentation and xs:annotation.
>>
>> [Henry, or whoever's responsible for the schema-for-schemas - I think
>>  it would be a good idea to change the schema-for-schemas so that the
>>  complex types for the xs:documentation and xs:annotation elements
>>  were defined at the top level, so that they could be redefined in
>>  these situations?]
>
> Why would this be required? The validation mode for appInfo is lax,
> so it will validate anything there as long as a schema is available.

It's not *required*, just would be useful. Say that you're a company
adopting XML Schema, and you want the people who create XML Schemas in
your company to use a specific documentation structure within them.
How do you help the authors check that their schema documentation
follows the company documentation standard? Using an XML Schema of
course!

But using the schema-for-schemas will lead to false positive results,
due to the lax validation - schemas in which the documentation doesn't
follow the company standard will still be valid according to the
schema-for-schemas (once it hits an element that it recognises, it's
OK, but it won't complain if it doesn't, and in this context you want
it to). You need a schema-for-this-company's-schemas - you can copy
and amend the general schema-for-schema, but that's not a nicely
modular solution, and XML Schema has a better solution, using
"redefine", it's just that the schema-for-schemas hasn't been designed
to make redefine usable in this situation.

It's not that the schema-for-schemas is wrong (this isn't an erratum),
it's just a suggestion to make the schema-for-schemas more usable if
you want to create a version that validates the content of
xs:documentation and xs:appinfo elements against some markup language
that you define. Plus it would illustrate one of the good points about
XML Schema - its ability to support extensible markup languages.

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/
Received on Monday, 14 January 2002 10:07:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:26 GMT