RE: CC/PP and UAProf implementations?

Hello Alexis,
 
Previously I sent a number of postings on this list before to indicate
why the UAprof drafting committe was closed. Unfortunately, the closure
of the drafting committe coupled with an unfortunate, slightly confused
and misinformed discussion on this list has given some people the
impression that UAProf activity has closed. 
 
UAProf activity has not finished. The Open Mobile Alliance has continued
UAProf activity within the The Wireless Applications Group.  Even as I
type this message the OMA membership is voting on a change document to
UAProf. This emphasises that UAProf activity has not ended. 
 
Your second paragraph should be viewed in light of the fact that there
are very few WAP 2.0 deployments at the moment. I know that 4 major
manufacturers have implemented UAProf and that a number of others are in
the process of coming out with browsers that support UAProf.  Also a
number of other organisations are encouraging the use and implementation
of UAProf.  We can expect that OMA will update and improve UAProf over
time. The mobile arena is not a static space.
 
There are various views on CC/PP and its evolution. there are those who
feel it is complete and done. There are others who think that it needs
to be evolved. Some believe that RDF is the bees-knees others think that
there are practical issues that remain to be resolved.  Again there are
postings on this list that give an indication of the variety of opinions
in the area.  
 
 
 
Vidhya
 
p.s. in case there is any confusion the WAP forum merged into the Open
Mobile Alliance in June 2002.

-----Original Message-----

-----Original Message-----
From: LE QUOC Alexis FTRD/DMR/ISS
[mailto:alexis.lequoc@rd.francetelecom.com]
Sent: 15 July 2002 14:48
To: www-mobile@w3c.org
Cc: LE QUOC Alexis FTRD/DMR/ISS
Subject: 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

Received on Monday, 15 July 2002 11:46:00 UTC