If you can make it quickly and easily
please do. I was planning on doing it that hard way. Excel format is
fine.
Technically for OASIS process purposes, we only have to account for the
ones received on the comment list during the public reviews. IT can
include others, but they are not required. I know Jan and Ludwick made
many comments on the TC list.
Hal
> -----Original Message-----
> From: Erik Rissanen [mailto:
erik@axiomatics.com]
> Sent: Tuesday, July 13, 2010 11:50 AM
> To: Hal Lockhart
> Cc: Tolbert, John W; Kim Goolsby; xacml TC; Mary McRae
> Subject: Re: [xacml] Requests for CS Ballots
>
>
> Hal,
>
> Thanks. I've been busy, but I can fix the jira issues tomorrow.
>
> Regarding the comment log, it's already done since we tracked the
> comments as issues. If you search backwards in the email
> archives, you
> will find my Excel sheet which contains all comments and what we
did
> with them. Maybe you need to clean it up a bit, but the info
> is already
> there. (Also, a PDF would be nice and simple. I can make it
> if you wish.)
>
> Best regards,
> Erik
>
> On 07/13/2010 05:15 PM, Hal Lockhart wrote:
> > Erik& John,
> >
> > I will generate the comment log.
> >
> > Can you check Jira for the issues and correct them?
> >
> > Hal
> >
> >
> >> -----Original Message-----
> >> From: Mary McRae [mailto:
mary.mcrae@oasis-open.org]
> >> Sent: Thursday, July 08, 2010 8:40 PM
> >> To: xacml TC
> >> Cc: Kim Goolsby; Kim Goolsby
> >> Subject: [xacml] Requests for CS Ballots
> >>
> >>
> >> On each of the following submission requests a link to an
> >> email was provided for the comment resolution log. This
> >> document, however, lists the changes made to the document
and
> >> does not identify any submitted comments and the response
to
> >> those comments. Please provide direct links to the comment
> >> resolution logs which should note a link to the email in
the
> >> xacml-comment archives, the name of the submitter, a brief
> >> summary of the comment and the resolution (action taken,
> >> changes made, no action taken, etc.) for each comment.
> >>
> >>
http://tools.oasis-open.org/issues/browse/TCADMIN-195
> >>
http://tools.oasis-open.org/issues/browse/TCADMIN-194
> >>
http://tools.oasis-open.org/issues/browse/TCADMIN-193
> >>
http://tools.oasis-open.org/issues/browse/TCADMIN-192
> >>
http://tools.oasis-open.org/issues/browse/TCADMIN-191
> >>
http://tools.oasis-open.org/issues/browse/TCADMIN-190
> >>
http://tools.oasis-open.org/issues/browse/TCADMIN-189
> >>
http://tools.oasis-open.org/issues/browse/TCADMIN-188
> >>
> >> In addition, several of the documents need some changes
to be
> >> made as noted in the comments on the issues; you should
have
> >> received emails from Kim noting the problems but staff
email
> >> is still not 100% functional so if you did not receive
those
> >> messages you can check the comments noted on the issues
(as
> >> well as TCADMIN-187 and TCADMIN-186) for the required
> >> changes. My apologies for the email problems; it is not
> >> expected to have staff email 100% functional (as well as
> >> aliases and autogenerated Kavi / Jira notifications until
> >> Monday at the earliest.
> >>
> >> Mary
> >>
> >>
> >>
> >>
>
---------------------------------------------------------------------
> >> To unsubscribe from this mail list, you must leave the
> OASIS TC that
> >> generates this mail. Follow this link to all your TCs in
OASIS at:
> >>
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
>>
>>