Reuse issue in DISelect

Dear all,

Another thread for another question. I'm envisaging the following issue 
with DISelect and has to do with the reuse of conditions.

Imagine I'm a developer and bacause of the requirements of my 
application I have to put the same selection conditions in several 
authoring units. During the lifetime of the project I realize that those 
conditions, that are spread over all the authoring units, are not 
accurate. So, to fix it, I will have to edit all the authoring units and 
change in all places my conditions.

Does DISelect have condition-reuse mechanisms that allow a developer to 
avoid this issue?

With respect to those conditions that only has to do with the delivery 
context subset composed by device properties (those found in the DDR), 
Wouldn't it better that the developer could define (externally) groups 
of devices, by means of logical conditions of belonging, and reference 
those groups logically in the select expressions within the authoring units?

If due to some reason the conditions change I will only have to change 
them in one place, outside the authoring units, that probably will be 
developed by designers with no deed knowledge of device specific 
technologies.

Thanks and best regards

Received on Thursday, 19 October 2006 10:26:07 UTC