Re: [xml-dev] Where is XML going

[Rob Koberg <rob@koberg.com>]

From all of the suggestions, I find myself asking why would anyone
change from JSON/JS to XML2/something? How would you convince the
browser vendors to accomodate  some new version of XML? Why is any of
this attractive to web devs? (if that is still the focus derived from
the James Clark blog post)

How do you get around cross domain security which includes different
virtual hosts on the same domain and http schemes (http and https)?
And you still need javascript to drive the transformations with
anything other than the processing instruction transform, unless that
would somehow change.

I would bet people outside the XML community would look at what has to
change, weigh the benefits, and say meh.

-Rob

On Sun, Dec 5, 2010 at 10:10 AM, Ben Trafford <ben@prodigal.ca> wrote:
> On Sun, 2010-12-05 at 08:59 -0500, David Lee wrote:
>> I must be working with different 'kinds' of documents then you (ben).
>
> David, there is no doubt that there's a whole class of documents that
> will require transformation. What I'm arguing is that there is an
> equally large class of documents that would be adequately served without
> significant transformation, and moreover, that we would see -more-
> documents that don't require transformation, if existing web
> technologies could properly handle and display pure XML.
>
> So, yes: you are working with different kinds of documents than I am.
>
> --->Ben
>
>
> _______________________________________________________________________
>
> 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
>
>