Curated for content, computing, data, information, and digital experience professionals

Category: Web technologies & information standards (Page 47 of 59)

Here we include topics related to information exchange standards, markup languages, supporting technologies, and industry applications.

Keynote Debate: Microsoft & Sun: What is the Right XML Strategy for Information Interchange?

I am liveblogging the Keynote Debate between Microsoft and Sun on what is the right strategy for information interchange. The panelists are Tim Bray, Director, Web Technologies, Sun Microsystems, and Jean Paoli, Senior Director, XML Architecture, Microsoft. Jon Udell is moderating.

  • Actually Frank Gilbane is moderating, and not Jon, so we will hear some of Jon’s thoughts as well
  • Frank: the session is really about strategies for sharing, preserving, and integrating document content, especially document content with XML.
  • Frank gave some background about the European Union attempts to standardize on Microsoft Office or OpenOffice
  • Tim elucidated some requirements of your data format. (1) Technically unencumbered and legally unencumbered (2) High quality (and a notable aspect of quality is allowing a low barrier to entry). Tim: “As Larry Wall (the inventer of Perl) noted, easy things should be easy, and hard things should be possible).”
  • Jean predicted that by 2010, 75% of new documents will be XML.
  • Tim agreed with Jean that 75% of new documents will be XML by 2010, but asked how many of them will be XHTML (as opposed toa more specialized schema, I assume).
  • Some agreement by all that electronic forms are an important aspect of XML authoring, but Tim thinks the area is “a mess.” I’m paraphrasing, but Tim commented on the official XForms release, “Well, it’s official.”
  • Jean commented that XML-based electronic forms are made more difficult because forms themselves require consideration of graphical user interface, interactivity, and even personalization to a degree. This suggests forms are more complex than documents. (And this reminds me of a comment Mark Birbeck made about there being a fine line between an electronic form and an application.)
  • Good question from the audience. So much time has elapsed since SGML got started, and we are still only have XSL-FO (which this person was not happy with). What does this suggest about how long it will take to get better, high-quality typographically sophisticated output?
  • Tim would suggest we are seeing some improvement, beginning with better resolution on the screen.
  • Another commenter weighed in, suggesting that format is important and format does convey meaning. Would like to hear that the tools are going to get better.
  • Frank: when do you need a customized schema?
  • Jean: best way to safeguard your data and systems is to have an XML strategy. You can gain efficiencies you never had before. Also suggested that the Microsoft schemas will not somehow trap your content into Microsoft’s intellectual property.
  • Jon’s takeaways: (1) software as service (2) XML-aware repositories and (3) pervasive intermediation (the content flows in such a way that you can intermediate it)

XBRL: You Gotta Love It

One of the cover stories on the new, April Journal of Accountancy carries the blurb: “Six Reasons to Love XBRL.” The article is actually part of continuing coverage by the American Institute of Public Accountants
(AICPA).  The AICPA’s commitment to making CPAs increasingly aware of XBRL
is a good thing if you are interested in seeing more and more ability to do
intelligent processing of financial documents. 

One unfortunate thing about the article, though, is that the six reasons to
love XBRL are all focused primarily on its use outside the company–after
you have produced financial statements in XBRL.  As I have noted
before, some of the really interesting applications–applications that could
be used as part of an internal control framework–happen only if you begin using
it inside the company and earlier in the process.

I think we’ll get there. 

By the way, there is a conference on
XBRL coming up in Boston later this month that you might be interested in if
you are wanting to learn more about XBRL and its applications.

Using XML in Enterprise Content Management: Technologies and Case Studies

As part of the conference next week, I will be doing a tutorial on XML and how it is currently used in content management applications. There is plenty to talk about. While there are few “pure” applications of XML content management, XML is used, in varying degrees, to manage and represent the content, the metadata, the supporting data, and the configuration data in many content management applications.
We will spend some time talking generally about how XML is used in content management applications. Much of the focus will be on a series of brief case studies–example applications really–discussing how successful projects use XML today.

