• Widgets 1.0: Packaging and Configuration
  • Covers Zip packaging and XML configuration document
  • Defines the processing model for XML and Zip
• Widgets 1.0: Digital Signatures
  • XML Digital Signature profile
• Widgets 1.0: APIs and Events
  • All the functions, properties, and events you know and love.
  • I’ve asked Arve Bersvendsen, of Opera, to be the lead editor. Unfortunately, he is tied up till mid April… probably making something awesome for Opera.

Other specs may also follow, particularly:

• Widgets 1.0: Automatic Updates (I personally think this one is critical)
• Widgets 1.0: Cross-widget Communication

Other documents are still under development too:

• Widgets 1.0: Requirements
• Widgets landscape
  • A look at how widgets are created and what features are supported across popular widget engines.

We are aiming to have all these done (ie. Last Call) by October. However, now that the document split has happened, I should be able to get the packaging format done fairly quickly.

We have more or less now settled on the configuration language format. The elements are going to be:

• <widget width=”" height=”" id=”">
  • <title: the title/name of a widget
  • <description> a description
  • <author email=”" url=”"> some details about the author
  • <license> paste your GPL here!
  • <icon src=”"> the icon
  • <access network=”true|false” plugins=”true|false”> if your widget need to get online
  • <content src=”"> some file in the widget archive

Only <widget> and <content> are mandatory at this point.

The processing model for the XML is going to be quite forgiving. The only thing that will cause an error, is not having a well-formed document.  For example, the following the following would result in “The Awesome Super Dude Widget” as the title:

<widget xmlns="http://www.w3.org/ns/widgets">
   <title>
     The <blink>Awesome</blink> 

     <author email="dude@example.com">Super Dude</author> Widget</title>
</widget>

The unrecognized elements are simply ignored, but their text content is extracted. This makes processing more forgiving and allows for extensibility and some graceful degradation. I also want to push that the widget should function if the namespace is omitted.

We are also currently investigating how we are going to deal with internationalization in the configuration document format. We are looking at following ideas from the Best Practices for XML Internationalization.

According to the new proposed charter, the missions of the new working group is to:

…is to provide specifications that enable improved client-side application development on the Web, including specifications both for application programming interfaces (APIs) for client-side development and for markup vocabularies for describing and controlling client-side application behavior.

The new Web Applications Working Group is chartered with the continual development of the following specifications:

Another cool thing about the new working group is that it is modeled on the HTML Working Group, meaning that is open, transparent (no secret chats on the members list) and anyone will be able to participate via the public mailing list.

I’ll continue to edit the Widget Spec and Requirements, and possibly continue to help out with the XBL Primer.  I’ll continue to be part of this new working group for a least 1 year, as I my PhD program ends in March 2009… and hopefully longer, if someone gives me a job to continue working on specs!

• Went to Sydney for two days to work with Lachlan Hunt on the XBL Primer.
• Finished My PhD confirmation.
• Become a Facebook addict.
• Published Widgets 1.0 Requirements.

July is also going to be pretty intense:

• will try to get the First Public Working Draft of the XBL Primer by the 13th of July.
• Presenting my PhD confirmation on the 25th.
• Going to Melbourne on the 26th to work with Cameron McCormack for two days on a model for the XBL 2.0 Test Suite.

After I come back from Melbourne I go to Oslo for a WAF Face 2 Face to be held at Opera Software.

Share on Facebook ]]> http://datadriven.com.au/2007/07/june-wrap-up/feed/ 0 http://datadriven.com.au/2007/06/phd-by-mp3/ http://datadriven.com.au/2007/06/phd-by-mp3/#comments Fri, 22 Jun 2007 03:08:50 +0000 Marcos http://datadriven.com.au/2007/06/22/phd-by-mp3/ I’ve created audio versions of the various sections of my PhD Confirmation document (PDF ~1Mb). They are read by a AT&T natural voice called “Mel”:
• Summary.mp3 (3Mb, 3mins) – gives an overview of the document; helps you decide if this is going to be your cup of tea.
• Section1.mp3 (46Mb, 48mins) – discusses the issues with widgets and how standardization could help fix them.
• Section2.mp3 (14Mb, 15mins)- discusses the methodologies that can be used to fix the problems with widgets, and other relevant stuff.
• Seciton 3 is the Widgets 1.0 Requirements, which you can read at the w3c.

