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

general questions

From: <Stan@rga.com>
Date: Sat, 18 May 2002 21:06:40 -0400
Message-ID: <A9EFA28BE083D311ACEF0008C74FF53303E8AF38@norman.ny.rga.com>
To: www-mobile@w3.org
Hello!

I got experience in creating websites that adapt to output format and
special features of information appliances. The approach we had until now
was a if this than that and so on, by examining HTTP header. I was hoping
that we could use CC/PP to take that approach to the next level, reading all
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 problem
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 the
whole spec (default, user, ...) . Couldn't that be expressed in more simple
key/value method? 

3.) Most documents talk about a proxy server analyzing the request. Isn't
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 wondering
if there is a notification approach in development that lets registered
components know when there is an update of device profiles? Is there a DOM
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 by
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.

Best,
Stan Wiechers
Received on Saturday, 18 May 2002 21:07:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 13:00:00 GMT