Sun & Microsoft on Open Document Formats & XML Strategy

It wasn’t too long ago that all document formats were proprietary, and vendors that sold authoring and publishing software had a really unfair advantage over their customers because it was so difficult and costly for organizations to convert their content from one proprietary system to another. It was the granddaddy of descriptive markup, SGML, that led the way to the infinitely improved situation we have today with seemingly universal support for XML, and tools like XSL, XQuery etc. So, if most major software applications support reading/writing of XML, including the 800 pound gorilla of office documents Microsoft Office, hasn’t the issue of proprietary formats gone away?

If you are in charge of protecting your organizations content/document assets, you better not be thinking your problems are over. If you are involved in sharing content with other organizations or among applications, you already know how difficult it is to share information without loss — if it is that difficult to share, how easy will it be to migrate to future applications?

Our keynote debate in San Francisco next week is all about helping you understand how to best protect and share your content. While there are some differences between the Microsoft and Sun positions represented by Jean Paoli and Tim Bray, I think they agree more than they disagree on the critical issues you need to consider. We’ll be looking at different aspects of the issue including technology, licensing, cost, and complexity vs. flexibility. For some background see Jon Udell’s posts here and here, and the Cover Pages here. Both contain links to additional info.

I almost forgot… What does this have to do with my earlier posts on the future of content management and Longhorn? Well, Office applications, like all content applications, should benefit from an operating system that can manage content elements and attributes that could be described in XML. Would this make document interchange easier? I don’t know, but it might be fun to explore this question in the session.

If you have a specific question you would like us to cover on the panel, send me an email or add a comment to this post and we’ll summarize what happens.
UPDATE: Jon says he is in Jean’s camp on custom schemas and Tim’s on XHTML. At our Boston panel I think all of us agreed – of course neither Tim nor Jean were there. Jon is tagging his posts on the conference with gilbaneSF2005.

We are using the category and (more wordy) tag Gilbane Conference San Francisco 2005 for all our SF conference postings.

A New Reality for XML and Web Services?

When business people want to condemn a new technology to a geeky grave, they often say that the new thing is “a technology in search of a problem.” This suggests–quite correctly–that the best technology solves a pressing business problem.
Web services, specifically, and service-oriented architectures in general, solve a number of pressing business problems. In particular, web services allow organizations to continue operating legacy systems that work well and that, for various reasons, defy replacement or upgrade. If you can at least reach a point where the legacy system can be integrated with other applications via web services, you likely have a moderate-cost, stable, and workable means to integrate the legacy system with web-facing applications going forward.

Continue reading

XyEnterprise XML Professional Publisher, Design Science MathFlow Editor Integrate to Support MathML

XyEnterprise announced that its XML Professional Publisher (XPP) publishing software now integrates with Design Science’s MathFlow Editor. XPP is an XML-based publishing system used to produce scientific, technical and medical journals, as well as many other types of print and electronic publications. Combined with MathFlow’s graphical interface, which supports the creation of complex mathematical expressions, publishers of complex mathematical information now have a user-friendly publishing tool that supports the MathML standard. http://www.dessci.com,

Longhorn adoption, file systems & content technology

Dan Farber raises the issue of Longhorn adoption and quotes a Jupiter analyst who claims the challenge is that XP is “good enough”. There is actually a more fundamental reason the question of adoption is interesting. What is that and what does it have to do with content technology?

I’ll start the answer with a little history. In 1994 at our first Documation conference, I moderated a debate between Tony Williams, Chief Architect of COM at Microsoft, and Larry Tesler, Chief Scientist at Apple. The Microsoft COM and OFS/Cairo and Apple OpenDoc efforts both recognized the need for operating systems to provide more support for the richness of unstructured information than is possible with the primitive file systems we had then.

