• From: "Simon St.Laurent" <simonstl@s...>
• To: "Thomas B. Passin" <tpassin@h...>, xml-dev@l...
• Date: Fri, 30 Mar 2001 08:11:57 -0500

At 07:34 AM 3/30/01 -0500, Thomas B. Passin wrote:
>Maybe you could view an element as being instances of two types at the same
>time: the type defined by the attribute set and the type defined by the
>non-attribute content.  What a wierd thought!

Once you start 'painting' types rather than assuming that types are part of 
the information, you can have multiple types for any given piece of 
information, as well as multiple type structures for the same document.

The 'cascade' in Cascading Style Sheets is one way to deal with such 
issues, but there are plenty of others.

Kind of a different way to look at information, but potentially very useful!


Simon St.Laurent - Associate Editor, O'Reilly and Associates
XML Elements of Style / XML: A Primer, 2nd Ed.
XHTML: Migrating Toward XML
http://www.simonstl.com - XML essays and books

• Follow-Ups:
  • RE: multiple types (Re: attribute order)
    • From: Gavin Thomas Nicol <gtn@e...>

• References:
  • RE: attribute order (RE: Syntax Sugar and XML information models)
    • From: Gavin Thomas Nicol <gtn@e...>
  • Re: attribute order (RE: Syntax Sugar and XML information models)
    • From: "Thomas B. Passin" <tpassin@h...>

• Prev by Date: RE: attribute order (RE: Syntax Sugar and XML information models)
• Next by Date: RE: attribute order (RE: Syntax Sugar and XML information models)
• Previous by thread: Re: attribute order (RE: Syntax Sugar and XML information models)
• Next by thread: RE: multiple types (Re: attribute order)
• Index(es):
  • Date
  • Thread