Today Adobe has announced that the PDF 1.7 specification will be published to AIIM, the Enterprise Content Management Association, for the purpose of publication by the International Organization for Standardization (ISO).
Obviously, PDF is already a standard — everyone who is anyone uses it, but in standards parlance it is not an “Open Standard”, because Adobe help sole control of it until now. In other words, PDF is a “de facto” standard…but we want to go one step further and put PDF out as a proper standard.
You can read the press release here
Since a commenter asked about what works on Intel-based Macs, I thought I’d post the official Adobe policy here.
I wrote a quick blog post on my personal blog that provides pointers to the things you will need to remap the delete key and get right click working with the trackpad under windows.
Check it out
These new LensBaby 2.0 selective focus lenses are just awesome. Check it out.
I can recall a recent shopping expedition in which I was searching for the perfect bath robe. Being a frequent traveller, I am used to having these “one size fits all” bath robes not fit my frame very well…and definitely wanted to improve the bath robe wearing experience considerably…at least at home.
I quickly realized that “One Size” was not my size. It turns out that I needed XL…now I am a happy camper with a properly fitting bath robe.
(Fairmont San Jose…if you are reading this….c’mon, buy some XL robes already)
Ok…so now you’re wondering “Is this guy for real? Is this all he thinks about? Bath robes?”. I am for real, and I felt that the bath robe story illustrates how I feel about an activity going on over at OASIS to develop a set of patterns & anti-patterns for implementers of Service Oriented Architecture.
A recent “anti-pattern” that has been discussed is about having too many services. The argument is that when we have too many services, it becomes dificult to find and invoke them. It would be better to group related services together and reduce some of the noise.
Now…in some architectures this could be a reasonable anti-pattern. I am sure there are SOAs out there that do not have any mechanism for classifying and managing services so as to help consumers to efficiently make use of a large body of services. On the other hand, I am also sure that there are SOAs out there that use an efficient, local transport which allows for fine grained services to be employed without serious performance penalties, and use a registry system (UDDI, ebXML, ISO 11179, …) to classify and manage their services.
I don’t mean to pick on this particular anti-pattern (In fact, the Blueprints TC has more or less dropped this as an anti-pattern)…I actually mean to attack the parent concept of all this, which is that of a few practitioners of a particular architectural style making broad statements about what is good and bad. This frustrates me to no end since I have spent the last year trying very hard to formalize Service Orientation as a valid software development paradigm. What the software industry needs now is a really good understanding of what Service Oriented Architecture really is, and what it means to their organizations in the long term. Generalizations such as “Don’t create hundreds of services.” or “Create hundreds of services.” are not really useful because those statements only apply in certain circumstances. Practitioners need help understanding when and why they should go coarse or fine grained…and that is the goal of foundational work such as SOA-RM.
I recently decided that I would like to have some kind of tool that I could run to backup all of my photos on Flickr. I basically wanted a directory containing a bunch of subfolders representing sets, with the original photos placed within. I also wanted all of the photos that I had not placed into a set to be downloaded.
Over the course of the weekend, I’ve become a developer on the flickrj “team”. You gotta love open source “Hey, maintainer. Are you going to fix bug x?” “No, user, I’m busy. Do you want to do it?”.
So…if you are a Java coder, and want to do neat stuff with Flickr, do check out FlickrJ. My backup program is also up there, checked into flickrj’s CVS repository.
Update: The actual backup application is here: http://cvs.sourceforge.net/viewcvs.py/flickrj/api/src/flickrj/samples/
In case you haven’t heard, we released v7 of the LiveCycle server platform recently. You can read the official press release here.
The press release spends a lot of time on the new workflow solution, but a lot of other major stuff is included in this release including Form Manager Registry, an ebXML Registry implementation which forms the backbone of our form management strategy and technology stack. The registry software is what I am directly responsible for, so I am very happy to see this great stuff ship. Its been a long development process (about a year), but the result is a much improved platform, and in the case of the registry, the first scalable and commercially supported ebXML Registry implementation on the market.
As I mentioned in my introduction, my place at Adobe is within the LiveCycle engineering team…so it is a bit ironic that one of my first posts on this blog is about Photoshop CS2.
In my spare time, I am an avid amateur digital photographer. I enjoy taking photos of nearly anything, but the fact of the matter is that I am not really a great photographer yet. Instead, I lean on one of the most excellent software packages ever invented — Photoshop. I’ve been able to do basic tasks with Photoshop for some time now, the basics like cropping, naive color correction, fixing under/over exposure but have found myself getting more and more interested in doing things correctly, and exploiting more of the functionality that lurks just under the surface of the Photoshop UI.
So I bought a book. “The Photoshop CS2 Book”, by Scott Kelby. I’m a day in with it, and about 5 experiments in and all I can say is “Great book!”. The author does a great job of walking the reader through many very useful tasks, and does his best to explain what is happening technically. I appreciate the howto + “science of” approach in books because I learn faster by understanding why I’m doing things.
If you are a beginner, or intermediate photoshop user…this book is probably for you.
This is my first blog post at blogs.adobe.com, so an introduction is probably in order.
My name is Matt MacKenzie, and at Adobe I fill the role of Software Development Manager for the ebXML Registry component that is part of the Adobe LiveCycle Form Manager product. I’ve been with Adobe now for close to two years. In addition to my work in product development, I also am involved with some standards work at OASIS – Specifically the SOA-RM Technical Committee, and to a lesser extent the ebXML Registry and Messaging TCs.
I hope to share information about Adobe’s Form Manager product on this blog, as well as discuss any interesting events that I am involved in or notice happening at OASIS.
I have also been blogging a bit on my own for a couple of months, you can see that blog at mac-kenzie.net.
Until the next post….