Before the debate I preferred the OpenDoc approach because it seemed more consistent with my view that new operating systems needed to be able to manage arbitrary information objects and structures that could be described with a markup language (like SGML at the time). However, Tony convinced me that OpenDoc was too radical a change for both users and developers at the time. Tony agreed with the ultimate need to make such a radical change to file systems to support the growing need for applications to manage more complex content, but he said that Microsoft had decided the world was not ready for such a shock to the system yet, and defended their strategy as the more realistic.

Eleven years later and we are still stuck with the same old-fashioned file system in spite of the fact that every modern business application needs to understand and process multiple types of information inside files. This means that database platforms and applications need to do a lot more work than they should to work with content. I am no expert on Longhorn, but the file system that will be part of it (although maybe not initially), WinFS, is supposed to go a long way towards fixing this problem. Is the world ready for it yet? I hope so, but it will still be a big change, and Tony’s concerns of 1994 are still relevant.

Everyone’s A Publisher

The impact of the Internet on most things personal and professional could be the life’s work of many a sociologist. How we shop, play games, read newspapers and books, and even how we fall in love doesn’t escape redefinition and change. From my perspective, its how we communicate that’s one of the more interesting topics. Safe to say that 10, perhaps even 5 years ago, stating that “everyone’s a publisher” would be quizzical. Now, evidence abounds.

In terms of “social” publishing, blogs and wikis certainly top the list of examples. These days however, those who chat, shop or place a classified ad in a newspaper can also be called a social publisher. And that’s a lot of people.

Granted, the usability of online forms for these types of tasks is usually exceptional enough to hide this fact. But the underlying result immediately publishes opinions, product reviews, and ads to the broadest communication vehicle available today. Even better, the tools are intuitive, fast, cheap, in some cases, free.

In terms of “corporate” publishing, the once contained group of professionals who publish to the Internet is no more. Formalized content technologies allow personnel across most, if not all business units to redefine information creation and delivery — toward the goal of eradicating Web publishing bottlenecks.

The tools in this arena, a.k.a content management systems and according to IDC, “dynamic enterprise publishing products”, certainly don’t boast the same reputation as those for social publishing. In fact, evaluation criteria such as usability, speed and cost often contradicts the notion of “intuitive, fast, and cheap.”

Still, the content technologies software market continues to redefine corporate publishing and support the fact that indeed, “everyone’s a publisher.” And every so often, there’s a real grassroots example of the ever-expanding definition of corporate publishers who create and deliver Web content on a daily basis. From my perspective, Macromedia provides the most recent example.

Since introducing Contribute in December of 2002 for a mere $99, Macromedia has enjoyed consistently growing sales for the past 2 ½ years for this desktop Web content and creation tool. In fact, the company has shipped over 360,000+ seats in less than three years based on the mantra “Web Publishing for Everyone.”

According to the company, users from its business and consumer markets are responsible for the uptake, bolstering a 165% and 258% year-on-year revenue growth respectively. Christening its Web Publishing System in July 2004 with a similar mantra, Macromedia now boasts 250 enterprise customers according to its latest product update release. Both products are included in the company-defined “Information Convenience” category.

Certainly, reputation and marketing have helped Macromedia establish a formidable presence in the corporate publishing arena. A savvy partnership with eBay will surely make a mark in the social publishing arena by introducing Contribute to thousands of consumers.

It’s my opinion, however, that Macromedia’s growth numbers can also be attributed to the fact that everyone is, or at least wants to be, a publisher. And the Internet makes it possible.

Example: in the enterprise, the definition of “everyone” has morphed from the traditional publisher roles such as Webmaster or technical writer into the evolving responsibilities of business unit representatives across a wide spectrum. Borrowing from Field of Dreams, it’s pretty clear that “if you build it, they will come.” Yes, of course it depends how and what you build, not to mention how much it costs! The point is however, that the corporate publishing audience is ready and waiting.

« Older posts Newer posts »

© 2026 The Gilbane Advisor

Theme by Anders NorenUp ↑