[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Where is XML going

  • From: "Pete Cordell" <petexmldev@codalogic.com>
  • To: "Rob Koberg" <rob@koberg.com>,"Ben Trafford" <ben@p...>
  • Date: Sun, 5 Dec 2010 21:13:42 -0000

Re:  Where is XML going
Original Message From: "Rob Koberg"
> 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)

For me it's not just about whether you feed JSON or XML to the browser.  I 
see the benefits of a universal way to represent data, and while I'm a 
data-head, I've accepted XML as the best approach to that.  The development 
of JSON shows that there are others that are not prepared to put up with the 
complexity of XML for their needs.  Hence the data representation world is 
splitting between those that want mixed data with mark-up and are going for 
XML, and those that don't who are going for JSON.

I would like to tweak and simplify XML so that people trying to decide 
between JSON and XML(lite) could see that there's no downside to going with 
the XML route.

I don't want to invent something completely new, because that just means 
there's 3 players in town instead of two.  If we do something completely new 
I'm sure it will just wither on the vine.  I'm hoping for more of a point 
version fix in tools to accommodate the revised format rather than a 
completely new set of tools (e.g. tool version goes from 5.2 to 5.3 with the 
update).

Removing the internal DTD and CDATA sections, along with restricting to 
UTF-8 and UTF-16 encodings is probably 80% of what's required.  Doing 
something with namespaces would also be appealing.

Thanks,

Pete Cordell
Codalogic Ltd
Interface XML to C++ the easy way using C++ XML
data binding to convert XSD schemas to C++ classes.
Visit http://codalogic.com/lmx/ or http://www.xml2cpp.com
for more info
----- Original Message ----- 
From: "Rob Koberg" <rob@koberg.com>
To: "Ben Trafford" <ben@prodigal.ca>
Cc: "David Lee" <dlee@calldei.com>; "Peter Hunsberger" 
<peter.hunsberger@gmail.com>; "Michael Kay" <mike@s...>; 
<xml-dev@lists.xml.org>
Sent: Sunday, December 05, 2010 7:47 PM
Subject: Re:  Where is XML going


>
> 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
>>
>>
>
> _______________________________________________________________________
>
> 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]


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.