Phones Archive

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

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