19 Dec

On the Java Community Process: Expert Groups, JSRs, Observers and legal-related thoughts

Antonio Goncalves writes that Everybody should be able to easily observe JSRs.

Yes, I agree. But it really is more than just being able to observe. I was an Observer for the MSA 1.0 Expert Group (EG) and other EGs; but not all spec-leads are created equal. I quickly realized that for certain EGs, in this case MSA 1.0, being an Observer didn’t mean much as Observer’s input was not really taken into consideration and not followed up. A number of Observers were not happy about this, and I personally kind of gave up. Too bad, as it was their loss.

Part of the reason the EGs are closed is due to the Intellectual Property (IP) and related legal issues. That is the first thing that needs to be addressed, so that EGs can really become open. A true open process will have a common license and companies must be willing to give up the IP, otherwise, those companies unwilling to do that should remain on the proprietary business and not allowed to participate.

The other legal-related issue that needs to be addressed is that even though many people and companies contribute to a specific Java Specification (JSR), as I have, at the end the owner of the JSR is the company that led the JSR (i.e. Specification Lead); meaning that company will own all related IP created by all EG members, and that the company defines the licensing terms. I always found this totally unfair and this needs to changed as well.

As I predict, 2009 should be a big turning point year for Java, the JCP, and mobile Java…


18 Nov

JCP Elections 2008: A Good Day for the Developer Community

Thanks to everyone who voted for Sean at the JCP elections. The two with the most votes have been elected for JCP ME Executive Committee for the next three years. Having Sean at the EC is a very good thing, as he will represent the developer community; he understands well the issues and will push for changes — lets now hope the JCP will listen, accept and implement Sean’s recommendations:

  • Sony/Ericsson: 45.1%
  • Sean Sheedy: 36.8%
  • Aplix: 17.9%

Congrats Sean (and Sony Ericsson)!!!


12 Nov

Java Community Process 2008 Elections – Vote for Sean Sheedy

This upcoming November 17, 2008 is the last day of the JCP Executive Committee elections.

This year a number of individuals have chosen to run for the SE and ME seats side-by-side large companies; see the JCP Ballot. On the ME side, we have Aplix and Sony Ericsson running for election, and Sean Sheedy (individual).

And with this post, I would like to ask you to vote for Sean Sheedy for one of the ME seats (two are open).

Sean represents the developer community. Sean knows the mobile Java space, the issues involved both technical and poltical, he is passionate about it, he is vocal, and he really means and intents to make a difference. You can read Sean’s statement of why he is running for the seat.

While I considered running for election, I felt that Sean is a much better candidate; we talked about how to better serve the mobile Java developer community and the answer is for him to run, and for me to support him by helping reach developers, help disseminate information, and gather feedback from the developer community for Sean to use, who again, will be representing the developer community, which is a very good thing.

Note that to vote, you have to be a member of the JCP, but that joining the JCP is free for individuals.

For more information about how to participate see
JCP Java ME EC Election: Vote now for a Voice for Independent Developers (Terrence Barr’s Blog).


05 May

Just Say No to Fragmentation (and to JSR-324)

One of my Pet peeves is “why create unnecessary fragmentation?”.

A good example of such unnecessary efforts is JSR-324 the On Screen MIDlet API for Java ME, a JSR that basically attempted to duplicate functionality in MIDP3.

Submitted by Dave Kim of SK Telecom, and initially supported by someone within the following companies: Vodafone, Orange T-Mobile, Telefonica, Telecom Italia, Samsung, LG Electronics, SUN, Veloxsoft, JSR-324 is a prime example of someone ignoring all that is happening within the Java community, even after being approached by some of us, and instead decides to press forward to try to fulfill their own agendas.

Drives me nuts…

But fortunately for us, the JCP ME executive committee did their job and voted it Not Approved, with the recommendation of making this part of MIDP3, which is the right answer. Thanks.

You should read how the committee voted for this JSR – see JSR-324 Review Ballot. Anybody who voted Yes either don’t get it (or didn’t do their homework to understand what the hell is going on), or I hate to say, have their own agendas. Period. Not that I’m a conspiracy theory buff, but I can’t resist to say this JSR was network carrier-heavy supported; do network carriers want to take control of the idle screen? Nah, why would they want to do that?

I was surprised by some of the votes from the committee; Sun voted “abstain”, Time-Warner didn’t vote at all (why Time-Warner is in the Java ME committee is beyond me; probably because of OpenCable), and Jean-Marie, the only Individual ME committee member member voted “Yes and with no comment”; Jean you are supposed to protect us, the individual developers; that is why we voted for you.

After all these years, you would think people will know better by now…

The JSR-324 author should have saved his and everyones time and efforts and instead should have contributed any new/different ideas related to on-screen/idle screen to the MIDP3 public review.

Say no to fragmentation.


With this, I’m announcing the “Just Say No to Fragmentation Fund”. For just 50 cents a day, you can help create awareness of this important issue. In exchange we will send you a photo of a tormented developer who has suffered, either emotionally, financially or both (with some of them never recuperating), due to the pains of fragmentation… Operators are standing by.


08 Nov

Sean Sheedy running for the JCP Micro Edition Executive Committee


Sean Sheedy, a good friend of mine, is running for the Micro Edition Executive Committee at the Java Community Process.

Sean is a very passionate individual who has great ideas on representing the developer community. He has been involved in this space for a while, and understands this space, and what developers need. He is running as an individual (vs. a company) and his goals include helping close a number of gaps related to the JCP with respect to the developer community. I totally endorse Sean and I count on him to represent the rest of us.

The JCP EC elections runs to November 12. Vote for Sean.

For more information see:


29 Dec

Deadline for JavaOne Call For Papers is the worst possible time

I missed the deadline (again) for JavaOne submissions… December is just the worst possible time for this: the end of the year rush for both business + family, etc… JavaOne submission deadline should be sometime in January, as in the 2nd week of January… I had 2 very interesting BoF topics in mind – oh well, maybe next year…


26 Jul

The Mobile Internationalization API for J2ME, MSA, and MicroI18N to the rescue

One of “new” JSRs in the block is the Mobile Internationalization API (JSR 238). This specification defines localization resource file formats and their organization, and of course, the API itself to manage the resources.

With the Mobile Services Architecture specification (JSR 248), the mobile internationalization API is one of the mandatory JSRs to be present on handsets… but this is only true for the full MSA stack, and not for the MSA subset stack — recall that MSA defines a full stack and a subset stack.

So how can developers handle this situation, where the internationalization API may or not be present on the handset? This is when projects like Mary Jane Soft's MicroI18N (under LGPL license) comes to the rescue. With such solution available to us, by implementing some logic (runtime or build/deployment), the developer can use the device's native JSR 238 implementation if available (i.e. full MSA stack), and use/embed MicroI18N within the application for handsets that don't include JSR 238 (i.e. subset MSA).


[Via Wendong’s Smart Phone Weblog]