Re: CAP-12-a: 9.6 VQUERY Component - QUERYID/NAME

Doug replied on 09/04/2003 11:19:09 AM:
> > In CAP-12-a, under Section 9.6 VQUERY Component is written:
> > 
> >                                              Normally "NAME" and
> >   "QUERYID" properties are used when looking for a correct stored
> >   "VQUERY" component, or when storing a "VQUERY" component.
> > 
> > Im curious to know when we decided that the NAME property was to be 
used 
> > for identifying the VQUERY? 
> 
> Check the archives, I think the requirement came from CS&T and
> there were no objections.

What permutations of search do I use?  Using NAME and QUERY and some other 
values do not help since I get TONS of unrelated matches.  You seem to 
recall it so how about at least a Subject I can use?

The idea is interesting but there are LOTS of unanswered questions 
involved in using localized strings for identification.  The NAME is there 
as a friendly/display name for the QUERY ("What the hell does 
QUERYID:Fizbin32 do??" vs "Ah, QUERYID:Fizbin32 is displayed w/the 
'NAME:Fínd all calendars that Andrè owns'.") and not as part of searching 
for it.

Even if it was suggested, there is NO prose in CAP _now_ for when NAME is 
used, how it is to be used or when it is NOT used in conjunction with 
QUERYID in a VQUERY.  If (and thats a big if) the WG decides to use NAME 
in addition to QUERYID as part of VQUERY location then issues like dealing 
with specifying localization code pages used, etc need to be answered. 

I hope George or any of the former CS&T/Steltor folks can chime in here 
and help us out here since they are credited w/the proposal.

> Correct. They wanted a localizable display name. Not everyone has
> to support just one locale at a time.

The abilty to have > 1 NAME property per component is understandable but 
its not relevant to the need to finding a particular query. 

I can have multiple queries all with NAME:Widget but each MUST have a 
different QUERYID per VAGENDA.  Since QUERYIDs are unique per VAGENDA and 
NAMEs are not, what good is searching on both QUERYID and NAME??  None 
really since the NAME is only intended for display purposes rather than 
actual identification.

> I did not write that text. I'll change it to remove NAME:
> 
>   The "QUERYID" property specifies the local identifier for
>   a stored "VQUERY" component. The "NAME" property specifies
>   a localizable display name of a stored "VQUERY" component.
>   Normally the "QUERYID" property is used when looking for a correct
>   stored "VQUERY" component, or when storing a "VQUERY" component.
> 
> TARGET is used so that you can use stored QUERIES that are not in
> the current CMD/TARGET, such as when you have access to more than
> one calendar.

Thank you.  Also, strike the word "Normally" from the last sentence too. 
Otherwise you imply there is a 'non-normal' case but you never say what it 
is.  After all, how would you identify a particular stored query w/o a 
QUERYID?

Bruce
===========================================================================
Bruce Kahn                                INet: 
[email protected]
Messaging & Collaboration                 Phone: 978.399.6496
IBM Software Group                         FAX: and nothing but the FAX...
Standard disclaimers apply, even where prohibited by law...