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.
If its just the "localizable display name" then what use is it in looking for the particular VQUERY? Isn't that the sole role for the QUERYID property? If not, when is NAME _not_ used (since the text says "Normally"...)?
Correct. They wanted a localizable display name. Not everyone has to support just one locale at a time.
Since later text says:
For a search, if the "TARGET" property is supplied in a "VQUERY" component, then the CS is to search for the query in the calid supplied by the "TARGET" property value.
I suspect that the 1st bit above is just poor phrasing and there is no actual intent of using NAME in some unspecified combination with QUERYID. However I dont want to second guess Dougs intent here.
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.
Doug Royer | http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@xxxxxxxxx | Office: (208)612-INET
http://Royer.com/People/Doug | Fax: (866)594-8574
| Cell: (208)520-4044Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature