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."
Is this a nail in the MS XML coffin?
I tip my hat to them.
I don't know that this move has more meaning today than if it was done two years ago, but I certainly see more motivation today. The purpose of the ODF is to ensure that 100 years from now we can still access data. Closed formats mean data may not be accessible in the future. 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.
While I still applaud the effort, Adobe is late to the party.
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
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.
http://www.adobe.com/licensing/developer/fileforma t/faq/#item-1-8:
1) I think you mean "du jour"
2) <IndigoMantoya>I don't think "du jour" means what you think it means.</IndigoMantoya>
"du jour" simply means "of the day" ("soup du jour" => "soup of the day"). I really don't think you intended to claim that becoming the standard of the day is a good thing. I think saying, "PDF will transition from a de facto standard to an official one" would have been clearer, more succinct, and still gotten your intended point across.
Nathan
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).
Quite, which is why things like PDFCreator exist.
AdobeGrl2002: then like u put a 64-byte header blok
ISO_19_TX: thats hot
Yo dawg, I heard you like the Ackermann function, so OH GOD OH GOD OH GOD