Re: [provision] RE: SearchRequestType#query.

[Gary P Cole <Gary.P.Cole@Sun.COM>]

TargetID is optional for a provider with one target, so
omitting <query> would be an error if a provider exposes multiple targets.
That's a little surprising, since one might not expect to need <query> 
just to specify targetID.

I think we should move targetID out of <query> and into <searchRequest>.
It makes more sense to say that "targetID" is optional if there's only 
one target.

Bohren, Jeffrey wrote:

>The <query> element should be optional. All the information it defines are
>option, including target. One of the overriding principles the TC agreed
>already was that for a Provisioning Service with only one target (the Black
>Box case), the target ID is always options. 
>
>If the query is omitted, that should mean:
>
>Search for all PSOs, regardless of target or containment.
>
>Jeff Bohren
>BMC
>
>-----Original Message-----
>From: Gary P Cole [mailto:Gary.P.Cole@Sun.COM] 
>Sent: Saturday, July 23, 2005 4:45 PM
>To: Bohren, Jeffrey
>Cc: PSTC
>Subject: Re: SearchRequestType#query.
>
>Gary P Cole wrote:
>
>  
>
>>SearchRequestType#query is currently optional.  Is this correct? If 
>>this is correct, what behavior is expected if no query is specified?
>>
>>The spec currently states that a searchRequest must contain exactly 
>>one <query> element.
>>
>>    
>>
>I believe the spec is correct (and that SearchRequestType should require 
><query>).  At one time <query> might have been optional.  (A 
>searchRequest without a <query> might have acted a lot like a "listAll" 
>or "listChildren".) 
>
>However, as it stands right now, SearchQueryType currently contains the 
>"targetID" and "scope" attributes, as well as the <basePsoID> element.  
>Any search requires "targetID", and a function to "listAll" or 
>"listChildren" would want the "scope" and <basePsoID> arguments.
>
>If we think that the <query> element of SearchRequestType should remain 
>optional, we should probably move "targetID", "scope", and "basePsoID" 
>to SearchRequestType.  (That would, in effect, leave SearchQueryType as 
>a wrapper for open content query conditions.)
>
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  You may a link to this group and all your TCs in OASIS
>at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
>
>  
>