Daniel Silva, Marcos Caceres and myself have completed Phase 1 of Widget Packaging and Configuration compatibility testing. We have also detailed the results as part of the conformance matrix.
We would like to publish the results as a working group note. Phase 2 will begin in about 3 weeks, in which we are hoping to start working with vendors to improve overall conformance.
We need help with Phase 2: if you know a team contact for any of the targeted products that are claiming conformance to W3C Widgets, then would appreciate your help in making them aware of the results of the testing - Implementation Report: Widgets Packaging and Configuration.
Internationalization, or i18n, is the design and development of a product, application or document content that enables easy localization for target audiences that vary in culture, region, or language. Localization refers to the adaptation of a product, application or document content to meet the language, cultural and other requirements of a specific target market (a “locale”).
Adapting application to various languages is for me, as a Java and HTML developer, more than a common task. Usually the solution involves a set of supported locales, which is very often different from the system locale and/or browser configuration. Majority of such cases are covered by the scenario when user chooses particular language settings and the only place where the locale setting can be stored is the HTTP Session.
Support for this behavior is now handled by majority of frameworks; nevertheless there is still one HTML element that you can’t effectively change - the file upload form field.
Read the rest of this entry »
There is a lot of momentum around Semantic Web and RDFa.
This may be caused by the big milestone reached for RDFa, a Candidate Recommendation of RDFa in XHTML: Syntax and Processing.
Recently, several discussion threads have been started on the WHATWG mailing list around the effort of integrating RDFa into the HTML5 specification as XHTML1.1 and XHTML2 that will have it integrated.
While I was pretty aware of the Microformats activity, I can’t say the same about RDFa. But Manu Sporny makes it a lot easier. In fact, this is by far the most comprehensive explanation of RDFa that I have ever seen.
Read the rest of this entry »
Now that almost everyone has heard about HTML 5, maybe not all of you know what’s new for us developers.
Lachlan Hunt and James Graham have presented on 2008-05-29 at @media 2008 in London Getting Your Hands Dirty with HTML5.
I really find it a great presentation and a good start if you want to check what’s new with the new HTML/XHTML version.
Lachlan Hunt is also the editor of The Web Developer’s Guide to HTML 5. Any suggestions can be added to the wiki.
We are all welcome to contribute, so let’s get our hands dirty!
I’m really impressed about Microsoft responding to their customers and to the community.
Microsoft Expands Support for Web Standards
Company outlines new approach to make standards-based rendering the default mode in Internet Explorer 8, will work with Web designers and content developers to help with standards behavior transition.
Microsoft’s Interoperability Principles and IE8
We’ve decided that IE8 will, by default, interpret web content in the most standards compliant way it can. This decision is a change from what we’ve posted previously.
Microsoft recently published a set of Interoperability Principles. Thinking about IE8’s behavior with these principles in mind, interpreting web content in the most standards compliant way possible is a better thing to do.
That’s awesome. An unified industry can move forward.
Brendan Eich, creator of JavaScript, give a keynote at The Ajax Experience.
Ajaxian have placed the presentation online so everyone can read up on some of the thoughts and discussion on JavaScript 2 and more.
Here we got to hear from the mouth of someone deep into the ECMA process about what we are going to see in JavaScript 2 and importantly why:
Motivation for JS2
- Fix problems in JS1 that bug people daily
- A type system to enforce invariants
- instead of writing/debugging lots of value-checking code
- optional annotations, an extension to JS1
- Programming in the large
- Package system
- Visibility qualifiers (namespaces, private internal public)
- Optional static type checking
- Support bootstrapping and metaprogramming
- Self-host most of the standard objects
- Self-host compiler front end and type checker
- Reduce need for future ECMA Editions
As Brendan flicked through these slides, I couldn’t help buy realise how important the decisions are. These changes are probably going to profoundly effect all of our lives in the near future.
Coverage on the talk on InfoWorld
