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

Re: [Fwd: The problems with Xlink for integration languages

• To: xml-dev@l...
• Subject: Re: [Fwd: The problems with Xlink for integration languages]
• From: Paul Prescod <paul@p...>
• Date: Tue, 17 Sep 2002 17:59:34 -0700
• References: <4.2.2.20020917131033.00ac4748@m...> <016401c25e0e$f48316a0$fe193044@tbp1> <E17qPSL-0002It-00@m...> <68872854568.20020917004759@j...> <016401c25e0e$f48316a0$fe193044@tbp1> <4.2.2.20020917131033.00ac4748@m...> <4.2.2.20020917142058.01432e40@m...> <3D8777BC.1010509@n...>
• User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.1) Gecko/20020826

Emmanuil Batsis (Manos) wrote:
> 
>...
> 
> By far the best post of this thread.
> 
> Currently, (X)HTML is mostly used for presentational purposes alone. I 
> would agree that in 90% of cases, XML+XLink+CSS2+ECMAScript should be 
> used to do what (X)HTML does today.

I disagree. The fact that HTML is a known vocabulary allows Google and 
browsers to (for instance) detect titles reliably. Who knows what other 
semantic markup they may use. Similarly, I suspect that  vocalizing 
browsers and text-based browsers depend on the semantics of the markup 
rather than trying to "translate" the style. The more a tool knows about 
teh semantics of the markup the more it can do something that wasn't 
anticipated by the designer of the tool. Sure, your "unordered list" may 
be styled in some cases as graphical bullets but Lynx knows that it is 
really an unordered list so it does the right thing.

The trend is to put more and more semantics in CSS X (X>1) but that's 
just a little bit of a slight of hand. Now CSS X becomes the 
"architectural supertype" and your vocabulary becomes the architectural 
subtype. CSS becomes both the mapping language and the target language 
which is arguably not an appropriate separation of concerns.

  Paul Prescod

• Follow-Ups:
  • Re: [Fwd: The problems with Xlink for integration langu ages]
    • From: "m batsis" <mbatsis@n...>

• References:
  • Re: [Fwd: The problems with Xlink for integration langu ages]
    • From: Ann Navarro <ann@w...>
  • Re: [Fwd: The problems with Xlink for integration langu ages]
    • From: "Thomas B. Passin" <tpassin@c...>
  • Re: [Fwd: The problems with Xlink for integration langu ages]
    • From: Uche Ogbuji <uche.ogbuji@f...>
  • Re: [Fwd: The problems with Xlink for integration langu ages]
    • From: Jeni Tennison <jeni@j...>
  • Re: [Fwd: The problems with Xlink for integration langu ages]
    • From: Ann Navarro <ann@w...>
  • Re: [Fwd: The problems with Xlink for integration languages]
    • From: "Emmanuil Batsis (Manos)" <mbatsis@n...>

• Prev by Date: SGML query: SHUNCHAR
• Next by Date: Re: [Fwd: The problems with Xlink for integration langu ages]
• Previous by thread: Re: [Fwd: The problems with Xlink for integration languages]
• Next by thread: Re: [Fwd: The problems with Xlink for integration langu ages]
• Index(es):
  • Date
  • Thread