Roger L. Costello wrote:
> Hey Robert,
>
>
>>><Lot id="1">
>>> .
>>></Lot>
>>><Picker id="John">
>>> .
>>></Picker>
>>><Assignment picker="John" lot="1"/>
>
>
>>I would hate to have transform this...
>
>
> Suppose that the purpose of your transformation was to move Picker John onto
> another Lot. (For example, a stylesheet that models the movement of Pickers
> on a Vineyard) Wouldn't this form support such a "movement transformation"
> beautifully?
Yes, but again this situation is quite simple. If all you needed to do
was move pickers to different lots. So pickers can be assigned to
different lots. What if you want to track their time spent on the lots:
<lot id="1">
<picker ref="John">
<timecard start="2005-01-29T12:00:00" end="2005-01-29T13:00:00"/>
</picker>
</lot>
<lot id="2">
<picker ref="John">
<timecard start="2005-01-29T13:00:15" end="2005-01-29T14:00:00"/>
</picker>
</lot>
>
> Simply locate:
>
> Assignment/@picker="John"
>
> And then change:
>
> @lot
>
> But this is getting off the topic: what is coupling? /Roger
Seems to be exactly about coupling, doesn't it? Maybe I should read more
definitions...
best,
-Rob
