W3C home > Mailing lists > Public > www-mobile@w3.org > May 2002

RE: general questions

From: Vidhya Gholkar <vidhya.gholkar@argogroup.com>
Date: Mon, 20 May 2002 12:37:56 +0100
Message-ID: <ABB39CCA97F2D840BB0FEDDEBD5A4D040A9E9BCC@mail-svr1.elstead-ad.elstead.argogroup.com>
To: <www-mobile@w3.org>

1) Much of the present interest in CC/PP is within Universities and
research laboratories of a few big organisations. CC/PP is still
'emergent' technology. It has some way to go before it will be
recognised as a mature piece of work. For this reason many companies
have not bothered with it. Having said that within the mobile world the
WAP forum has produced the UAProf specification which is a cousin of
CC/PP. There are 4 phone manufacturers that are/have rolled out phones
which have a UAprof vocabulary. The best example of this is Sony
Ericsson http://mobileinternet.ericsson.com/UAprof/T68R1.xml. Today, to
my knowledge, the most comprehensive source of this information is
actually a free regularly updated device query web service called UDQ
http://udq.argogroup.com. This could be used within a CC/PP or a UAProf

2) CC/PP adopts RDF, but not everyone agrees that it should - there are
messages on this list which go into those issues in more detail.

3) Itis not necessary to use a proxy - that is just a specific
implementation. In general have a look at
http://www.w3.org/Mobile/CCPP/ as it contains useful info related to


-----Original Message-----
From: Stan@rga.com [mailto:Stan@rga.com]
Sent: 19 May 2002 02:07
To: www-mobile@w3.org
Subject: general questions


I got experience in creating websites that adapt to output format and
special features of information appliances. The approach we had until
was a if this than that and so on, by examining HTTP header. I was
that we could use CC/PP to take that approach to the next level, reading
the documents (I'm not a RDF guru) I'm left with some questions.

1.) My understanding is that companies creating devices and browsers are
supposed to create CC/PP definitions of their product which could be
used in
adaptive websites. Is/Are there an institution(s) collecting them? 

2.) From reading the spec  I found that using RDF doesn't make that
easier to solve. Wouldn't it make sense to take a more straigforward
approach? I like the idea of having several layers of specs making up
whole spec (default, user, ...) . Couldn't that be expressed in more
key/value method? 

3.) Most documents talk about a proxy server analyzing the request.
that already too specific? I believe that in most cases a sever local
component could do the job better. Related to question 1.) I was
if there is a notification approach in development that lets registered
components know when there is an update of device profiles? Is there a
like pseudo API for components that reflect device capabilities? How
does a
proxy server fit into the approach that user preferences are usually
accesible through components available on a app server and not accesible
the proxy server? At what point do all properties come together into a
unified object?

I would appreciate if someone could clarify these issues for me.

Stan Wiechers
Received on Monday, 20 May 2002 07:38:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:16:03 UTC