Files are all encoded in 32Khz, 16Bit, mono…. perfect for listening on any Mp3 Player. Document was converted to Mp3 using NaturalReader by Natural Soft.

UPDATE: added the latest draft of the widgets 1.0 requirements document.


Getting the document to be read smoothly required me to make a few minor editorial changes to the document:

• Replaced words like “I’ve” to “I have”, as the text-to-speech (TTS) engine was reading them as “I ve ee”.
• Put a full stop “.” on the end of every heading to force the TTS engine to pause before reading the next paragraph.
• Put either comas or full stops on all bulleted or numbered lists. The TTS engine reads lists as if they are a sentence.
Share on Facebook ]]> http://datadriven.com.au/2007/06/phd-by-mp3/feed/ 4 http://datadriven.com.au/2007/06/finished-confirmation-document/ http://datadriven.com.au/2007/06/finished-confirmation-document/#comments Wed, 20 Jun 2007 14:35:30 +0000 Marcos http://datadriven.com.au/2007/06/21/finished-confirmation-document/ Finally finished my PhD confirmation document (PDF ~1Mb) on Standardizing Widgets. This document is supposed represent all the research I’ve been doing into widgets over the last year or so. If you are interested in widgets and the standardization process, Section 1 might be of value. Please send me any feedback and let me know what I need to work on.

Hate reading on screen? Don’t want to kill trees?… download the confimation document as an Mp3 File (~76Mb, 1:21:36sec, 16Bit 24Khz) . It’s read by AT&T’s Natural Voice’s Mike.

On the 11th of July, I have to do a 40 minute presentation to a panel of academics to “confirm”… once I confirm I then have two years to finish all my publications…. It will be great to have two years to focus on the widgets specs. Hopefully we can get them to Rec.

Share on Facebook ]]> http://datadriven.com.au/2007/06/finished-confirmation-document/feed/ 0 http://datadriven.com.au/2007/06/may-wrap-up/ http://datadriven.com.au/2007/06/may-wrap-up/#comments Mon, 04 Jun 2007 08:32:40 +0000 Marcos http://datadriven.com.au/2007/06/04/may-wrap-up/ May was a fairly uneventful month. I spent most of my time just working on my PhD confirmation document (read the finished draft) and made but a few editorial changes to the Widgets 1.0 Requirements document.

I’m supposed to submit the confirmation soon (on June 13th to be exact). I still have a bit of work to do on it, especially in regards to methodology and a contextual review of widgets and widget engines… a contextual review basically looks at what widgets are, what they do, and what are the forces (markets, usefulness, web 2.0, etc) that are driving the continual popularity of widgets. As one can imagine, the contextual review is an ongoing process.

In regards to the requirements documents, I’ve was quite influenced by a chapter I read from the book Advanced Topics in Information Technology Standards and Standardization Research. In that book, there is a chapter title “Open Standards Requirements”, by Ken Krechmer, that provides a set of criteria for basically deciding if a standard is “open”. I took a few idea and used them in the requirements document to make sure that the standard remains “open” as defined by Krenchmer and that no one company controls it… even if not all widget engine vendors are taking part in the discussion.

Share on Facebook ]]> http://datadriven.com.au/2007/06/may-wrap-up/feed/ 0 http://datadriven.com.au/2006/08/on-the-origin-of-incomprehensibility/ http://datadriven.com.au/2006/08/on-the-origin-of-incomprehensibility/#comments Tue, 22 Aug 2006 07:06:33 +0000 Marcos http://datadriven.com.au/2006/08/22/on-the-origin-of-incomprehensibility/ I’m just starting to read On The Origin Of Objects by Brian Cantwell Smith for my PhD. My god! What a bunch of incomprehensible nonsense! The guy is talking about simple stuff (ontology, objects, properties), yet he uses the most convoluted language and metaphors ever. If I ever start writing like that, shoot me! Please. I have refraining from reading overly academic nonsense thus far for my PhD. Really! I don’t agree that you need to adhere to silly academic prose to get your point across. And it really makes me wonder why people make very interesting ideas completely inaccessible. I’m sure that Smith knows what he is talking about, but really! There is no need for this kind of unintelligible garbage:

“… a way to feed our undiminished yarning for foundations and grounding, while at the same time avoiding the reductionism and ideological fundamentalism that have so bedevilled prior fundamentalist approaches.” (p4)

