Here are my minutes from the meeting related to 156 and 167. note: both
mention the use of policies:
156 - users who wish to select metadata and then issue
getContentRequest calls in a more productive manner
can do that now. joel asked: would it be useful to
define specific policies around implementations that
manage and protect for DoS and or other unexpected
"deep" query issues. we agreed to work discussion of
these policy into V3.
167 - joel asked: would it be useful to
define specific policies around implementations that
manage and protect for DoS and or other unexpected
"deep" query issues. we agreed to work discussion of
these policy into V3.
Your version of the resolution discussion for 156 does not include any of
this. here is yours for reference:
"Metadata is retrieved efficiently via SQL or XML Filter query.
User may issue separately issue a GetContentRequest call to"
In the version that you sent, the closed_date column for every row was
empty.
Joel
-----Original Message-----
From: Farrukh Najmi [mailto:]
Sent: Thursday, March 21, 2002 4:39 AM
To: Munter, Joel D
Cc: 'Oasis RR Comment Resolution'
Subject: Re: [regrep-comresolve] Issue list distribution: 3/19/2002
Joel,
Comments inline. Revised issues list attached. Thanks.
"Munter, Joel D" wrote:
> Farrukh,
> Thanks for your efforts here. Thanks for going to the Excel version. You
> have saved me much time while syncing email.
>
> I was a little surprised to see that our agreed resolutions were not
> completely recorded within the excel file and that the close date was not
> set. Can you please compare the resolutions that you have against the
> minutes that I recorded in our meeting on Monday.
I am not sure what issues and differences you are talking about and give me
specifics. I did not use your words
verbatim as it was agreed that I would do any final wordsmithing. Of course
I
may have missed something
important.
>
>
> Can you please highlight which issues are still open. A simple sort might
I have indicated which issues are close under closed_date column.
>
> work here. For some of the issues, the resolution text field appears to
> have been truncated. We also agreed that the resolution that you listed
This seems to be due to a bug in the auto-conversion tools. I have manually
fixed it. Thanks.
>
> against Issue 167 also applies to Issue 156.
I do not recall or see that. Please elaborate.
>
>
> Thanks,
> Joel
>
> -----Original Message-----
> From: Farrukh Najmi [mailto:]
> Sent: Tuesday, March 19, 2002 1:35 PM
> To: 'Oasis RR Comment Resolution'
> Subject: [regrep-comresolve] Issue list distribution: 3/19/2002
>
> Team,
>
> Attached is the revised issues list. It is now an Excel spreadsheet
> exported from the Issues db which I will no longer distribute. Please
> let me know of any corrections I need to make before I post to the main
> TC. Thanks for all your help.
>
> --
> Regards,
> Farrukh
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
--
Regards,
Farrukh
