Open Web

Get your HTML 5 bug reports filed *before* October 1.  See http://lists.w3.org/Archives/Public/public-html/2010Sep/0074.html for more details.

The Text Encoding Initiative (TEI) is a consortium which collectively develops and maintains a standard for the representation of texts in digital form. Its chief deliverable is a set of Guidelines which specify encoding methods for machine-readable texts, chiefly in the humanities, social sciences and linguistics. Since 1994, the TEI Guidelines have been widely used by libraries, museums, publishers, and individual scholars to present texts for online research, teaching, and preservation. In addition to the Guidelines themselves, the Consortium provides a variety of supporting resources, including resources for learning TEI, information on projects using the TEI, TEI-related publications, and software developed for or adapted to the TEI. The TEI Consortium is a non-profit membership organization composed of academic institutions, research projects, and individual scholars from around the world. Members contribute financially to the Consortium and elect representatives to its Council and Board of Directors.

A while back I included the following as one of the areas of interest of the PDF/D Consortium: Structured Documents and Single Sourcing: improving round-trips to document softwareWhat did I mean by Structured Documents? For years Solid Documents has been converting PDF files to Word documents with a focus on retaining format and layout to allow customers to repurpose the content. While this is a great solution for a large amount of customers, it is not the only type of reconstruction that is interesting. PDF is by nature a "document" format: the layout is in the form of pages. Content also needs to exist in alternate formats like a continuously flowing stream. Use cases for continuously flowing content include:conversion to HTML to reflow for form factors other than "pages"conversion to content management systems where structure is more important than layout and formattingconversion for alternate readers for people with disabilities (text to speech, etc)Reconstruction for these use cases focuses more on the structure of the document than on the layout and formatting. For example, we need to take unstructured PDF files and recognize columns, tables, lists, headers and footers, etc. This allows us to organize the content in a logical structure. Ultimately, we'll recognize topics and sections too so that we can produce logical hierarchies from plain old non-tagged PDF files. One great example of where conventional PDF pages are not the most appropriate way to read a document are on small screens of handheld devices. For example, the typical Blackberry has a 3"x2" screen with a resolution something like 320x240 pixels.

According to Aberdeen, the next generation web content management system needs to bridge the inter-system gap - providing marketers with actionable insights that can support and enhance online engagement.  To find out more about the challenges for today's marketers and how the next generation of web content management system can support them, check out the Aberdeen Group's report (hosted by Sitecore) entitled Next Generation WCM: A Comprehensive Assessment of Current Challenges and The Future of WCM.

According to a new Forrester report, though Microsoft Office continues to be a mainstay both in the enterprise and at home, developing concerns about productivity as they relate to mobile, cloud, and collaboration may bring a shift in enterprise behaviors.

It's official now. OpenSolaris is abandonware, leaving OpenBSD as the major open Unix platform still supported.    

From the NOT So OpenWeb department, MacroView provides a folder based hierarchy view of MSOffice, OutLook and PDF documents/messages.  Note that the metadata information is held at the server level - it is not part of of the document container!  Which is another way of saying that while the document might be portable, the metadata and layered components/relationships involving that document are not.  SharePoint only.  I doubt google Search will be able to access and read this metadata. intro:  Enable full function document management in Microsoft® SharePoint® 2007 and 2010 - save, browse and search from the applications that you use every day with MacroView DMF™ v7 (formerly known as MacroView WISDOM DMF)

Patent application filed on OASIS UOML access by API. 0002]The present invention relates to electronic document processing technologies, and particularly to a method for encapsulating Unstructured Operation Markup Language (UOML) into an Application Programming Interface (API).  BACKGROUND OF THE INVENTION  [0003]The UOML standard includes a series of docbase management system instructions defined according to a format of "action+object" in Extensible Markup Language (XML), which has been explained in detail in an UOML Standard published by of the Organization for the Advancement of Structured Information Standards (OASIS ). Since XML works across different platforms and with different languages, the UOML standard can enable the docbase management system instructions to be exchanged across the different platforms in the different languages. However, in practical applications, operations on a docbase are usually controlled by using programs written in programming languages, hence the programs need to parse and process UOML XML texts. If every application developer designs his/her own way of parsing and processing UOML XML texts in his/her programs, the workload of coding will increase significantly and the efficiency of coding will drop sharply.  SUMMARY OF THE INVENTION  [0004]The objective of the present invention is to provide a method for encapsulating Unstructured Operation Markup Language (UOML) into an Application Programming Interface (API) of a programming language so as to improve the development efficiency of docbase management system application developers.  [0005]The method provided by the present invention for encapsulating UOML into an API includes:  Read more: http://www.faqs.org/patents/app/20090187927#ixzz0xVS2ZUSr

