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

Re: Restricting input depending on output

From: Drew McDermott <drew.mcdermott@yale.edu>
Date: Wed, 12 Mar 2003 08:31:05 -0500 (EST)
Message-Id: <200303121331.h2CDV4c26639@pantheon-po04.its.yale.edu>
To: www-ws@w3.org
CC: drew.mcdermott@yale.edu

   X-PH: V4.4@mr3
   From: Saied Tazari <Saied.Tazari@zgdv.de>
   X-Accept-Language: en, de, fa, ar
   Cc: www-ws@w3.org
   X-YaleITSMailFilter: Version 1.0c (attachment(s) not renamed)

   > 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)
	 (availableLocationList_In --here--> selectedLocationList_Out)
      despite making the sequence longer.

The same solution works in both places.

   . The natural meaning of PickOne says that only one location is
      selected but our requirement is that the value to be provided
      for selectedLocationList_In must be a **subset** of the value
      provided for availableLocationList_Out in the preceeding step.

Sorry, I missed that.  Since my hypothetical PickOne step is, indeed,
hypothetical, just rename it "PickSome" and the problem is solved.

                                             -- Drew McDermott
Received on Wednesday, 12 March 2003 08:31:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:37:08 UTC