Open Specifications Developer Center >
Open Specifications Forums
>
Using the Exchange Server Protocols
>
MS-OXCDATA 2.13.5.1 (Restrictions) table question
MS-OXCDATA 2.13.5.1 (Restrictions) table question
- In [MS-OXCDATA] — v20090712, the table on pages 99/100 is not very clear.
First of all, the last two rows of the table both refer to PropTag of "Multi-valued but not same as MultivalueInstance of table" and TaggedValue of "Single-valued", but contain different Support and Details cell entries. I believe that the last row should actually have TaggedValue of "Multi-valued". Is that indeed the case?
Secondly, the PropTag descriptions in the table are unclear. What exactly do the entries "Multi-valued and same as MultivalueInstance column of table" and "Multi-valued but not same as MultivalueInstance of table" mean? Does "Multi-valued and same as MultivalueInstance column of table" mean that the bit field of the PropTag in the restriction is the same as the MultivalueInstance bit field of the column? Since MultivalueInstance bit must not be set on the PropTag field in the restriction, does "Multi-valued and same as MultivalueInstance column of table" refer to the case when the table column also does not have the MultivalueInstance bit set? That does not seem to make sense given the actual Details descriptions involved.
Thanks.
Dan
All Replies
- Dan,
Thanks for your question. One of our team member will work on your question and get back to you when investigation is done.
Thanks!
Hongwei Sun -MSFT - Hi Dan,
I'll be looking into your questions. I will let you know as soon as I have an answer for you.
Best regards, Tom Jebo Senior Support Escalation Engineer Microsoft Open Specification Support - Dan,
Just letting you know that we're still investigating this to get you an explanation on the "Multi-valued and same as MultivalueInstance column of table" and "Multi-valued but not same as MultivalueInstance of table". I've filed a bug to correct the last entry in the supported cases table so it has a TaggedValue of "Multi-valued".
Best regards, Tom Jebo Senior Support Escalation Engineer Microsoft Open Specification Support - Dan,
I can confirm that the correction has been made in the last row of the multi-valued property support table and this correction will appear in future releases of MS-OXCDATA. The corrected TaggedValue column for that last row does indeed read "Multi-valued" instead of "Single-valued".
As far as the clarification or explanation of the "Multi-valued and same as MultivalueInstance column of table" (et al), I'm still awaiting and explanation. I'll let you know was soon as I have something.
Best regards, Tom Jebo Senior Support Escalation Engineer Microsoft Open Specification Documentation Support - Tom,
Can we get the TDI number for the correction, so we can see this come though to the docs?
Brad


