Tomorrow at 11:30am local time there will be an informal CMIS panel at the AIIM info360 conference in Philadelphia (i.e. Doculabs expo booth 434). This panel is organized by AIIM (Betsy Fanning). Thomas Pole, iECM co-chair and organizer of the CMIS demo, will be the moderator.
My EMC colleague and OASIS CMIS TC chair, Dr. David Choy, will provide an overview of CMIS at 11:30am leading into the panel discussion. As a reminder to my fellow TC’ers, the panel is open to any TC member.
So, if you’re at AIIM info360 and want to learn more about CMIS, please join the discussion. You can also stop by the EMC booth (#825) for the duration of the expo. Cheers!
Thanks to a recent IT change concerning the OASIS JIRA server, I can now leverage ALM Works JIRA Client to work OASIS CMIS TC issues.
Furthermore, all OASIS Issue Trackers in the single OASIS JIRA server are available to me–or any other OASIS member!
Here is how…
- Visit ALM Works and download JIRA Client.
- Install JIRA Client and choose “Run JIRA Client” before exiting the installer.
- Enter your license key. That is, download deskzilla_oasis.license to your local %USERPROFILE%\.JIRAClient directory (e.g. C:\Documents and Settings\YourUserName\.JIRAClient, on a Windows XP machine), and point your JIRA Client instance to your local license file (i.e. select it).
- Verify the following license data is presented upon selection:
Licensed to: open-source community
Support ID: 4000383
- Restart JIRA Client in order for this license to take effect (i.e. Start | Programs | JIRA Client | JIRA Client).
- Configure connection (i.e. enter your OASIS member login credentials).
- Connect and select the OASIS issue trackers of interest.
- Initialize connection, which may take a short amount of time during first-time initialization.
At this point you should be able to leverage JIRA Client against OASIS issue trackers (e.g. CMIS).
- A big thank you to ALM Works founder, Igor Sereda, for his support of open source projects and organizations like OASIS.
- Thanks also go to Mary McRae of OASIS for gently vetting JIRA Client licensing details, since I’m not an OASIS employee.
Just to be clear, this ALM Works software is not being provided by, nor licensed to OASIS as an organization. The JIRA Client license from ALM Works isn’t granted to OASIS, but it’s restricted to access the OASIS JIRA repository. Each person who installs will need to determine whether or not they are able to accept the licensing agreements for their organization.
Earlier today, John Newton posted a nice summary of what the OASIS CMIS Technical Committee (TC) accomplished this Monday through Wednesday. Anyone interested in the CMIS progress will want to read John’s post.
Earlier this week, EMC released its second Early Access bits that support both bindings in the current draft specification.
It was great to spend time focusing on technical issues and discussing proposals to resolve them. Sometimes there simply isn’t a substitute for working with others in the same room! It was also nice to catch up with prior colleagues–John and Dave Caruana–and establish new report with others in the Enterprise Content Management industry.
In particular, I appreciate the effort made by TC’ers from EMC and IBM to get our bits–both REST and SOAP–interoperating together. We did make demonstrable progress–however difficult the technical environment (i.e. lack of viable network onsite) proved to be. (I’ll post my WCF test client (CMIS WSDL endpoint consumer) separately.)
(By the way, if you ever test MTOM content transfer while outputting messages to a console window, think twice about logging all HTTP traffic. I think that folks in the lobby of building 40 thought my laptop was a bomb when I rushed to leave the TC meeting after I couldn’t get my computer alarm to silence or stop–until a hard power-down action was applied. )
Update 1/31/2009: Thanks to Dennis Hamilton, here is a group photo of those physically present at the TC meeting:
Robin Cover just published a technology report for CMIS to support the activities of the OASIS CMIS TC and external commentary, and with the intent to update the document with relevant bibliographic references as the Technical Committee work progresses. Thanks, Robin.
This week has seen REST experts Roy Fielding and Sam Ruby comment on CMIS. As someone directly involved in CMIS, I wanted to acknowledge both Roy’s remarks and Sam’s remarks, which follow onto Roy’s.
The standards effort based in OASIS that is CMIS is indeed just getting started, as Sam notes. There is a lot of work to be done, and CMIS needs timely, constructive feedback from the wider community if it is to become widely adopted.