“Bedevilled”? pelase! Anyway, now that I have vented I feel better. If I don’t end up throwing the book out the window in a fit of unintelligible rage, then I will move progressively review each chapter over the next three months. Pease note that I am not the only one that bitches about the complexity of this book, simply do a search for the book title, or look on Amazon, and you will see that I am not alone.

Share on Facebook ]]> http://datadriven.com.au/2006/08/on-the-origin-of-incomprehensibility/feed/ 0 http://datadriven.com.au/2006/04/initial-thoughts/ http://datadriven.com.au/2006/04/initial-thoughts/#comments Fri, 07 Apr 2006 05:27:27 +0000 Marcos http://www.datadriven.com.au/?p=4 I’ve been tyring to come up with some ideas about what areas to research for my PhD. I’ve given up my quest to try and create games using Semantic Web technologies. Instead, I plan to follow my current work practices and look at problems in web application development: As the starting point, I am particularly interested in how to build rich internet applications or rich web clients like those made by Google, flickr, etc.


For my PhD, I originally proposed to look at how games could be made using Semantic Web technologies (RDF(S) or OWL). Althought I still think it is quite a nobel idea, the reason for not following the games and Semantic Web line of enquiry include:

• Semamtic Web technologies do not seem to be taking off in a big way (Timbl would say, “you don’t get it“, but I think I do). I will still look at the Semantic Web in what I am researching (I will discuss in future entries in relation to microformats), but it will not make it the main focus of my research.
• Judging from the simple examples discussed in Robert Colomb’s forthcoming book on the Semantic Web, producing ontologies for games would be too massive a task. The problem is describing all the little rules and conditions that would take place in a game: basically it’s too hard and time consuming. I’m not going to go into it here as I am not interested in the problem. However, I think the problem might be able to be approached with the right visual tools. But again, not my problem
• As a carreer, I don’t really want to go into games development (or games in general). Sure, I like playing games; but I am not particularly good at drawing or design. Also, I’m no longer a 3D guy, nor have I really ever made a computer game… I can talk about some of the theory behind games (game structures, graphic communications, narrative structure, etc…), but I don’t feel comfortable persuing that area. It’s fun, but it’s just not for me. There are probably more reasons, but I can’t think of them right now.

Instead of persuing games and Semantic Web, I will stick to my roots: Web Application Development! Why? Well…

1. I’ve been doing web app development for about eight years now (I must be getting old!), so I guess (practically speaking) it’s what I know most about. Besides, it pays the bills.
2. I quite enjoy the problems that I encounter through web development: database design, user requirements, interface requirements, development strategies, standards adherence, cross-browser issues… so these problems are enough (I hope) to keep me interested for the next three years (for those who don’t know, that is the time needed to complete a PhD).
3. I am interested in learning ways of creating dynamic user interfaces. That is not to say that I am any good at creating user interfaces, but through practice hopefully I’ll get better at it.
4. I’m quite interested in the technical challenges that Web Accessability and usability create.
5. I’m quite interested in design patterns, both for programming and for multimodal user interfaces… I have to admit, I am a recent convert of visual design/interface patterns (but not yet a full believer! my semiotic roots influece my thinking).
6. I’m quite interested in the strategies used to build next-generation web applications. By next-generation web applications I mean rich internet applications (RIA), such as the one I am using to create this blog (wordpress), Google maps, Google Calendar, etc. These applications challange what most of web developers would consider a traditional web development approach: ie. developing for the standard client-server model where a data from a webpage is posted to a server, and a response page is sent back to the user by the server. In RIAs, the application is designed to continously send data to and from the server via an brokering (XMLHttpRequest) object. To the web development community, the coordination of asynchronous brokering of server requests without needing to reload a web page has become known as AJAX (Asynchronous JavaScript And XML – see also wikipedia definition of AJAX). Very sophisticated user interfaces have already been built using technologies such as AJAX (see those applications listed above). And, as a result, web developmers have had to think up new strategies for how to design the both the client-side and server-side of web applicaitons.

From a research standpoint, this last point (6) is of greatest interest to me: how can I, as a web developer (and not a computer scientist) create one of these new applications? The next question is what is driving the development of these new web applications?

For a reseach path, I need to start by defining these new web applications: what are they? why are they? where are they? how do I build one? and how is this new development approach different to other development approaches… refining what and how I am going look at will be the focus of my next few blog entries (this one is getting a bit long!).

Share on Facebook ]]> http://datadriven.com.au/2006/04/initial-thoughts/feed/ 0