[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Mapping XHTML to XLink via Architectural Forms

• From: "Bullard, Claude L (Len)" <clbullar@i...>
• To: Eric van der Vlist <vdv@d...>, xml-dev@l...
• Date: Fri, 27 Oct 2000 10:57:55 -0500

The img element is a good example. I have 
to warn locals when showing them the vocabularies 
that two tags, with similar applications, can 
often have very different attribute sets.  The 
namespace lets us isolate them but not say 
much about the application.

We keep coming back to arch forms.  There 
must be something to them.   

I wonder:  has anyone revisited arch forms 
and where *inheritance* is discussed, delegation 
might be more appropriate?  I confess to not 
knowing enough about it, but isn't inheritance 
considered fragile and delegation robust?

Len 
http://www.mp3.com/LenBullard

Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h


-----Original Message-----
From: Eric van der Vlist [mailto:vdv@d...]

I see this as something that will happen more and more frequently and
not only within vocabularies defined by the W3C ;=) ...

There is a lot of overlap between vocabularies that have been defined
independently and it would often make sense to create new modules to
isolate the common feature and reduce the overlaps.

• Prev by Date: Re: Mapping XHTML to XLink via Architectural Forms
• Next by Date: XML Schemas: even more complex than Java
• Previous by thread: Re: Mapping XHTML to XLink via Architectural Forms
• Next by thread: XML Schemas: even more complex than Java
• Index(es):
  • Date
  • Thread