Adobe To Release Full PDF Specification to ISO

nickull writes "Adobe announced it will release the entire PDF specification (current version 1.7 ) to the International Standards Organization (ISO) via AIIM. PDF has reached a point in its maturity cycle where maintaining it in an open standards manner is the next logical step in evolution. Not only does this reinforce Adobe's commitment to open standards (see also my earlier blog on the release of flash runtime code to the Tamarin open source project at Sourceforge), but it demonstrates that open standards and open source strategies are really becoming a mainstream concept in the software industry. So what does this really mean? Most people know that PDF is already a standard so why do this now? This event is very subtle yet very significant. PDF will go from being an open standard/specification and de facto standard to a full blown de jure standard. The difference will not affect implementers much given PDF has been a published open standard for years. There are some important distinctions however. First — others will have a clearly documented process for contributing to the future of the PDF specification. That process also clearly documents the path for others to contribute their own Intellectual property for consideration in future versions of the standard. Perhaps Adobe could have set up some open standards process within the company but this would be merely duplicating the open standards process, which we felt was the proper home for PDF. Second, it helps cement the full PDF specification as the umbrella specification for all the other PDF standards under the ISO umbrella such as PDF/A, PDF/X and PDF/E. The move also helps realize the dreams of a fully open web as the web evolves (what some are calling Web 2.0), built upon truly open standards, technologies and protocols."

Comments

ISO approved PDF

[Xymor]

Is this a nail in the MS XML coffin?

Re:ISO approved PDF

[99BottlesOfBeerInMyF]

Even the most verbose XML couldn't come close to the unbelievable bloat that is .PDF.

The PDF standard does not seem particularly bloated to me.

I got sick of PDF's taking forever to loading, and the reader hanging constantly on our PC's at work, so I banned them from from the office. It shouldn't take a bleeding edge machine to open plain old documents in a reasonable amount of time.

Ignorance is one of the main reasons why open standards lose to MS proprietary ones in the market. The average person does not understand the advantages. One of the main advantages is that no one is locked into a single vendor for their tools. Despite this almost everyone uses the combination of Window+IE+Adobe Acrobat Reader Plug-in. This is a terrible toolset and is bloated, slow, and poorly designed. Windows can't multi-task memory resources if your life depended upon it. IE itself is bloated and poorly handles threading plug-ins and will hang the whole process until a download is complete. The acrobat plug-in is slow and bloated with all the default settings turned on. The end result is an average user with an average machine clicking on a PDF link and their whole machine grinding to a halt while it waits for the download to finish, then they get to wait yet longer while the Acrobat plug-in eventually gets around to its main purpose.

The solution is, quite simply, don't use that combination of tools. If you're on Windows there are plenty of great, free PDF readers. Foxit is my favorite. On Linux I like XPDF and on OS X I like Preview. You have choices because PDF is an open standard. Blaming a standard for the failings of a given tool is just plain incorrect.

Now I imagine you won't care what I say anyway and will be quite happy when Microsoft's bundled XPS format takes over the market. It will even render faster for you for some time, since the default tools will be built into the OS's display APIs. You'll probably be happy about this for years until you realize you can't move to another platform because all your files are trapped in one only MS's reader will open. Moreover, you'll probably be wondering why you need a top end machine 5 years from now to open files you used to be able to open on your old machine, but since there will only be one reader available you'll be stuck with that. And if they start adding DRM as a mandatory feature on XPS files, so that you have to register all the documents you create with MS, well what can you do? Sure you'll complain about these things, but what will you do? Everyone uses XPS and if you ever want to submit a resume you need to have Windows with its built-in XPS tools.

...or maybe you won't. Maybe you and the rest of the industry will wise up to the advantages of open standards, as a few large organizations currently seem to be doing. Maybe you'll just download a good PDF viewer and think to yourself, wow I'm glad I have options and I'm not stuck with just one viewer, that would suck."

Thanks Microsoft?

[paugq]

Translation for mere mortals: Adobe is feeling the breath of Microsoft and its Metro. They are so scared to become the next Netscape they are trying to nil any reason people may have to use Microsoft's XPS.

Flash SWF file specification not open

[NearlyHeadless]

You cannot download the Flash File Format (SWF) specification without agreeing to a license which forbids writing a flash interpreter.

http://www.adobe.com/licensing/developer/fileforma t/faq/#item-1-8:

Can I use the File Format Specification to create a SWF interpreter or player?

No, the File Format Specification is provided for the specific purpose of enabling software applications to export to the Macromedia Flash File Format (SWF).

Re:Kudos to them

[c_fel]

PDF used to be the sole means to have a document look exactly the same across any platform. That is no longer the case, and even Microsoft has opened the standard (mostly) on their new Office data files.

No, I disagree. Even when open office formats, the document won't look exactly the same on one an other platform. Example : the open document format (.odt) renders somewhat differently when opened in OpenOffice for Windows and OpenOffice for Linux. And it may be completely different when opened with koffice.
The content is the same, though.

What I believe is the .pdf excels in porting the exactly same layout of a page between platforms and softwares, while Office files excel in porting the exact editable content. Their goals are simply not the same.

Great news, but not necessarily a free-for-all

[The Empiricist]

It is wonderful to hear that the PDF specification will be the subject of open standardization. Caution should be exercised when implementing products though. Almost 400 patents have been granted to Adobe. Adobe has another 50 patent applications in process. There may also be additional patents that have been assigned to Adobe or that Adobe has an exclusive license to practice. Adobe may also have intellectual property in foreign markets that are greater in scope than what Adobe has in the United States.

Caution should be exercised because ISO does not require that its standards be patent-free. Necessary patents merely must be available on a reasonable and non-discriminatory basis. Adobe (or anyone else really) may also seek patents on how PDFs are used, manipulated, etc.

This doesn't necessarily mean that Adobe is bad or that any Open Source Software projects will ever face any obstacles from Adobe. It simply means that some care should be taken to determine whether any of Adobe's patents cover features of the PDF standard or its uses, especially when developing software that mimics an existing proprietary product. If there is a question, then OSS developers should contact Adobe to try to get a license (perhaps for the consideration of a promise that the resulting product remain open source).

Re:Well...

[ettlz]

There is no reason that it needs to cost so much to create non-editable documents.

Quite, which is why things like PDFCreator exist.