W3C home > Mailing lists > Public > www-ws@w3.org > March 2003

Re: Restricting input depending on output

From: Saied Tazari <Saied.Tazari@zgdv.de>
Date: Wed, 12 Mar 2003 15:01:40 +0100
Message-ID: <3E6F3DC4.1040105@zgdv.de>
To: Drew McDermott <drew.mcdermott@yale.edu>
CC: www-ws@w3.org

Drew McDermott wrote:
>    
>    > Why not introduce a
>    > "select" step that picks one from a list?  Then you could have a sequence
>    > 
>    >     GetPostitCompositionPrerequisites
>    >       
>    >       >out>  availableLocationList_Out
>    >             =availableLocationList_In
>    >              >in>
>    > 
>    >                PickOne
>    > 
>    >                  >out>  selectedLocationList_Out
>    >                        =selectedLocationList_In
>    > 
>    >                           >=> 
>    > 
>    >                               StickPostit
>    > 
>    > You would need two 'sameValues' declarations to make this work.
>    > 
>    >                                              -- Drew McDermott
> 
>    Two problems:
> 
>    . That is shifting the problem from
> 	 (availableLocationList_Out --here--> selectedLocationList_In)
>       to
> 	 (availableLocationList_In --here--> selectedLocationList_Out)
>       despite making the sequence longer.
> 
> The same solution works in both places.

Maybe I coudn't explain the problem well.  With the above bullet I wanted to 
say that the proposed solution shifts the problem of "restricting 
selectedLocationList_In as a subset of availableLocationList_Out" to the 
need "to restrict selectedLocationList_Out as a subset of 
availableLocationList_In" (what you are simply assuming based on the 
human-understandable ID 'PickSome', without giving a machine-checkable 
restriction ).

-- Saied Tazari
Received on Wednesday, 12 March 2003 09:01:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:41 GMT