RE: [VOC] Comments on the current version of the vocabulary

Hello everyone,

Please don't forget that accessing non-DDR properties server side is what
DCAP is doing in OMA. We don't want to duplicate that work. If you really
want a single API to cover both use cases, then MUCH closer cooperation is
going to be needed with OMA.

Also, while part of the API can be the same, I don't think it all can. For
example, connection to the API provider is likely to require different
information when that provider is DDR than when it is some dynamic
delivery context access mechanism. And don't forget that general queries
against arbitrary delivery contexts won't be supported by an API designed
to return information about the particular device instance currently
accessing an application. Such queries are absolutely required for tooling
that uses a DDR.

Sounds like modularisation is going to be needed if you want to achieve
this. You need to allow people that don't have a burning desire to access
the dynamic information not to have to implement it to be DDR compliant,
particularly as DDR is quite clearly for static information.

Best wishes
Rhys


  _____

From: public-ddwg-request@w3.org [mailto:public-ddwg-request@w3.org] On
Behalf Of Jo Rabin
Sent: 02 October 2007 12:52
To: jmcf@tid.es
Cc: public-ddwg@w3.org; DDR Vocabulary
Subject: RE: [VOC] Comments on the current version of the vocabulary



> scope is only to access properties that are in a DDR? With my
MyMobileWeb hat on I would like it to be an API for accessing any property
of

> the DC at the server side, as we are going to need it anyway  ...



that’s my assumption, anyway



Jo




  _____


From: jmcf@tid.es [mailto:jmcf@tid.es]
Sent: 02 October 2007 10:43
To: Jo Rabin
Cc: public-ddwg@w3.org; DDR Vocabulary
Subject: Re: [VOC] Comments on the current version of the vocabulary



Hi Jo,

Good point, this is something that I have been discussing with my
colleagues here while creating the table of properties used to analyse the
current situation of the vocabulary. There are properties that are
specific to the browser, other specific to the device itself, but others
that depend on the whole DC (depends on the browser, the device and other
elements that are in a delivery context, such as content transformation
proxy or the current user preferences:).

So is the DDWG in charge of defining such kind of properties?

Also when I think more and more on the API the same issue arises, is the
API an API for accesing any property of the Delivery Context or its scope
is only to access properties that are in a DDR? With my MyMobileWeb hat on
I would like it to be an API for accessing any property of the DC at the
server side, as we are going to need it anyway  ...

That's all for now

Best Regards

Jo Rabin escribió:

-----Original Message-----
From: public-ddr-vocab-request@w3.org [mailto:public-ddr-vocab-
request@w3.org] On Behalf Of José Manuel Cantera Fonseca
Sent: 01 October 2007 15:38
To: public-ddwg@w3.org; DDR Vocabulary
Subject: [VOC] Comments on the current version of the vocabulary


Dear all,

As a result of the analysis made on [1] here are the comments (coming
from me on behalf of the MyMobileWeb project) on the vocabulary (some of
them already known by Andrea, as I was chatting with him on the MSN :) ):

+ Usable Screen Width / Height. If I read the description, this is
something that will depend on the whole DC and it will be likely not
suitable for storing in a DDR. The value of this property will be
calculated and not stored



That doesn't stop it being part of the core vocabulary, surely?

Jo