Newtonsoft’s JSON.NET has received a pair of architectural updates to make it easier to use in projects that involve third party libraries. The two features are known as DefaultSettings and Extension Data.
JSR-353, the Java API for JSON Processing (JSON-P), has reached final approval ballot this month. JSON-P (similar to JAXP) consists of a Streaming API (similar to StAX) and an Object Model API (similar to DOM). Please note that this API does not include JSON data binding (similar to JAXB), and is unrelated to the more popular JSONP or "JSON with padding".
Create any “flexible” or “extensible” file format and sooner or later a group of developers will start complaining about validation. For JSON, several options are starting to spring up.
If you are building new web services with .NET then OData should be high on your list of frameworks to investigate, especially if you need to support unknown third parties. The technology inherently supports both SOAP and REST style messages with the latter offering ATOM (XML) and JSON representations. This means consumers can pretty much request whatever format is best for them.
Microsoft has announced the availability of WCF Data Services 5.2.0 with support for UriParser and fixes to several bugs.
As JSR 342, the specification for Java EE 7, makes its way through early draft review the expert group is keen to get community feedback on a number of open issues. These include which of the new APIs should be added to the Java EE Full/Web Profile, as well as how to better align CDI with Java EE.
JSONiq is a new query language that builds upon XQuery. Like SQL or LINQ, it has syntactic support concepts such as let, for, where, group by, and select.
On behalf of the IETF, Mark Nottingham has recently published a draft of the Home Documents for HTTP APIs specification. Intended for non-browser clients, it provides a way to describe resources available from a particular site as well as possible hints on how to interact with those services.
Developers are overwhelmed by Web APIs. APIs are being published at an alarming rate exposing a myriad ways to access data which in turn is incompatible with similar objects across other Web APIs. The Object Network is an attempt at universalizing data formats for objects to create a data fabric that leverages the network effects of hyperlinking similar to the Internet.
Collaboration in the enterprise software space has been plagued with process and technology challenges. The advent of lightweight open API specifications from industry associations such as NetworkedHelpDesk alleviate some of these technical challenges and are being touted as examples of what future enterprise APIs will resemble.
Jon Galloway is researching dynamic ASP.NET MVC 3 models using Mono’s Compiler as a Service. Meanwhile Karsten Januszewski is looking into deserialized JSON in lieu of statically typed models.
The growth of Open APIs both in numbers and volume has surpassed any expectations over the last decade. John Musser from the ProgrammableWeb presented his analysis of the Open APIs State of the Market for 2011.
Frank Ableson published an article last week providing a thorough introduction about using jQuery Mobile, JSON, PHP and MySQL to create mobile web applications.
Most developers first use WCF as a way to expose SOAP-based Web Services. But despite the name, Web Services are not really well suited for building web sites. XML and JSON-based REST services are simply a better fit for most projects. Microsoft has recognized this and is working on a project to bring WCF up to date with modern standards.