Deliverable Review Form

Identification of the deliverable or milestone
Project: EMI Deliverable or milestone identifier: D5.3.3
Title: DJRA1.3.3 – Security Area Work Plan and Status Report Doc. identifier: EMI-DXXX-CDSREF-Title-vx.x
Author(s): J. White Due date: 30/04

Identification of the reviewer
Name: E. Fernandez Affiliation: CSIC EMI Activity/External project or Institute: SA1/JRA1

Review date 04/18/2012
Author(s) revision date mm/dd/yyyy
Reviewer acceptance date mm/dd/yyyy

Reviewed document:

General comments

The document is well structured and well written. Mostly minor issues were found and detailed below. Some typos were also corrected (see attached document).

Additional recommendations (not affecting the document content, e.g. recommendation for future work)

Detailed comments on the content

Note 1: The reviewers must list here any observation they want to track explicitly and that require interaction with the authors
Alternatively all changes must be listed in the document itself using Word change tracking features (if you use Word)
Note 2: These comments have to be explicitly addressed by the authors and the action taken must be clearly described

Page Section Observations and Replies Is Addressed?
1 10 1 TOC of Section does not strictly follow 1.4. TERMINOLOGY does not exist (and could be the Glossary section), 1.5 References does not exist (and is instead available as section 6), 1.3. DOCUMENT AMENDMENT PROCEDURE is in Section IV Aha. You have to look at the "even newer" deliverable template at:
2 28 4 Missing Gantt chart for the overall technical area (as proposed in Again, new template does not need this. Gantt chart prepared by JRA1 manager, not area leaders.
3 12 2.1 All components are affected, but only a few detailed. Add some explanation why or detail all components I have added the sentence "The following EMI Security Area components have reported on the status of evolution work." to the end of the previous section. Most components don't need to report trivial matters.
4 13 2.2.3 Include reference to GGUS ticket OK, I have referenced the arcproxy buzilla list as this is what ARC works from.
5 13 2.2.3 Reference to 14 should be to 15? Probable reference 15 is wrong (bugzilla?) Fixed. Reference now after tracker and is indeed bugzilla. Attribute this to crappy editing software.
6 13 2.3.1 Put XACML AuthZ profile as reference Done
7 13 Please rephrase first paragraph, it's hard to follow  Paragraph re-arranged. Take a look?
8 17 Consider rephrasing first paragraph, the reasons for needing push mode should be stated before. Agree. Paragraphs re-arranged.
9 17 URC is not defined, typo? UNICORE Rich Client. Now defined.
10 18 2.12.1 "LCMPAS plugins will be replaced by code shared from the LCMAPS framework": are both LCMAPS? or should one of them be LCAS? Paragraph completely re-written.
11 19 2.13.1 CMC and CMP protocols, what are they?  Both added as references.
12 23 3 Some components are duplicated but do not have possible duplicate (e.g. nordugridmap). Yup. Added "edg-mkgridmapfile" to the table as the duplicate.
13 28 4.1.2 "How is the proxy maximum lifetime defined. In seconds, minutes or days?" -> I don't understand the issue, it's just a matter of deciding the units? Or having a default maximum lifetime?  Changed text to "Need to agree on a simple and intuitive way to define the maximum proxy lifetime and a reasonable default value."

Any other modification, spelling or grammatical corrections, etc must be done directly in the document using tracked changes or similar mechanisms that allows the authors to identify which correction is suggested.

-- FloridaEstrella - 12-Apr-2012

Topic attachments
I Attachment History Action Size Date Who Comment
Unknown file formatodt EMI-DJRA1.3.3-v0.3-enolfc.odt r1 manage 81.1 K 2012-04-18 - 11:03 UnknownUser v0.3 with corrected typos.
Unknown file formatodt EMI-DJRA1.3.3-v0.4.2-enol.odt r1 manage 99.0 K 2012-05-03 - 12:25 JohnWhite  
Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r6 - 2012-05-03 - JohnWhite
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback