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

RE: "Introducing MicroXML, Part 1: Explore the basic principle

• From: "Len Bullard" <Len.Bullard@ses-i.com>
• To: "David Lee" <dlee@calldei.com>,"Rushforth, Peter" <Peter.Rushforth@N...>
• Date: Mon, 25 Jun 2012 09:08:18 -0500

The disagreement originally was is hyperlinking owned by the content or
by the style sheet (say the application).  This is the original Hytime
vs DSSSL schism.  At that time, there was no "web" to talk about.

IOW:  what IS a hyperlink?  A relationship?  A function? An object?
What?

Be careful of the "giants" and "REST is THE" discussion.   There is a
bit of retrofitted history in that description.  The Internet and the
web applications as well as others were functional before the term
"representational state transfer" was ever coined and that notion was
already a part of discussions.  There is less invention there than you
believe which is why the W3C has been unable to overturn certain
critical patents.  It isn't authoritative nor an invention.  It is a
thesis with ideas that work because there was sufficient experience to
document them formally.  

However the technical point is as David and others have said.  As soon
as you add application semantics, XML becomes less useful, not more.
For example, try putting hard wired linking semantics into non-text
browser applications such as 3D gaming.

len

-----Original Message-----
From: David Lee [mailto:dlee@calldei.com] 
Sent: Monday, June 25, 2012 8:44 AM
To: Rushforth, Peter; Andrew Welch
Cc: Uche Ogbuji; xml-dev@lists.xml.org
Subject: RE:  "Introducing MicroXML, Part 1: Explore the basic
principles of MicroXML"

Peter Sez
> But, my point remains, Web browsers are the most common XML processing
> application on earth, and they can't recognize the hypermedia
affordances we
> put in our representations.  Why not?
>

Here is where I think you will find the crux of the disagreement.
First off I will assert your statement is factually incorrect (about
being the most common XML processing app). 

But more importantly,  philosophically ...

There is the camp that believes XML should be agnostic about the
application layer
And there is the camp that believes XML should be tailored to make its
use in a web browser more usable.

Finding common ground between these is tough ... and IMHO is why we
ended up with HTML5 instead of XHTML2.



----------------------------------------
David A. Lee
dlee@calldei.com
http://www.xmlsh.org



_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

• Follow-Ups:
  • RE: "Introducing MicroXML, Part 1: Explore the basicprinciples of MicroXML"
    • From: "Rushforth, Peter" <Peter.Rushforth@NRCan-RNCan.gc.ca>

• References:
  • RE: "Introducing MicroXML, Part 1: Explore the basicprinciples of MicroXML"
    • From: "Rushforth, Peter" <Peter.Rushforth@NRCan-RNCan.gc.ca>
  • Re: "Introducing MicroXML, Part 1: Explore the basicprinciples of MicroXML"
    • From: Andrew Welch <andrew.j.welch@gmail.com>
  • RE: "Introducing MicroXML, Part 1: Explore the basicprinciples of MicroXML"
    • From: "Rushforth, Peter" <Peter.Rushforth@NRCan-RNCan.gc.ca>
  • Re: "Introducing MicroXML, Part 1: Explore the basicprinciples of MicroXML"
    • From: Andrew Welch <andrew.j.welch@gmail.com>
  • RE: "Introducing MicroXML, Part 1: Explore the basicprinciples of MicroXML"
    • From: "Rushforth, Peter" <Peter.Rushforth@NRCan-RNCan.gc.ca>
  • RE: "Introducing MicroXML, Part 1: Explore the basicprinciples of MicroXML"
    • From: David Lee <dlee@calldei.com>