• To: "'Razvan MIHAIU'" <mihaiu@m...>,"'Matthew Terenzio'" <matt@j...>
• Subject: RE: XLINK support in browsers
• From: "Michael Kay" <mike@s...>
• Date: Sat, 2 Apr 2005 10:08:19 +0100
• Cc: <xml-dev@l...>
• In-reply-to: <424D9268.3050607@m...>
• Thread-index: AcU3TT8QQ+gdxBjZQre/6/A/NJucfAAFVtmQ

> 
>     What's wrong with XLINK ? At first sight it seems to be 
> quite powerful.
> 

It's at the wrong place in the architecture. XML caught on because people
liked the idea of separating information content from presentation, and
XLink never recognized that. XML says you can use any names you like for
your objects and their properties, but XLink says you have to call your
relationships xlink:href.

In practice people are storing information in XML form, and using XSLT to
transform it into presentation formats like HTML and PDF (via XSL-FO). If
you do that, you can model your relationships any way you like, and give
them names that make sense. XLink just doesn't add value in that scenario.

Michael Kay
http://www.saxonica.com/ 

• References:
  • Re: XLINK support in browsers
    • From: Razvan MIHAIU <mihaiu@m...>

• Prev by Date: Cascading Style Sheets (CSS) and Attributes within an XML Document
• Next by Date: Re: all group composition
• Previous by thread: Re: XLINK support in browsers
• Next by thread: Re: XLINK support in browsers
• Index(es):
  • Date
  • Thread