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

RE: general questions

From: Jason Williams <jwilliams@wc-group.com>
Date: Mon, 20 May 2002 09:26:20 -0400
To: <Stan@rga.com>
Cc: <www-mobile@w3.org>
Message-ID: <EOEGKIBABLHKEKEOHBFBGEIMCGAA.jwilliams@wc-group.com>

> I believe that in most cases a sever local component could do the job

Arkdom PLUS is exactly that (www.arkdom.com).  It is a simple,
straight-forward, server-side component that can detect and provide
information for the given HTTP request or user-agent.  It is a great way to
complement other UA-Prof technologies and is updated regularly.  It may be a
good fit for your application.
The product brochure is here:

Best regards,

Jason Williams

-----Original Message-----
From: www-mobile-request@w3.org [mailto:www-mobile-request@w3.org]On
Behalf Of Stan@rga.com
Sent: Saturday, May 18, 2002 9:07 PM
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 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.

Stan Wiechers
Received on Monday, 20 May 2002 09:27:45 UTC

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