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

RE: xml:href, xml:rel and xml:type

• From: "Len Bullard" <Len.Bullard@ses-i.com>
• To: <liam@w3.org>
• Date: Thu, 19 Apr 2012 14:57:25 -0500

Eliot is a faithful and durable cat.  He hoed to the end of that row.  I
bailed when I realized that past the basic ilink/clink concepts, I
didn't have the foggiest notion what the rest of the spec was for. I was
just too dumb.

It's a features-in-contexts challenge.   For the web where many media
types have to be negotiable (blind exchange) and loosely coupled (a link
locator and click detection inside a raster image vs a real time 3D
graphic are the same feature implemented within the constraints of
different media types) proper layering is sine qua non.  Hytime thinking
didn't really factor in the potentials of the environment being capable
of emailing state (async) and that the metadata authority is the
container not the content.  It was originally more concerned with the
linking applications of the media types themselves.

I come back to the IETM and note that attempts to go to databases
driving data packages to presentation systems have fared badly and we
might want to consider an XML native presentation engine where the
application language (what the DTD/schema declares) is handled by style
sheets with built in hypertext controls and a handful of XML-defined
names (say xml:href).

len

-----Original Message-----
From: Liam R E Quin [mailto:liam@w3.org] 
Sent: Thursday, April 19, 2012 1:50 PM
To: Len Bullard
Cc: Rushforth, Peter; xml-dev@lists.xml.org
Subject: RE:  xml:href, xml:rel and xml:type

On Thu, 2012-04-19 at 08:10 -0500, Len Bullard wrote:
> Let's be fair.  Hytime became Elliot's by award and rightfully given
the
> work he put into it, but it was being worked some years before Eliot.

Yes. Eliot was, in a way, to HyTime as Yuri was to SGML.

Layered and loosely-coupled systems win out every time over complex
monolithic ones. Of course, one must not confuse complex systems with
large specifications - the spec might be larger because it is clearer
and more precise, and not only because of new features.

Best,

Liam


-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/

• References:
  • RE: xml:href, xml:rel and xml:type
    • From: "Rushforth, Peter" <Peter.Rushforth@NRCan-RNCan.gc.ca>
  • RE: xml:href, xml:rel and xml:type
    • From: "Len Bullard" <cbullard@hiwaay.net>
  • RE: xml:href, xml:rel and xml:type
    • From: "Rushforth, Peter" <Peter.Rushforth@NRCan-RNCan.gc.ca>
  • RE: xml:href, xml:rel and xml:type
    • From: Liam R E Quin <liam@w3.org>
  • RE: xml:href, xml:rel and xml:type
    • From: "Len Bullard" <Len.Bullard@ses-i.com>
  • RE: xml:href, xml:rel and xml:type
    • From: Liam R E Quin <liam@w3.org>