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

I think it is in scope for the DDR, as we are talking about values that are "a priori" knowable. If the device has a fixed width screen and the browser makes the whole width available and the proxy doesn't mess with the content then you know, "a priori", what the usable screen width is. I think this is best described as "the usable screen width in this delivery context".

 

Jo

 

________________________________

From: Rotan Hanrahan [mailto:rotan.hanrahan@mobileaware.com] 
Sent: 02 October 2007 13:36
To: José Manuel Cantera Fonseca; Jo Rabin
Cc: public-ddwg@w3.org; DDR Vocabulary
Subject: RE: [VOC] Comments on the current version of the vocabulary

 

We're only doing an API for the DDR, not an API for the whole DC. The point of having a common ontology is to be able to work within a framework where the DDR API would be compatible with other APIs to access other aspects of the DC. I'm sure the MyMobileWeb people will ensure that their DC API is a superset of the DDR API, and that their additional (non DDR) properties will be communicated to the UWA for consideration in the common ontology being created by that group.

 

---Rotan.

 

From: public-ddr-vocab-request@w3.org [mailto:public-ddr-vocab-request@w3.org] On Behalf Of José Manuel Cantera Fonseca
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