XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [xml-dev] "Introducing MicroXML, Part 1: Explore the basicprinciples of MicroXML"

Hey Len,

> 
> 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?  :)

I don't know where the example comes from, but it goes to my
point exactly.  The semantics of that markup is too important
to be left out for re-invention by everyone.  It needs to be
nailed down with 10-ton bolts!!!!

> 
> In short, once on the path to including hyperlinking 
> semantics, there is
> no end to it.

That's exactly the problem.  Build it into the language, problem 
disappears! Well ok, there may be other problems.  

XML may live on for 1000 or more years, if we make it.
How many times can that markup be reinvented?  And each time it
gets reinvented is one more reason to not use XML.


   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.

I'm on board with XSL! Why do you say was/?

> 
> 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_los
> es_in_web_
> patents_claim_against_google_and_others.html
> 
> and others are still battling
> 
> http://www.zdnet.com/blog/networking/microsoft-buys-netscape-w
eb-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."

Wow.  Still, can you imagine what the impact of this would be on putting
hypermedia affordances in the XML namespace?

Peter


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS