[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: <xml-dev@lists.xml.org>
• Date: Mon, 25 Jun 2012 10:32:04 -0500

Even better:

<extref docno="CTA 50-970" linktype="message" href="CTA 50-970 is not
included in this document set." color="green" popup="1" />

Note the linktype and the content of the href which of course, isn't an
html href but hey, who cares?  :)

In short, once on the path to including hyperlinking semantics, there is
no end to it.   You assert that the web is "the application".  That
simply isn't true.  The web is a lot of different applications knitted
together.  XSL was/ideal because it enables many languages to co-exist
and leaves it to the locals to work out the details.  It is the Data is
Data mantra at work which asserts the Local Rules Prevail notion.

Games on the web and real time 3D are most certainly web applications
but they do a lot of local work to get around the performance penalties
of a text-oriented browser based orientation.   They had to wait over a
decade to use the HTML web browser to do the tricks the non-HTML systems
could do in 1996 On The Web.   The overhead is borne by APIs.

And while there are no patents on XML (we sidestepped that), there are
patents on web browser technologies.  The EOLAS patent was years in
court and finally voided only recently:

http://www.pcworld.com/businesscenter/article/249695/eolas_loses_in_web_
patents_claim_against_google_and_others.html

and others are still battling

http://www.zdnet.com/blog/networking/microsoft-buys-netscape-web-patents
-from-aol-to-attack-google/2203

"Netscape's intellectual property (IP), however also included such
universal Web browser mainstays as Secure Socket Layers (SSL), cookies,
and JavaScript. It's these old Netscape patents that Microsoft is paying
a billion bucks for. And, you know what? For a mere billion Microsoft
got a steal of a deal."

len

• 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>
  • Re: "Introducing MicroXML, Part 1: Explore the basic principlesof MicroXML"
    • From: Michael Kay <mike@saxonica.com>
  • RE: "Introducing MicroXML, Part 1: Explore the basic principles of MicroXML"
    • From: "Len Bullard" <Len.Bullard@ses-i.com>