Group items tagged

Jochen Bekmann, August 2009 - PDF

Response to marbux comments.

# See also my comment on the same web page that explains why HTML 5 is NOT it for document exchange between web editing applications. . - comment by marbux # Response to marbux supporting the WebKit layout/document model. Marbux argues that HTML5 is not interoperable, and CSS2 near useless. HTML5 fails regarding the the interop web appplications need. I respond by arguing that the only way to look at web applications is to consider that the browser layout engine is the web application layout engine! Web applications are actually written to the browser layout/document model, OR, to take advantage of browser plug-in capabilities. The interoperability marbux seeks is tied directly to the browser layout engine. In this context, the web format is simply a reflection of that layout engine. If there's an interop problem, it comes from browser madness differentials. The good news is that there are all kinds of efforts to close the browser gap: including WHATWG - HTML5, CSS3, W3C DOM, JavaScript Libraries, Google GWT (Java to JavaScript), Yahoo GUI, and the my favorite; WebKit. The bad news is that the clock is ticking. Microsoft has pulled the trigger and the great migration of MSOffice client/server systems to the MS WebSTack-Mesh architecture has begun. Key to this transition are the WPF-.NET proprietary formats, protocols and interfaces such as XAML, Silverlight, LINQ, and Smart Tags. New business processes are being written, and old legacy desktop bound processes are being transitioned to this emerging platform. The fight for the Open Web is on, with Microsoft threatening to transtion their entire business desktop monopoly to a Web platform they own. The Web is going to be broken. There is no way of stopping Microsoft at this point. What we can do though is focus on Open Web solutions that are worthy alternatives to Microsoft's proprietary push. For me, this means the WebKit layout/document model supported by Apple, Adobe and Google. ~ge~

A CMS expert argues for HTML over XHTML, explaining his reasons for switching. Excellent read! He nails the basics. for similar reasons, we moved from ODF to ePUB and then to CDf and finally to the advanced WebKit document model, where wikiWORD will make it's stand.

Note: discussion of annotations.

Whether 'annotation' in the Google Wave Protocol sense is comparable to annotation in the Diigo sense, I don't know

Note: annotation — com.google.wave.api.Annotation — within the API.

Whether 'annotation' in the Google Wave Protocol sense is comparable to annotation in the Diigo sense, I don't know

KINGSINE KS833 Three-phase Power Source Calibrator Item No.: 202004 ● Open protocol for software self-programming. ● AC voltage sources: 3x900V@3x25VA, accuracy 0.05%. ● AC current sources: 3x30A@3x25VA, accuracy 0.05%. ● 3-phase Harmonic Standard Power: 2-31x orders with 0.1 % accuracy.

KINGSINE KS823 Standard Source Meter Calibration Item No.: 202003 ● Open protocol for software self-programming. ● AC voltage sources: 3x900V@3x25VA, accuracy 0.05%. ● AC current sources: 3x30A@3x25VA, accuracy 0.05%. ● 3-phase Harmonic Standard Power: 2-31x orders with 0.1 % accuracy.

KINGSINE KS813 Three-phase AC Voltage Calibrator and DC Calibrator Item No.: 202002 ● Open protocol for software self-programming. ● AC voltage sources: 3x900V@3x25VA, accuracy 0.05%.