@y33liu: "Hi,
The proposals have been marked and will be returned at the end of 
tommorow's class. Please pay attention to following points when you revise 
the proposal:
1> Format. use a cover page please, and leave enough black space for 
comments. Put your id information on the cover page, you will loose 
mark for lacking of useid on the final proposal. But the professor is nice 
enought to let it go for the draft version this time.
2> Objective list. Use the formal objective list page format as in the 
assignments. we mark your project against this list, so please be careful 
on it
 Robin"
    @y33liu: "the tricky part is that we will not mark the revised proposal,
what we need  is its objective list ( not the one in the final 
document), we will use it  to mark your project. In this case, we need 
your signature on the objective list of proposal.
I know the process is a little bit complicated for a course project in 2
  weeks...   but that is the policy
 Robin
<quote>"
    @tkuchida: "I understand the need to sign the objective list, as it is a means of 
maintaining academic integrity.  However, I believe that signing before 
submitting the project gets away from the purpose of the declaration, which 
is to confirm (not foreshadow) that you have submitted your own work.  I 
assumed that the objective list would be signed at the demo, as both the 
student and the objective list would be present, and the project would have 
been submitted.  I guess this is a pedantic point, though, as we must follow 
the policy.
Tom
"Yingbin(Robin) Liu" <email_address> wrote in message 
news:<email_address>
<quote>"
    @akennber: "Why would you even submit a project that is not your own work? If you 
wanted to cheat then you'd still sign the list otherwise "you're giving 
it away"... so, just sign the objective lists... it's pretty straight forward.
Alex.
<quote>"
{'source': 'USENET', 'other_information': '{"reply_count": 3, "forum_name": "uw.cs.cs488.20140309.mbox"}', 'file': 'data/output/usenet-uw.cs.parquet'}