Computing Archive

Audio Output: Mp3 vs Mp4 vs Analog

This is going to be a bit of a different topic, as we will cover audio output of the most common listening mediums today. First we have the revolutionary mp3, the grand daddy of the mp4, and lastly the primordial analog. The latter is the one you would find by using a record player and

Discovering AtomPub Collections – best current practices

When working with data synchronization using Atom feeds in AtomDB, we frequently encounter situations where we learn about a feed simply through its public URL. However, most feed documents do not provide any indication of whether new items can be added to them. (This is not because of a lack of existing standards but because

New WD for programmable HTTP caching and processing

The programmable HTTP caching and processing standard that is advancing through W3C, called DataCache, has recently been updated. A new working draft is available. You can read the frequently updated, latest and greatest version or get to a stable WD of DataCache. This version has several improvements over the previous working draft: The spec extends

New WD for browser database standard

At the start of a new year, I wish the best to you in 2010. The browser database standard that is advancing through W3C, called Indexed Database API, has recently been updated. A new working draft will soon be available. You can read the frequently updated, latest and greatest version or get to a stable

Use Cases for DataCache

I discussed a set of use cases not well supported by HTML5 ApplicationCache with the HTML WG during a breakout session at TPAC. These use cases were the basis for AtomDB are being solved by the DataCache API. Found out that OMA and AT&T had similar ideas too. Also learnt that these techniques could be

DataCache API now rewritten and ready for FPWD

There was a wave of support for programmable HTTP caching when the first DataCache editor’s draft was published. The main issue with the draft was the inability to derive the exact list of additional requirements on browsers compared with HTML5’s AppCache. I went ahead and rewrote DataCache to make it easier to spot the differences.

CMIS X: Is CMIS a good AtomPub citizen?

CMIS has consumed a lot of my blog space for a good reason. Hierarchy is quite important to CMIS and we (Colm Divilly and I) have spent a great deal of time on it. Despite having pointed out several issues in this blog,¬†I can’t beat the feeling that CMIS is determined to go its own

CMIS I: AtomPub binding and AtomPub service documents

This is the beginning of a new series of posts on the still-nascent AtomPub binding of CMIS. Although, this spec has been seen by over 20 companies (led by IBM, Microsoft, and EMC that are participating in its TC) over six months now, I doubt anyone involved in writing this spec has ever written an

CMIS II: (C)MISsing good old AtomPub

In my earlier post on AtomPub vs. CMIS, I expressed concern that new constraints on Atom syntax introduced by CMIS go so far as to rule out using a standard AtomPub client with a CMIS AtomPub server. In theory, one could say that adding a new required element to Atom’s schema is a non-starter. However,

CMIS VIII: Futile to model Atom using XSD

The CMIS AtomPub bindings include a W3C schema for XML, aka XSD for Atom, in a file called atom.xsd. I wanted to warn potential users of that schema about the perils of validating against that schema. First of all, Atom’s syntax has been specified using RNG. There are programmatic Atom validators¬†to ascertain whether an Atom