chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Naresh Bhatia <bhat...@comcast.net>
Subject Re: Understanding the CMIS spec
Date Wed, 08 Jun 2011 15:51:24 GMT
Thanks Florent, good explanation of the why behind some of my observations!

Naresh


On Wed, Jun 8, 2011 at 10:54 AM, Florent Guillaume <fg@nuxeo.com> wrote:

> CMIS defines three different but often related concepts:
> - cmis:name
> - cmis:contentStreamFileName
> - relative path segment
>
> cmis:name is usually seen as "the title", and
> cmis:contentStreamFileName as "the file name". Some repository will
> keep those in sync when they are modified, for the benefits of dumber
> non-CMIS access modes that basically expect a filesystem-like
> interface (WebDAV, CIFS, WSS, etc.). The relative path segment is also
> often tied to the file name as other dumb access modes expect the
> relative path segment to be the same as the file name.
>
> So it all depends on the repository implementation, which usually has
> to make compromises to work with 1. non-spec-compliant CMIS clients
> and 2. other non-CMIS clients.
>
> Florent
>
> PS: I know WebDAV has separate title and displayname but a number of
> dumb WebDAV clients confuse the two and expect them to be the same as
> well
>
>
> On Wed, Jun 1, 2011 at 1:53 AM, Naresh Bhatia <bhatian@comcast.net> wrote:
> > One follow up question - I have a requirement to show the following
> > attributes for a document on my front-end:
> >
> >   - Title
> >   - Description
> >   - Full author name (e.g John Smith)
> >
> > What's the best way to do this with CMIS/OpenCMIS? Here's what I have
> tried:
> >
> >   - Title: I am thinking of using cmis:name for this, although there
> seems
> >   to a minor glitch. When I upload a document to my CMIS repository (an
> >   Alfresco instance) it sets cmis:name and cmis:contentStreamFileName to
> the
> >   filename, e.g. yearly-report.pdf. However when I change the document's
> name
> >   from Alfresco's front-end, it not only changes the cmis:name but also
> >   the cmis:contentStreamFileName. I was not expecting the latter to
> change and
> >   don't know if it has any bad side-effects.
> >   - Description: Don't know how to handle this!
> >   - Full author name: Don't know how to handle this!
> >
> > Any suggestions?
> >
> > Thanks.
> > Naresh
> >
> >
> > On Tue, May 31, 2011 at 4:08 PM, Ryan McVeigh <
> rmcveigh@ziaconsulting.com>wrote:
> >
> >> Those attributes at the top are atom elements, not CMIS ones.  The spec
> >> identifies what they should be though - for example title should be
> >> cmis:name.  The properties are all accessible but perhaps not exposed
> from
> >> the OpenCMIS API when using the AtomPub binding of the server.  This is
> >> likely because the same properties aren't available in the web services
> >> binding (e.g. summary), and OpenCMIS should be binding agnostic.  To
> write
> >> a
> >> reasonably portal and binding-agnostic application, I'd suggest only
> >> relying
> >> on CMIS-specified properties instead of those from the atom entry.
> >>
> >> -Ryan
> >>
> >> On Tue, May 31, 2011 at 2:01 PM, Naresh Bhatia
> >> <naresh.archfirst@gmail.com>wrote:
> >>
> >> > I am trying to understand the CMIS spec by looking at the Atom output
> >> from
> >> > Alfresco. From the spec it looks like most CMIS attributes are
> >> represented
> >> > as Object properties. However when I look at the Atom output, there
> are
> >> > similar attributes floating outside of properties. For example (highly
> >> > simplified output):
> >> >
> >> > <entry>
> >> >
> >> >    <author>
> >> >        <name>nbhatia</name>
> >> >    </author>
> >> >
> >> >    <id>urn:uuid:5c92e5a7-8563-4a15-8b92-bb4d8ae55ae0</id>
> >> >
> >> >    <title>cmis-article.pdf</title>
> >> >
> >> >    <summary>Examples using CMIS, Abdera, &amp; Chemistry</summary>
> >> >
> >> >    <published>2011-05-25T17:15:36.740Z</published>
> >> >
> >> >    <updated>2011-05-25T17:15:40.045Z</updated>
> >> >
> >> >    <cmisra:object>
> >> >        <cmis:properties>
> >> >            <cmis:propertyString propertyDefinitionId="cmis:createdBy">
> >> >                <cmis:value>nbhatia</cmis:value>
> >> >            </cmis:propertyString>
> >> >
> >> >            <cmis:propertyId propertyDefinitionId="cmis:objectId">
> >> >
> >> >
> >> >
> >>
> <cmis:value>workspace://SpacesStore/5c92e5a7-8563-4a15-8b92-bb4d8ae55ae0</cmis:value>
> >> >            </cmis:propertyId>
> >> >
> >> >            <cmis:propertyString propertyDefinitionId="cmis:name">
> >> >                <cmis:value>cmis-article.pdf</cmis:value>
> >> >            </cmis:propertyString>
> >> >
> >> >            <cmis:propertyDateTime
> >> propertyDefinitionId="cmis:creationDate">
> >> >                <cmis:value>2011-05-25T17:15:36.740Z</cmis:value>
> >> >            </cmis:propertyDateTime>
> >> >
> >> >            <cmis:propertyDateTime
> >> > propertyDefinitionId="cmis:lastModificationDate">
> >> >                <cmis:value>2011-05-25T17:15:40.045Z</cmis:value>
> >> >            </cmis:propertyDateTime>
> >> >        </cmis:properties>
> >> >    </cmisra:object>
> >> >
> >> > </entry>
> >> >
> >> >
> >> >   - Are the attributes at the top (author, id, title, summary,
> published,
> >> >   updated) accessible via CMIS?
> >> >   - Why are the values of <id> and CMIS property objectId different?
> >> >   - Is the <summary> value accessible via CMIS? It does not seem
to be
> a
> >> >   CMIS object property.
> >> >
> >> >
> >> > Thanks.
> >> > Naresh Bhatia
> >> >
> >>
> >>
> >>
> >> --
> >> Ryan McVeigh
> >> Director of Enterprise Integration
> >>
> >> office: 303.443.4004 x204
> >> cell: 720.841.4838
> >> fax: 877.569.7942
> >> Follow Me:
> >> <http://twitter.com/#!/rmcveigh>
> >> <http://www.linkedin.com/in/rmcveigh><
> >> http://www.ziaconsulting.com/blog/rmcveigh>
> >>
> >
>
>
>
> --
> Florent Guillaume, Director of R&D, Nuxeo
> Open Source, Java EE based, Enterprise Content Management (ECM)
> http://www.nuxeo.com   http://www.nuxeo.org   +33 1 40 33 79 87
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message