Re: [Xmlastro-discussion] Weather, etc. Was: Multiple Objects

[Peter C. C. <pc...@ec...>]

On Wed, 2 Apr 2003, Don Willems wrote:

> > Maybe the best way to go, for now, would be to use <xs:anyType> in the
> > schema so that the weather type can be provided at instance creation
> > from another schema doc/namespace?
>
> I favor that, not only for Weather, but also for other types (personal
> information, geographical information, markup for notes, etc...). We
> should though be able to provide the most important information.

I'm not familiar with <xs:anyType>. I do have a reference that talks about
the <xs:any> element, however. It gives an example like this:

<xs:element name="XHTMLSection>
  <xs:complexType>
    <xs:sequence>
      <xs:any namespace="http://www.w3.org/1999/xhtml"
              minOccurs="0" maxOccurs="unbounded"
              processContents="skip"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>

This apparently allows an <XHTMLSection> element to contain any elements
from XHTML. The processContents attribute controls how the contents of
that element are validated. The value of "skip" means no validation, but
other options are possible (namely "strict" and "lax").

Is this the sort of thing we're talking about?

Note that apparently the namespace attribute can be left off so that the
content of the element can be from any namespace. The reference I have
even says that this is a nice thing to do during development for exactly
the reasons we have been discussing. Using this approach does sound good
and it may be a good way to handle <notes> permanently.

Peter