RE: Recommending publishing data as JSON [in: Publishing Open Government Data]

Hi

>	From: public-egov-ig-request@w3.org [mailto:public-egov-ig-request@w3.org] On Behalf Of Eyal Sela
>	Sent: Thursday, 25 November 2010 11:46 PM
>	To: public-egov-ig@w3.org
>	Subject: Recommending publishing data as JSON [in: Publishing Open Government Data]
>
>	Hello all,
>	I was wondering why you do not mention JSON as a possible format for publishing data.
>	Is it because it might impede progress to publishing RDF? 
>
>	In my opinion, not mentioning it might cause you to lose audience. Namely, people who are less familiar with XML, and might think that 'this document/approach is not for them'.

This occurred to me yesterday, maybe because there's been an interesting thread quite recently about JSON in APIs with some big XML personalities [1], [2]. I'm personally an XML zealot, but I can see JSON has a place in straightforward situations where there's no danger of requirements changing (pretty much what Norm says). I don't like dropping XML, though, and I suspect GLD wouldn't get by without its expressive power.

>	If indeed you dilatorily do not mention JSON, I'd suggest writing a paragraph that explains XML's advantages over it, and maybe stating that throughout the document you will relate to XML, but JSON (And other formats) are also possible to use.

Agree.

Cheers

Hugh Barnes
Technical Interface Specialist
nehta – National E-Health Transition Authority
Address:      Level 2, 10 Browning St, West End, QLD, 4101
Phone:        +61 7 3023 8537
Mobile:       +61 417 469 552
Email:        hugh.barnes@nehta.gov.au
Web:          http://www.nehta.gov.au

	 
[1] http://norman.walsh.name//2010/11/17/deprecatingXML
[2] http://blog.jclark.com/2010/11/xml-vs-web_24.html

Received on Thursday, 25 November 2010 23:21:30 UTC