Aspose.Words Product Family Save any Document from Microsoft Word 2007 to EPUB using a Free Add-in from Aspose We are happy to announce the first release of a free add-in that allows you to convert any document opened in Microsoft Word 2007 to EPUB. To download goto http://www.aspose.com/community/files/69/free-microsoft-office-add-ins/aspose.words-for-microsoft-word/default.aspx. Below are excerpts from the user's guide that is included in the installer. Introduction Aspose.Words for Microsoft Word is a free utility that allows converting any document opened in Microsoft Word 2007 to the EPUB format. Microsoft Word 2007 can load documents in many formats including DOC, DOCX, RTF, HTML, ODT etc and you can now easily convert them all to EPUB using Aspose.Words for Microsoft Word. About the EPUB format EPUB is an XML-based distribution format for eBooks that is rapidly gaining adoption by publishers and distributors. EPUB is an open standard supported by the International Digital Publishing Forum (IDPF) organization. See also the Wikipedia article. To Save as EPUB After you install Aspose.Words for Microsoft Word, the EPUB format will be listed in the Save As dialog. Saving to EPUB is just as simple as saving to any other file format available in Microsoft Word. 1.      Open any document in Microsoft Word. 2.      From the Save As menu select "Aspose.Words - EPUB (*.epub)", and then click Save. You can save any document from Microsoft Word to EPUB using Aspose.Words for Microsoft Word.

MathML 3 achieves proposed recommendation status. For those unfamiliar with W3C lingo, this means that it is now a proposed standard. Concurrently, W3C published a proposed recommendation for a A MathML for CSS Profile, http://www.w3.org/TR/2010/PR-mathml-for-css-20100810/

While the candidate Media Queries specification is interesting and a small step in the right direction, W3C continues to butcher the meaning of "interoperability." In this latest sleight of hand, we now have "interoperable" *user agents*, a term of art used by W3C for implementations that only receive and cannot return data, e.g., web browsers. But under competition law, "interoperability" requires implementations that can exchange data and *mutually* use data that has been exchanged. See e.g., European Commission v. Microsoft, European Community Court of First Instance (Grand Chamber Judgment of 17 September, 2007), para. 230, 374, 421, http://tinyurl.com/23md42c (rejecting Microsoft's argument that "interoperability" has a 1-way rather than 2-way meaning; "Directive 91/250 defines interoperability as 'the ability to exchange information and *mutually* to use the information which has been exchanged'") (emphasis added). W3C --- the World Wide Web Conspiracy --- continues down its rut of broadcasting information whilst denying the world the power to round-trip the data received. Incredibly, in its latest assault on the meaning of "interoperability", W3C no longer defines "conformance" but redefines the term "interoperability" as its substitute for "conformance." As though W3C could redefine the law?

The Future of the Open Web You're right that the browser wars do not matter - except for this point of demarcation; browsers that support HTML+ and browser that support 1998 HTML. extensive comment by ~ge~ Not all Web services and applications support HTML+, the rapidly advancing set of technologies that includes HTML5, CSS3, SVG/Canvas, and JavaScript (including the libraries and JSON). Microsoft has chosen to draw the Open Web line at what amounts to 1998-2001 level of HTML/CSS. Above that line, they provision a rich-client / rich-server Web model bound to the .NET-WPF platform where C#, Silverlight, and XAML are very prominent. Noticeably, Open Web standards are for the most part replaced at this richer MSWeb level by proprietary technologies. Through limited support for HTML/CSS, IE8 itself acts to dumb down the Open Web. The effect of this is that business systems and day-to-day workflow processes bound to the ubiquitous and very "rich" MSOffice Productivity Environment have little choice when it comes to transitioning to the Web but to stay on the Microsoft 2010 treadmill. Sure, at some point legacy business processes and systems will be rewritten to the Web. The question is, will it be the Open Web or the MS-Web? The Open Web standards are the dividing line between owning your information and content, or, having that content bound to a Web platform comprised of proprietary Microsoft services, systems and applications. Web designers and developers are still caught up in the browser wars. They worry incessantly as to how to dumb down Web content and services to meet the limited functionality of IE. This sucks. So everyone continues to watch "the browser wars" stats. What they are really watching for though is that magic moment where "combined" HTML+ browser uptake in marketshare signals that they can start to implement highly graphical and collaboratively interactive HTML+ specific content. Meanwhile, the greater Web is a

Microsoft today won the skirmish, the battle, and--in light of the leanings of a Bush/Ashcroft Justice Department--probably the war, in its fight against the pesky antitrust suit that's been nipping at its heels. With much of the decision accusing the behemoth of violating the Sherman Act exploded, Microsoft may now go down in history as the Little Monopolist That Could. In the short run, they've bought more time. In the medium run, settlement is probably inevitable, and in the long run, they have almost no possibility of a breakup. Not a bad day's work for a busy monopolist. (Full disclosure: Microsoft publishes Slate.)

Summary:  It was 10 years ago this week that Judge Thomas Penfield Jackson ordered Microsoft split in two as a remedy for abusing its Windows monopoly. That judgment was tossed out on appeal, but the eventual antitrust settlement has had plenty of repercussions. From crapware to insecurity, here's my wrap-up of what 10 years of antitrust regulation has really accomplished.