Group items tagged

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

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)

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

With the increased interest in cloud, software as a service (SaaS), and mobile computing, applications are jockeying across multiple networks, both in terms of how services are assembled, as well in how users in different environments access and respond to these critical applications. Indeed, cloud computing forces a collapse in the gaps between the former silos of private, public, and personal networking domains. Since the network management and governance tasks have changed and continue to evolve rapidly, so too must the ways in which solutions and technologies address the tangled networks environment we all now live and work in.

The Barcelona World Mobility Conference is under way, and Microsoft is making a show of force.  They are hitting with features that support both "Social Network Hubs" (People Hub) and "Productivity Hubs" (Office Hub).  The key to Microsoft's Windows 7 Smartphone success is not that of new and exciting features competitive with Apple and Google smartphones.  No, the key feature that Microsoft owns is that of integration into legacy desktop productivity business systems based on the MSOffice productivity platform, and, more importantly, integration into the emerging Web centered but proprietary Microsoft Business Productivity Platform.  Stay tuned. excerpt on the new Windows 7 feature set:  The Office Hub lets you easily sync your documents between your phone and your PC. Office Hub comes with OneNote, for notetaking, Documents and Sharepoint for presentation collaboration. Users will also have access to an Outlook Mail application which gives similar features, like flagging important e-mails, that you'd find on the desktop version.

I disagree with the authors conclusions here.  He misses some very significant developments.  Particularly around Google, WebKit, and WebKit-HTML5. For instance, there is this article out today; "Google Really is Giving Away Free Nexus One and Droid Handsets to Developers".  Also, Palm is working on a WiMAX/WiFi version of their WebOS (WebKit) smartphone for Sprint.  Sprint and ClearWire are pushing forward with a very aggressive WiMAX rollout in the USA.  San Francisco should go on line this year!   One of the more interesting things about the Sprint WiMAX plan is that they have a set fee of $69.00 per month that covers EVERYTHING; cellphone, WiMAX Web browsing, video, and data connectivity, texting (SMS) and VOIP.  Major Sprint competitors, Verizon, AT&T and TMobile charge $69 per month, but it only covers cellphone access.  Everything else is extra adn also at low speed/ low bandwidth.  3G at best.  WiMAX however is a 4G screamer.  It's also an open standard.  (Verizon FIOS and LTE are comparable and said to be coming soon, but they are proprietary technologies).   The Cable guys are itneresting in that they are major backers of WiMAX, but also have a bandwidth explosive technology called Docsis. There is an interesting article at TechCrunch, "In Mobile, Fragmentation is Forever. Deal With It."  I disagree entirely with the authors conclusion.  WebKit is capable of providing a universal HTML5 application developers layer for mobile and desktop browser computing.  It's supported by Apple, Google, Palm (WebOS), Nokia, RiMM (Blackberry) and others to such an extent that 85% of all smartphones shipped this year will either ship with WebKit or, an Opera browser compatible with the WebKit HTML5 document layout/rendering model.   I would even go as far as to say that WebKit-HTML5 owns the Web's document model and application layer for the future.  Excepting for Silverlight, which features the OOXML document model with over 500 million desktop develop

EU settlement will alter Microsoft's stance on interoperability By Kurt Mackie Dec 21, 2009 Microsoft provided more details about its settlement with the European Commission (EC), particularly with regard to interoperability agreements. In a blog post on Thursday, Dave Heiner, Microsoft's vice president and deputy general counsel, claimed that the company has pledged to implement a threefold approach to interoperability that EC Commissioner Neelie Kroes outlined in past speeches. Heiner summarized that approach: companies should disclose technical information, provide a remedy if the information is inadequate and charge equitable royalty rates for associated intellectual property. Kroes had also specifically called for companies to follow open standards as one of the best ways to achieve interoperability. However, Heiner omitted the word, "open," from his comment. He said that "products from different firms can work well together when they implement common, well-designed industry standards." Microsoft's interoperability pledge announced this week appears to continue ideas the company put forth in February 2008. At that time, the company announced broad interoperability principles as well as APIs for software developers working with Microsoft's mainline products, including Windows client and server operating systems, Exchange, Office and SharePoint, among others. Microsoft has been releasing documentation for that purpose, with "hundreds of Microsoft developers" devoted to the effort, according to Heiner. The new elements to Microsoft's interoperability pledge appear to be warranty and patent-sharing templates. Those documents, and more, can be accessed at the end of a statement about the settlement by Brad Smith, Microsoft's senior vice president and general counsel.

