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] Where is XML going

I respectfully disagree.
The server may well be "closed" and the browser may be "open" .. or visa-versa ...
I don’t think "open" vs. "closed" is the issue.

In my opinion the server is 'closer to the data' then the browser.  It has more chance of knowing about the meaning of the data then the browser.
And also has access to possibly higher compute power as well as 'back end' data to aid in translation to presentation format.

If We take the server as the knowledge repository and the browser as  the presentation layer ( I know this isn't the only model but I argue it’s a good one),  then the Server->Browser transition it would be the servers' responsibility to translate data representation into presentation data.
I argue that is the correct place to do the transformation.   

Now if were talking about B2B (server<->server) then passing the raw XML between parties may make sense, or perhaps a transformed XML which is transformed to the domain intended to the other party.

I am still not convinced yet why the browser is the 'right place' to do Data to Presentation transformations.
Maybe it is, and I would love an argument for it.
I think this is a fundamental architectural question.  What is the responsibility of the browser on the web and what is the responsibility of the serer ?
I would suggest that the concept of "server serving static data documents" is no longer valid ... 
The dividing line is indeed gray ...but is there a universal consensus of separation of concerns ?

David A. Lee

-----Original Message-----
From: Michael Kay [mailto:mike@saxonica.com] 
Sent: Saturday, December 04, 2010 6:42 PM
To: xml-dev@lists.xml.org
Subject: Re: [xml-dev] Where is XML going

On 04/12/2010 21:38, David Lee wrote:
> I'll stil bite and raise you a devils-avococate.
> Explain to me why its "better" that XML be translated in the browser to presentation then on the server.
Because that's a more efficient use of resources, and enables a more 
interactive and responsive presentation.
> Compare/contrast that to the cost of requiring ALL browsers in the entire world to adopt your technology vs only requiring the server hosting the particular content to adopt it.
The ONLY reason for doing it on the server is that the server is an open 
platform while the browser is a closed platform. So fix that problem.

Michael Kay


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

[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