[Cs5500] New Design For OpposeAction

[Karl Lieberherr]

I agree with Rashmi that Paarth's proposal is not an improvement.
It would send more information around than is needed. And this leads
to problems.

At this point in the project we only want to change the basic
structures if it is a clear
improvement for everybody.

-- Karl

On Sat, Mar 19, 2011 at 6:15 PM, rashmi nayak <rashmin at ccs.neu.edu> wrote:
> Hi Paarth,
>
> I think I did not understand you correctly. But from what I understand, here
> is what I think.
>
> As I understand  - If you are implementing the admin, the admin needs to
> process only the responses obtained from the Avatars. So you would be
> processing "oppose" <oppositions> List(OpposeAction).
>
> The avatar has to either agree, refute or strengthen each claim. So there is
> a one to one mapping between each OpposeAction in Response and each Claim in
> the "oppose"  <claimsToOppose> List(Claim)  in Request.
>
> So you are suggesting that instead of having the Admin loop through this
> mapping once to fetch which all claims have been agreed, strengthened or
> refuted, you would be changing the response to group these differently. Is
> my understanding correct?
> If so,  I see one problem here is that the Avatar may modify the Claims in
> refuting" List(Claim) "agree" List(Claim). So it will be Admin's
> responsibility to ensure that such Avatar's are punished.
>
> If I have misunderstood your suggestion, please let me know.
>
> Thanks,
> Rashmi
>
>
>
> On Sat, Mar 19, 2011 at 4:27 PM, Paarth Chothani <chothani.p at husky.neu.edu>
> wrote:
>>
>> Hi Folks,
>>
>> While doing implementation, we (BostonChargers) found that the design of
>> OpposeActions was not proper as, we had to iterate over "oppose"
>> <claimsToOppose> List(Claim) in the request to find out the claims which
>> have been strengthened, opposed & agreed.
>>
>> Here is our new design for OpposeAction:
>>
>> OpposeAction = "strengthen" List(Claim) "refuting" List(Claim) "agree"
>> List(Claim)
>>
>> where List(Claim) for strengthen will contain claims with updated
>> qualities
>>
>> List(Claim) for refute will contain the list of claims refuted
>>
>> List(Claim) for agree will contain list of agreed claims
>>
>> The advantage of having such design is that there is no need to iterate
>> over the "oppose"  <claimsToOppose> List(Claim) to figure out which claims
>> have been strengthened, opposed & agreed.
>>
>> Please let us know about this design change ASAP.
>>
>> --
>> Sincerely,
>> Paarth Chothani
>> Research Assistant & Graduate Student,
>> College of Computer & Information Science,
>>
>> Northeastern University.
>>
>> _______________________________________________
>> Cs5500 mailing list
>> Cs5500 at lists.ccs.neu.edu
>> https://lists.ccs.neu.edu/bin/listinfo/cs5500
>>
>
>
> _______________________________________________
> Cs5500 mailing list
> Cs5500 at lists.ccs.neu.edu
> https://lists.ccs.neu.edu/bin/listinfo/cs5500
>
>