CC/PP and UAProf implementations?

Greetings all,

New to the list I've spent some time perusing the list archive and I've noticed the debate going on over the use of RDF and an XML representation of RDF in CC/PP. This debate has far-reaching implications as far as the future of UAProf is concerned and I find it confusing to see UAProf adopted while cc/pp is still in discussion.

The work on UAProf is indeed finished but I have not found any non-trivial UAProf implementation in cellular phones, the main deployment target. None of the dynamic aspects of capability updates through profile-diffs are implemented and I suspect that they aren't going to be for quite a while given the level of complexity that the whole RDF machinery requires on a cell phone (can someone prove me wrong please?). So UAProf on a cell phone does little more than "User-Agent" since the cell phone profile cannot be updated during a WAP session.

On the server-side, what is the impact of the java specification request on cc/pp? Does that mean that CC/PP is being cast to stone? I'm a little bit concerned that the current lack of working implementations on the client-side jeopardizes profile and capability information exchange; especially implementations in the cell phone space, where that kind of functionality makes a lot of sense.

I'm not arguing about what should be done next, I'm just trying to grasp the situation. Am I getting the right picture?

Best regards,

Alexis Le-Quoc
France Telecom R&D
alexis.lequoc@rd.francetelecom.com