RE: [xml-dev] XML2.0: Truncated End Tags (Was: Fixing what's broke)

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

From: "David Lee" <dlee@calldei.com>
To: "'Len Bullard'" <cbullard@hiwaay.net>, "'Pete Cordell'" <petexmldev@codalogic.com>, "'rjelliffe'" <rjelliffe@allette.com.au>, "'Xml-Dev''" <xml-dev@lists.xml.org>
Date: Mon, 6 Dec 2010 20:25:00 -0500

Sorry don't buy that at all.

The biggest users of JSON are Web Developers who type and read <HTML> all
day long and in their sleep.  Angle Brackets are no new concept to them.

I don't think comparing JSON to Programming languages is appropriate.
It compares to *data* description not *programming* languages.

But I will give you this,  I don't like "programming" in XML  syntax.
As powerful as it is,  I have a hard time with XSLT,  and prefer XQuery
hands-down.

Maybe it is the "<" after all !

s/</{//g
s/>/}//g





----------------------------------------
David A. Lee
dlee@calldei.com
http://www.xmlsh.org

-----Original Message-----
From: Len Bullard [mailto:cbullard@hiwaay.net] 
Sent: Monday, December 06, 2010 8:12 PM
To: 'David Lee'; 'Pete Cordell'; 'rjelliffe'; 'Xml-Dev''
Subject: RE: [xml-dev] XML2.0: Truncated End Tags (Was: Fixing what's broke)


It's easier typing for people accustomed to curly bracketed languages.  

Consider it a composition cost.  When writers or programmers write, they
want to think in the concepts they are conceiving, not in the syntax, so the
fewer typing strokes they memorize to create a value pair or any other
expression regularly used is a net savings in human energy.

Some resistance comes from the costs of multiple hand-to-eye habits.  Unless
used a lot by the same person, these penalize the process with a
start-up/relearning time (maybe not long but rusty has a meaning), and
introduce more errors.

len

-----Original Message-----
From: David Lee [mailto:dlee@calldei.com] 
Sent: Monday, December 06, 2010 10:04 AM
To: 'Pete Cordell'; 'rjelliffe'; 'Xml-Dev''
Subject: RE: [xml-dev] XML2.0: Truncated End Tags (Was: Fixing what's broke)

If you really value conciseness above all else there is always attributes

JSON:
{ "element" : { "a1" : "value1" , "a2" : "value2" }  }

XML
<element a1="value1" a2="value2"/>


This whole "JSON is more compact" theory is a red herring.



_______________________________________________________________________

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

References:
- RE: [xml-dev] XML2.0: Truncated End Tags (Was: Fixing what's broke)
  - From: "David Lee" <dlee@calldei.com>
- RE: [xml-dev] XML2.0: Truncated End Tags (Was: Fixing what's broke)
  - From: "Len Bullard" <cbullard@hiwaay.net>

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