Office suites are now taking the cloud route and offering advanced services, luring partners with smart gain  By Varun Aggarwal While all applications are moving to the cloud, there is no reason why the ubiquitous office productivity suites like MS Office or OpenOffice should stick to the desktop. Providing customers with a key set of capabilities, and a browser to aid easy access makes complete sense. Take for instance a student working on a class paper. Writing in a Web browser might aid in sharing and incorporating constructive changes, but it is a cumbersome experience as compared to using Office on his PC. But by using productivity suite online, he gets best of both worlds.  

... The Internet Operating System is an Information Operating System ... Search is key to managing and working "information" ... Media Access ... Communications ... Identity and the Social Graph ... Payment ... Advertising ... Location ... Activity Streams - "Attention" ... Time  ... Image and Speech Recognition ... Government Data ... The Browser Where is the "operating system" in all this? Clearly, it is still evolving. Applications use a hodgepodge of services from multiple different providers to get the information they need. But how different is this from PC application development in the early 1980s, when every application provider wrote their own device drivers to support the hodgepodge of disks, ports, keyboards, and screens that comprised the still emerging personal computer ecosystem? Along came Microsoft with an offer that was difficult to refuse: We'll manage the drivers; all application developers have to do is write software that uses the Win32 APIs, and all of the complexity will be abstracted away. This is the crux of my argument about the internet operating system. We are once again approaching the point at which the Faustian bargain will be made: simply use our facilities, and the complexity will go away. And much as happened during the 1980s, there is more than one company making that promise. We're entering a modern version of "the Great Game", the rivalry to control the narrow passes to the promised future of computing.

Bingo!  Took five years, but finally someone gets it: excerpt:  Great question. After 10 years, OpenOffice hasn't had much traction in the enterprise - supported by under 10% of firms, and today it's facing more competition from online apps from Google and Zoho. I'm not counting OpenOffice completely out yet, however, since IBM has been making good progress on features with Symphony and Oracle is positioning OpenOffice for the web, desktop and mobile - a first. But barriers to OpenOffice and Web-based tools persist, and not just on a feature/function basis. Common barriers include: Third-party integration requirements. Some applications only work with Office. For example, one financial services firm I spoke with was forced to retain Office because its employees needed to work with Fiserv, a proprietary data center that is very Microsoft centric. "What was working pretty well was karate chopped." Another firm rolled out OpenOffice.org to 7,00 users and had to revert back 5,00 of them when they discovered one of the main apps they work with only supported Microsoft. User acceptance. Many firms say that they can overcome pretty much all of the technical issues but face challenges around user acceptance. One firm I spoke with went so far as to "customize" their OpenOffice solution with a Microsoft logo and told employees it was a version of Office. The implementation went smoothly. Others have said that they have met resistance from business users who didn't want Office taken off their desktop. Other strategies include providing OpenOffice to only new employees and to transition through attrition. But this can cause compatibility issues. Lack of seamless interoperability with Office. Just like third-party apps may only work with Office, many collaborative activities force use of particular versions of Office. Today's Web-based and OpenOffice solutions do not provide seamless round tripping between Office and their applications. Corel, with its

Web 2.0 2009 presentation is loaded with charts and numbers, all of which point to an explosive growth in mobile access to the Internet.  Lots of 3G projections.  Nothing on 4G though.  This years Web 2.0 will no doubt be all about 4G and LTE, Apple, and Google Android/Chrome

WiMAX (worldwide interoperability for microwave access) is a fourth-generation (4G) telecommunications technology primarily for fast broadband. Also a 4G mobile technology, LTE allows a peak download speed of 100 megabits per second (Mbps) on mobile phones, compared with 20Mbps for 3G and 40Mbps for WiMAX. "For operators, the choice of technology depends on a number of things including available spectrum, legacy inter-working, timing and business focus," says Nokia Siemens Networks head of sub region, Asia South, Lars Biese. To deploy either technology, operators will have to commit tens of billions of dollars in network upgrades for the new mobility landscape, which now includes social, video, location-based and entertainment applications and experiences. Wing K. Lee says WiMAX and LTE more similiar than different. Also a 4G mobile technology, LTE allows a peak download speed of 100 megabits per second (Mbps) on mobile phones, compared with 20Mbps for 3G and 40Mbps for WiMAX. Some argue that LTE is the next step for mobile networks like GSM, WCDMA/HSPA and CDMA in the move to future networks and services. The common belief is that the natural migration path is from 2G to GPRS, from GPRS to 3G, and from 3G to LTE. But IDC Asia/Pacific's telecom research director Bill Rojas has a differing view. To him, LTE is a totally new set-up. It has been reported that LTE's main advantage over WiMAX, in addition to speed, is that it is part of the popular GSM technology and can allow backward compatibility with both 2G and 3G networks. A point many dispute.  The new Sprint EVO is a 4G smartphone with chipsets for 2G, 3G, 3G enhanced, and 4G WiMAX.  Sprint argues that LTE is just another chipset away.

