RE: Need Information on DCCI

Hello Kedar, 
 
No problem. Interestingly, this is the second request I've had today about
implementations of DCCI.
 
The only ones I know about are not in the public domain. I suggest posting
a request to the public mailing list for UWA, the group that develops the
DCCI specification. That should be a good way to find out if there are any
implementations that are publicly available.
 
Best wishes
Rhys
 
[1] public-uwa@w3.org

  _____  

From: kedar phadke [mailto:kedar.phadke@gmail.com] 
Sent: 16 October 2007 15:27
To: Rhys Lewis
Subject: Re: Need Information on DCCI


Hello Rhys
sorry to bother you again but is there a sample implementation (Using DCCI
preferably in a web browser). I plan to build one but it would be nice if
one exists and I could refer to the same. I plan to have something like an
Active X control for DCCI. 
Could you help me by pointing me to some sample implementation. I know on
the web there are many requests for the same but no one has answered to
these requests so far. The only write up I have found so far is from Keith
Waters where in he explains something with an implementation example but
that seems to be his own implementation. 
 
Please could you help.
 
-Kedar

 
On 10/11/07, kedar phadke <kedar.phadke@gmail.com> wrote: 

Thank you. I will now re-read the documents on W3c
 
-Kedar

 
On 10/9/07, Rhys Lewis <rhys@volantis.com> wrote: 

Hi Kedar, 
 
Confusing isn't it?
 
DCCI is really the newer name for DPF. It's a client side API for
accessing device properties. Demonstrations of it have shown how
Javascript code can access device characteristics. Because it is on the
client, DCCI can access static and dynamic properties. 
 
UAProf is the OMA way of representing device characteristics in RDF. It's
really used by device manufacturers to define the properties of new
devices. It represents static properties. 
 
DCAP is a new effort at OMA to define a server-side interface to dynamic
properties. This involves transporting updated values back from the device
to a server and potentially caching them, of course. 
 
One you didn't mention is the W3C Device Description Repository API. This
is a server side interface for static properties.
 
And finally, the ontology is an attempt to underpin all the new work with
a shared view of device characteristics. The aim is to create an accurate
and powerful description of device characteristics to which the other work
can refer. 
 
To summarise the interfaces, DCCI is for access to static and dynamic
properties on the client. The DDR API is for server-side access to static
properties, and DCAP is for server side access to dynamic properties.
There is work going on to try and coordinate DDR API and DCAP. 
 
I hope that helps
 
Best wishes
 
Rhys


  _____  

From: kedar phadke [mailto:kedar.phadke@gmail.com] 
Sent: 09 October 2007 13:22 
To: rhys@volantis.com
Subject: Need Information on DCCI

 
Hello 
I am Kedar and was reading up on DCCI and other topics related to
Multimodal technologies. 
I have a question and a basic one I think
 
How are DCCI, DCONT, UAPROF, DPF, DCAP related to each other? 
I did look up on the internet and did see that DCCI is an interface and
UAPROF is a representation of Delivery Context(Static Props) and the
others also do pretty much the same thing.
 
If there is no relation between them then what are the differences?
 
Thanks in advance
 
-Kedar