HTML is a markup language. XML is not a markup language. XML is a tool that you use to create a markup language. In HTML the markup up tabs are defined for you. The rules for combining those tags are already defined for you.
With XML you create your own markup language by creating the tags and defining the rules that determine how those tags can be combined.
Do you understand the difference between HTML and XML?
The suit is not about a patent on XML. Nobody has a patent on XML. It is about a patent on a markup language created with XML, that is to say the new markup tags a company created and the rules that define how those newly created tags can be combined.
In HTML you don't invent your own tags. You don't define your own rules for combining those tags. It's all defined for you.
With XML you have the ability to create your own tags and rules for combining those tags.
By the way XHTML has been a huge flop. Why? Because XHTML is too restrictive. And nobody uses XML for AJAX any more. JavaScript objects and arrays have replaced XML. JavaScript is now the X in AJAX. Why has JavaScript replaced XML? Because it so much easier to describe a data structure in JavaScript than XML.
Mmmm.. lets see, over the last 10 years I have spent nearly a million dollars on XML/Java application development, so maybe, just maybe I know something about this.
I participated in the eBXML project until it became lost in international bureaucratic vacation taking rather than doing anything of import. And I can assure you that nothing, nothing associated with XML or XML tags is patentable because its like patenting a combination of words on a page, no way to do this to create a novel invention. XML is an international standard that defines the XML code layer and the DTD and DLD layers that manage the definition of the XML and call resources associated with these tags. Its like discovering PHP on the web one day and deciding to develop PHP pages and then deciding to patent using it to write a web page that includes a flash movie... its stupid, thats what PHP was designed to do, what is the unique invention?
XML is simply a carrier, just the same as HTML. The difference being is that I can use it to call resources and pass them data.
XML is server side because Browsers are not written to read it, but XML could be sent to any proprietary rendering engine that is designed to accept XML tags and interpret them. Any Web Browser could serve as such a proprietary engine if the definitions were shared via a plug-in or some such.
In the case of Word, it is acting as a non-browser, non-server rendering engine with a specific set of XML tags of meaning that resolves into Markup Instructions as well as resource calls.
There is no difference between this action and my Java based programs that accept the XML we write and generate HTML that Web Browsers recognize.
Mmmm.. lets see, over the last 10 years I have spent nearly a million dollars on XML/Java application development, so maybe, just maybe I know something about this.
I participated in the eBXML project until it became lost in international bureaucratic vacation taking rather than doing anything of import. And I can assure you that nothing, nothing associated with XML or XML tags is patentable because its like patenting a combination of words on a page, no way to do this to create a novel invention. XML is an international standard that defines the XML code layer and the DTD and DLD layers that manage the definition of the XML and call resources associated with these tags. Its like discovering PHP on the web one day and deciding to develop PHP pages and then deciding to patent using it to write a web page that includes a flash movie... its stupid, thats what PHP was designed to do, what is the unique invention?
XML is simply a carrier, just the same as HTML. The difference being is that I can use it to call resources and pass them data.
XML is server side because Browsers are not written to read it, but XML could be sent to any proprietary rendering engine that is designed to accept XML tags and interpret them. Any Web Browser could serve as such a proprietary engine if the definitions were shared via a plug-in or some such.
In the case of Word, it is acting as a non-browser, non-server rendering engine with a specific set of XML tags of meaning that resolves into Markup Instructions as well as resource calls.
There is no difference between this action and my Java based programs that accept the XML we write and generate HTML that Web Browsers recognize.
“HTML is a markup language. XML is not a markup language. XML is a tool that you use to create a markup language. “
eXtensible Markup Language (XML) is a markup language and a defined standard. XML is NOT a “tool”. No such thing.