Amazon Releases Developer SDKs One interesting and important exception is Amazon's recent release of its Software Development Kits (SDK) for Google's Android and Apple's iOS. With these kits, developers are provided with tools that will simplify development of cloud applications stored on the Amazon Web Services cloud platform, or AWS. Developing apps that can use many of the already popular AWS cloud services offers many new opportunities for the developer community, especially due to its low-barrier-to-entry and affordability, enabling more developers with limited resources  to build and provision new mobile cloud services. The new SDK includes libraries that simplify handling of HTTP connections, request retries and error handling, which used to be complex and arduous. Integration of applications with several AWS cloud services, like the Simple Storage Service (S3), SimpleDB database, Simple Notification Service (SNS) and Simple Queue Service (SQN) will be much more accessible than before. For example, it's going to be interesting to see whether developers will build a viable messaging solution atop the AWS SNS service that can actually compete with mobile SMS services - which have been a long-time major cash-cow for many mobile network operators.

Essentially, what CloudConnect does is to enable users to view documents that are stored in the cloud without having to upload them, while giving document providers complete control over the document. What this means is that no matter who views the document, it won't ever be uploaded on Adeptol servers. An additional feature is that document creators can create documents in any format they want and deliver them to users in the format that they can best view it in. New features include: ..... AJAX document viewer with support for more than 300 file formats ..... Mobile Viewer license that enables users to view documents on iPhone/iPad and Android with enhanced loading times .....Built in AES encryption that can be turned on at will. Encrypts not only document content but document URL too .... Advanced caching enabling users access static documents directly from the cache Adeptol viewing technology is based on the adoption of HTML 5 technology that enables viewing across a wide range of mobile devices including iPad, Android, Blackberry and Windows Mobile. 300+ file formats available in the viewer

In addition to its ability to sync to mobiles and tablets, ShareFile also lets user's work with their existing folder structure, rather then demanding everything goes into one drop folder. The two-way functionality works via an Adobe Air 2.0 app, while Sync itself is part of ShareFile's Power Tools suite that comes with desktop and mobile apps, Outlook plug-ins and other goodies

RuleLab.Net is a web-based system for designing and implementing the business rules that operate on an application's XML data. Extend your existing applications by adding Rule building and Business Rules Engine (BRE) capabilities. Consolidate your business logic in an easy to read format, build, test, share, and deploy your Rules using the web browser; and integrate them into your system via the BRE. Intuitive GUI, English-like syntax, and centralized repository empower business users with direct access to the Rules.In the RuleLab.Net system, Business Rules are composed and managed over the Internet or Intranet using the web-based Rules Designer. It allows users to associate an application XML data template with Rules, create a vocabulary of natural terms, graphically build complex logical expressions, test the Rules on data samples, and store the Rules in a database. Features include strong data types, reasoning, rule priorities and dependencies, calculation formulas, looping-data-structure support, and a built-in set of computational, aggregate and other data processing functions. Rules and other system objects are stored in XML files that can be downloaded, modified, and uploaded to the online repository. Rule changes made online can be instantly deployed for runtime use by the applications integrated with the BRE. The forward chaining BRE parses XML application data against the ruleset, updates your data XML document, and returns it back to the application along with the comprehensive state information. Written in .NET, the BRE component can be utilized as a managed assembly, a COM object, or through the Web Service.

Developers simply upload their application, and Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring," the company said this morning in announcing the service. "At the same time, with Elastic Beanstalk, developers retain full control over the [Amazon Web Services] resources powering their application and can access the underlying resources at any time." Customers pay nothing for Elastic Beastalk, paying instead for the resources used to run their applications. Elastic Beanstalk provides a quick way for developers to make use of a range of Amazon services - Amazon EC2 (for computing power), Amazon S3 (for data storage), Amazon Simple Notification Service, Elastic Load Balancing, and Auto-Scaling.  "Elastic Beanstalk handles the provisioning and deployment of the infrastructure needed to run the application," the company said.

Google has pretty much given up on developing a JavaScript API for GMail. There was once a Greasemonkey script Google developed for GMail but that broke and Google shows no sign of fixing it. James Yu is now trying to fix that scenario with GMailr, a JavaScript API for GMail. It is made from the code he wrote for 0Boxer, an extension for GMail that turns organizing your inbox into a game. Yu is also a lead developer at Scribd. Yu said developing the API took him on a path fraught with frustrations and dead ends. He writes there is supported official JavaScript API for Gmail. The Greasemonkey script is broken and no one has yet released a frontend API for Gmail. He said he needed access to the various user actions in the UI as the backend APIs were not going to work as he wished. He decided to write his own library from scratch.