Enterprise Archive

Managing source code repositories

There are few areas in software engineering that get programmers and managers as actively engaged as the source code management processes. Naturally, it has evolved rapidly over the last decade or so as we went from RCS and Visual Source Safe to Git/Mercurial and SVN. As these tools have come and gone, so also have

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

WebSimpleDB gets thumbs up from major browser vendors

Microsoft and Mozilla declared their intention to advance WebSimpleDB and their preference for it over WebDatabase(which itself is getting renamed to WebSQLDatabase) and WebStorage. WebDatabase will be frozen in terms of its current API and likely stay at the SQL dialect of SQLite 3. WebSimpleDB has taken on the mandate of the WG to create

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

CMIS VII: has more items and paging

In the example for folder children included with the AtomPub bindings for CMIS, I noticed a weird thing just before the end of the document:     …   </ns3:entry>   <ns1:hasMoreItems>false</ns1:hasMoreItems> </ns3:feed> Now Atom’s liberal content model allows various kinds of foreign markup. However, Atom very carefully prevents any foreign markup from occurring at the end of

CMIS VI: A case of unpredictable relations

In CMIS AtomPub extensions, an entry may optionally specify two relations: If this is a folder entry, it only specifies children link if it actually has children If this is a folder or document entry, it only specifies parent link if a parent exists. There is a basic problem with this approach. Suppose that a

CMIS IX: Confused loyalties – CMIS or AtomPub

In a previous post, I complained that I miss good old AtomPub when working with CMIS servers. One of the reasons is duplication of key information items of Atom in a CMIS property set. One of my colleagues reported an issue to the CMIS TC for CMIS properties that duplicate APP/ATOM information. Duplication produces two problems

CMIS vs. AtomPub Hierarchy I-D

Led by Microsoft, IBM, and EMC, OASIS has been working on a modern standard for content management systems, called CMIS. This group has started from a submission made by the above three vendors called CMIS v0.5. This standard also includes a “binding for REST/Atom”. In layman terms a binding is an adaptation of the abstract

Hierarchy in AtomPub

We have submitted the AtomPub hierarchy I-D to IETF for consideration along Standards Track. Although there is no working group looking at extensions to Atom or AtomPub, and there is not so good feeling about the future of AtomPub, there seems to be a very good use for Atom and AtomPub for document-oriented data. Feedbooks