We at mBricks have been using WURFL for more than 18 months now. We
are now seeing the need for additional j2me capabilities to meet our
product's requirements.

While our DB is based on WURFL, we currently do a lot of manual
maintenance. This work is highly needed to meet the challenges of
Device Fragmentation. - Nevertheless, this is both time consuming and
expensive work.

For this reason, we would like to see more happening at the level of
J2ME developers working together on this common issue. In order to
put our money where our mouth is, we will invest resources and share
the data collected through our effort so far, with the rest of the
community. We hope that this will bring others to follow suit and get
everyone to benefit.

There are two main parts behind our initiative:
- Defining (or better, refining) the list of J2ME capabilities
currently in WURFL
- Creating a Midlet which people can download on their phones, to
automatically collect J2ME data and save them in a centralised
repository, for insertion into WURFL.

Of course, the model will be the usual WURFL one: the data will be
open and available to everyone free of charge and intellectual
property claims.

The model we envision is one where the WURFL J2ME developer community
will do its part by downloading the midlet and providing information
for devices that are relevant in their respective regions.

If you are interested in supporting the initiative, please comment on
the list of capabilities we provide, preferably over the next 7 days.
Likewise, feel free to comment or ask any question you may have.
After collecting the requirements, we will develop and deploy the
application for everyone in the community to use.

Here is the list of capabilities (we have kept the existing
capabilities already in WURFL, edited some of them):

brand
device_name
user_agent
j2me_cldc_1_0 (JSR-30)
j2me_cldc_1_1 (JSR-139)
j2me_midp_1_0 (JSR-37)
j2me_midp_2_0 (JSR-118)
doja_1_0
doja_1_5
doja_2_0
doja_2_1
doja_2_2
doja_3_0
doja_3_5
doja_4_0
j2me_jtwi (JSR-185)
j2me_mmapi_1_0 (JSR-135)
j2me_mmapi_1_1 (JSR-135)
j2me_wmapi_1_0 (JSR-30)
j2me_wmapi_1_1 (JSR-120)
j2me_wmapi_2_0 (JSR-205)
j2me_btapi (JSR-82)
j2me_3dapi (JSR-184)
j2me_loctapi (JSR-179)
j2me_nokia_ui
j2me_motorola_lwt
j2me_siemens_color_game
j2me_siemens_extension
j2me_heap_size
j2me_max_jar_size
j2me_rms_max_record_store
j2me_rms_max_record_number
j2me_rms_max_record_size
j2me_screen_width
j2me_screen_height
j2me_canvas_width
j2me_canvas_height
j2me_canvas_size
j2me_nokia_canvas_height
j2me_nokia_canvas_width
j2me_nokia_canvas_size
j2me_bits_per_pixel
j2me_audio_capture_enabled
j2me_video_capture_enabled
j2me_photo_capture_enabled
j2me_capture_image_formats
j2me_http
j2me_https
j2me_socket
j2me_udp
j2me_serial
j2me_gif
j2me_gif89a
j2me_jpg
j2me_png
j2me_bmp
j2me_bmp3
j2me_wbmp
j2me_midi
j2me_wav
j2me_amr
j2me_mp3
j2me_mp4
j2me_imelody
j2me_rmf
j2me_au
j2me_aac
j2me_realaudio
j2me_xmf
j2me_wma
j2me_3gpp
j2me_h263
j2me_svgt
j2me_mpeg4
j2me_realvideo
j2me_real8
j2me_realmedia
j2me_left_softkey_code
j2me_right_softkey_code
j2me_middle_softkey_code
j2me_select_key_code
j2me_return_key_code
j2me_clear_key_code
j2me_datefield_no_accepts_null_date
j2me_datefield_broken
j2me_root_certificate
has_qwerty_keyboard
platform (SE JP7, Nokia Series40, Series 60, etc.)
known_issues



Feel free to edit and suggest additional capabilities.

Thanks everyone!

Cato
mBricks