The following abbreviations have been used for the reviewers: BC: BillCotton DP: DanielPonz HT: HansTerlouw KB: KlausBanse KR: KlausReinsch MU: MarkoUllgren NC: NicolaCaon PG: PrebenGrosbol VH: J.M.vanderHulst WP: WilliamPence Comments sorted after page are given below: ______________________________________________________________________ ++ 1 +++ p.000 - S0 - BC ++++++++++++++++++++++++++++++++++DD My biggest comment is that the document covers a number of issues which are related to, but different from, requirements for a software environment. These include application software that will run in the environment and parameter sets used to communicate between the environment and applications and between applications. Rather than try to define these other areas it would be better to reference the relevant documentation. Since the environment and applications using it are likely to be developed by different groups and maintained and distributed independently, defining and controlling the interfaces is important. For example, if (as seems desirable) the environment has the means to display online documentation provided by the applications, this interface needs to be spelled out with details such as format (HTML, XML, MS Help files :'{ ...) and localization, if any. Sections I would consider outside the bounds of this document include:2.1.7, 2.2.2 and most of 2.3 (unless the environment does more than provide access to directories and files). Section 2.3 also overlaps strongly with VO work; we shouldn't try to do this independently. Several sections include items which largely apply to applications include R1.3.4(?), R1.3.6(?), R1.4.4, R1.4.5, R1.4.6, R1.8.6, R1.10.2, R1.10.3, R1.10.5, R1.10.3. ---------------------------------------------------------------------- Reply: Discuss. It is true that both environment and application related requirements are included. They may be slight overlap with requirements for VO but this is not seen as a problem as long as they are important for data processing. In an implementation phase, one would expect to use VO products to satisfy such requirements. Firstly, the name of the documents should be changed to replace 'environment' with 'system' and it should be mentioned in the introduction that both environment and application requirements are included. Secondly, a new section for more explicit application related requirements should be added and the such requirements be moved to the new section. At this moments this would include requirements such as the ones mentioned above. ______________________________________________________________________ ++ 2 +++ p.001 - S0 - DP ++++++++++++++++++++++++++++++++++++ New section - include Table of Contents. It will improve readability of the document. ---------------------------------------------------------------------- Reply: Accepted. ______________________________________________________________________ ++ 3 +++ p.001 - S0 - KR ++++++++++++++++++++++++++++++++++++ LaTeX processing of document: A paragraph is missing at the end of the definition of \req just replace \newcommand{\req}[4]{\noindent\vspace*{3mm} \noindent\makebox[20mm][l]{\tt\bf #1 #3} \parbox[t]{14.0cm}{#2\hfill\\[2mm] \noindent\parbox{14.0cm}{\small\sl #4\hfill}}} % with \newcommand{\req}[4]{\noindent\vspace*{3mm} \noindent\makebox[20mm][l]{\tt\bf #1 #3} \parbox[t]{14.0cm}{#2\hfill\\[2mm] \noindent\parbox{14.0cm}{\small\sl #4\hfill}}\\ } % and remove \break directives from the document. Then all pages should be formatted properly. ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 4 +++ p.002 - S1.2 - DP ++++++++++++++++++++++++++++++++++++ Suggestion: Add references to OASIS, FITS, IRAF, AIPS, MIDAS. ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 5 +++ p.002 - S1.2 - PG ++++++++++++++++++++++++++++++++++++ references to FITS and OASIS should be added ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 6 +++ p.002 - S2 - DP ++++++++++++++++++++++++++++++++++++ First line. Change "... list below arranged in 3 subsection" by "... listed below arranged in 3 subsections" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 7 +++ p.002 - S2 - HT ++++++++++++++++++++++++++++++++++++ Propose change in text: "... listed below arranged in 3 subsections. ..." Further text change proposals will appear without comment. ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 8 +++ p.002 - S2 - KR ++++++++++++++++++++++++++++++++++DD Within each subsection requirements should be listed in order of priority in order to have the most important requirements visible at a glance. ---------------------------------------------------------------------- Reply: Discuss. Within each section the requirements will be resorted so that the most important will be at the start. Note - this will change the actual requirement reference number! ______________________________________________________________________ ++ 9 +++ p.003 - R1.1.1 - BC ++++++++++++++++++++++++++++++++++++ "astronomer" should be qualified as "computer knowledgeable astronomer". As stated, the requirement is unachievable. ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 10 +++ p.003 - R1.1.1 - VH ++++++++++++++++++++++++++++++++++++ ... system manageRs. ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 11 +++ p.003 - R1.1.1 - WP ++++++++++++++++++++++++++++++++++DD Does the reference to POSIX compatibility imply that the software need not run on Microsoft Windows? Many astronomers do much of their other "non-data analysis" tasks such as email, document preparation, spreadsheets, etc. on a Windows machine, and presumably would like to stay in that environment to also do their data analysis if possible. Windows compatibility should be encouraged, and at least given a "C" priority. ---------------------------------------------------------------------- Reply: Discuss. It is recognized as an issues but there exist several products for MS Windows systems which provides a POSIX compatible environment. One could use such products for running the environment on MS Windows systems. The overhead in requiring native MS Window compatibility is judged to be too high. The following will be added to the narrative: Several products for Microsoft Windows systems offer environments which can run POSIX compatible applications and systems. ______________________________________________________________________ ++ 12 +++ p.003 - R1.1.2 - KR ++++++++++++++++++++++++++++++++++++ This narrative basically repeats what is given under R1.1.5. At this point the narrative should describe the configuration tool itself. ---------------------------------------------------------------------- Reply: Accepted. The narrative will be replaced by the following text: It is important that installation and configuration of the standard system is as simple as possible in order to make it easily available. ______________________________________________________________________ ++ 13 +++ p.003 - R1.1.2 - MU ++++++++++++++++++++++++++++++++++++ The configuration tool should offer sensible default values to all configurable parameters ---------------------------------------------------------------------- Reply: Accepted. The following will be added to the narrative: Reasonable defaults must be provided by the tools so that a standard installation can be done with a minimum of interaction. ______________________________________________________________________ ++ 14 +++ p.003 - R1.1.2 - VH ++++++++++++++++++++++++++++++++++++ it is important THAT it can ... ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 15 +++ p.003 - R1.1.3 - HT ++++++++++++++++++++++++++++++++++++ "... as CL and GUI ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 16 +++ p.003 - R1.1.3 - VH ++++++++++++++++++++++++++++++++++++ ... most userS are likely ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 17 +++ p.003 - R1.1.4 - PG ++++++++++++++++++++++++++++++++++++ 'base system' -> 'sungle-user, standard system' ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 18 +++ p.003 - R1.1.5 - KR ++++++++++++++++++++++++++++++++++++ The logical order would be to place this requirement before R1.1.2. ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 19 +++ p.003 - R1.1.6 - KR ++++++++++++++++++++++++++++++++++++ This should better be priority "A". At a minimum the installation procedure should inform the user whether it completed successfully or not. ---------------------------------------------------------------------- Reply: Accepted. The following will be added to the narrative: At a minimum the installation procedure should inform the user whether it completed successfully or not. ______________________________________________________________________ ++ 20 +++ p.003 - R1.1.6 - VH ++++++++++++++++++++++++++++++++++++ ... to sit and wait (not site and wait) ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 21 +++ p.003 - R1.1.7 - KR ++++++++++++++++++++++++++++++++++++ This requirement potentially conflicts with R1.1.4 as a shared installation may always require some privileges. ---------------------------------------------------------------------- Reply: Accepted. With the change of the requirement to mention single-user installations, this conflict is removed. ______________________________________________________________________ ++ 22 +++ p.003 - R3.4.3 - HT ++++++++++++++++++++++++++++++++++++ "... and collections should ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 23 +++ p.004 - R1.1.10 - MU ++++++++++++++++++++++++++++++++++DD The binary installation packages should be compatible with the major software package management systems (such as yum) ---------------------------------------------------------------------- Reply: Discuss. It may be reasonable to rely on a software package management system on some platforms but it is not clear that a generic tool is available. The following will be added to the narrative: Several package management systems (e.g. yum, deb, and prm) exist which may serve as examples for high automated installation systems. ______________________________________________________________________ ++ 24 +++ p.004 - R1.1.13 - KB ++++++++++++++++++++++++++++++++++++ ... sum-check... => ... check-sum ... ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 25 +++ p.004 - R1.1.7 - PG ++++++++++++++++++++++++++++++++++++ 'single user' -> 'single-user' (also in other places) ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 26 +++ p.004 - R1.1.8 - KB ++++++++++++++++++++++++++++++++++++ Installation shall rely on general, commonly available tools (A) => Installation shall rely on tools commonly available on POSIX compliant platforms (A) ---------------------------------------------------------------------- Reply: Rejected ______________________________________________________________________ ++ 27 +++ p.004 - R1.1.9 - DP ++++++++++++++++++++++++++++++++++++ To improve readability, suppress the parenthesis. ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 28 +++ p.005 - R1.2.1 - BC ++++++++++++++++++++++++++++++++++++ It might be useful to mention cvs as an example. ---------------------------------------------------------------------- Reply: Accepted. The following sentence will be added: Several open revision control systems (e.g. cvs and subversion) are available and could form a basis for handling patches and updates. ______________________________________________________________________ ++ 29 +++ p.005 - R1.2.4 - DP ++++++++++++++++++++++++++++++++++++ Change "Recent (but not only last) patches..." by "Patches ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 30 +++ p.005 - R1.2.6 - DP ++++++++++++++++++++++++++++++++++++ Change "... take care of download and launch ..." by "... take care of downloading and launching ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 31 +++ p.005 - R1.2.6 - VH ++++++++++++++++++++++++++++++++++++ ... take care of THE download and launch ... ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 32 +++ p.005 - R1.2.7 - DP ++++++++++++++++++++++++++++++++++++ Change "(Not all users..." by "Not all users..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 33 +++ p.005 - R1.2.7 - NC ++++++++++++++++++++++++++++++++++++ Remove parenthesis before "Not all users ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 34 +++ p.005 - R1.2.7 - PG ++++++++++++++++++++++++++++++++++++ '( Not all' -> 'Not all' ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 35 +++ p.005 - R1.2.7 - VH ++++++++++++++++++++++++++++++++++++ ... first A download, FOLLOWED BY the installation ... ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 36 +++ p.006 - R1.2.10 - DP ++++++++++++++++++++++++++++++++++++ Change "Bug reports should have a unique a clear ..." by "Bug reports should have unique, clear ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 37 +++ p.006 - R1.2.10 - HT ++++++++++++++++++++++++++++++++++++ "... unique and clear ..." "... explicitly ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 38 +++ p.006 - R1.2.10 - MU ++++++++++++++++++++++++++++++++++DD A formal bug-reporting system (using a proper bug-reporting software such as Bugzilla) shall be established ---------------------------------------------------------------------- Reply: Discuss. For the environment it is essential to have a bug reporting system while for applications it would be desirable. The requirement should be upgraded to an (A) priority due to environment. The following will be added to the narrative: Several open problem reporting systems exist (e.g. gnat and Bugzilla) and could provide a well define work-flow for handling bug reports. ______________________________________________________________________ ++ 39 +++ p.006 - R1.2.10 - VH ++++++++++++++++++++++++++++++++++++ ... unique AND clear identifier ... ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 40 +++ p.006 - R1.2.8 - VH ++++++++++++++++++++++++++++++++++++ ... is produced, all the associated ... (omit "a new version of") ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 41 +++ p.007 - R1.3.2 - PG ++++++++++++++++++++++++++++++++++++ A reference to OASIS should be added ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 42 +++ p.007 - R1.3.3 - BC ++++++++++++++++++++++++++++++++++++ "indeces" => "indices" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 43 +++ p.007 - R1.3.3 - DP ++++++++++++++++++++++++++++++++++++ Change "Access to the information in document should ..." by "Access to the information in document must ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 44 +++ p.007 - R1.3.3 - HT ++++++++++++++++++++++++++++++++++++ "indices" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 45 +++ p.007 - R1.3.3 - NC ++++++++++++++++++++++++++++++++++++ "indeces" .. I think it's either indices or indexes ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 46 +++ p.007 - R1.3.3 - VH ++++++++++++++++++++++++++++++++++++ ... have indIces ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 47 +++ p.007 - R1.3.4 - VH ++++++++++++++++++++++++++++++++++++ documentation should BE THE SANE for all packages ... ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 48 +++ p.007 - R1.3.6 - KR ++++++++++++++++++++++++++++++++++DD Should be priority "A". It doesn't make sense for me that other requirements, like R1.3.1, R1.3.2, R1.3.3, have a higher priority if the existence of a documentation itself is not mandatory. ---------------------------------------------------------------------- Reply: Discuss. It should be upgraded to an (A) priority but it should be mentioned that tutorial only in some cases may be optional. The following will be added: Tutorials may not be relevant in some case and are therefore optional. ______________________________________________________________________ ++ 49 +++ p.008 - R1.3.7 - DP ++++++++++++++++++++++++++++++++++++ Change "Documentation must be addressed to two different communities: (1) end users, at different levels - novice, standard and expert -, on-line help and tutorials are addressed to this community and (2) developers, design documents and technical notes are typical documents. In addition a third community, namely system integrators should also be considered for system infrastructure and complex packages,..." by "Documentation must be addressed to three different communities: (1) end users, at different levels - novice, standard and expert -, on-line help and tutorials are addressed to this community, (2) developers, design documents and technical notes are typical documents and (3) system integrators,..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 50 +++ p.008 - R1.3.7 - VH ++++++++++++++++++++++++++++++++++++ here I propose to rewrite the text as: - novice, standard and expert -, containing: on-line help and tutorials, and (2) developers, containing: design documents and technical notes. In addition ... ---------------------------------------------------------------------- Reply: Accepted. See comment 49 above. ______________________________________________________________________ ++ 51 +++ p.008 - R1.3.8 - DP ++++++++++++++++++++++++++++++++++++ Change the requirements from "It is recommended that in-line code documentation of following an open standard format" to "It is recommended that in-line code documentation follows an open standard format" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 52 +++ p.008 - R1.3.8 - KR ++++++++++++++++++++++++++++++++++++ Some text seems to be missing in the formulation of this requirement. ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 53 +++ p.008 - R1.3.8 - NC ++++++++++++++++++++++++++++++++++++ First Sentence sounds odd: should it be "It is recommended that in-line code documentation follow an open standard format"? ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 54 +++ p.008 - R1.3.8 - PG ++++++++++++++++++++++++++++++++++++ It would be more reasonable with a priority 'B' ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 55 +++ p.008 - R1.3.8 - VH ++++++++++++++++++++++++++++++++++++ there is a symbol missing in the link in front of dimitry (was this a ~ sign?) ---------------------------------------------------------------------- Reply: Accepted. The actual reference has been moved to the first part of the document. ______________________________________________________________________ ++ 56 +++ p.009 - R1.4.1 - NC ++++++++++++++++++++++++++++++++++++ I would reword the paragraph in italic: "To ensure ... in the astronomical community, it is essential that no restrictions (including financial ones) exist for obtaining it." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 57 +++ p.009 - R1.4.2 - VH ++++++++++++++++++++++++++++++++++++ ... be useD to run the environment without ... ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 58 +++ p.009 - R1.4.3 - DP ++++++++++++++++++++++++++++++++++DD Change "Any non-free software must..." by "Any licensed software must ..." ---------------------------------------------------------------------- Reply: Discuss. It is important that all software having a restricting (e.g. non-free license) is marked. The best way should be discussed. ______________________________________________________________________ ++ 59 +++ p.009 - R1.4.3 - VH ++++++++++++++++++++++++++++++++++++ ... components if noT desired BECAUSE OF license ... ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 60 +++ p.009 - R1.4.4 - PG ++++++++++++++++++++++++++++++++++++ 'possible to users' -> 'possible for users' ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 61 +++ p.009 - R1.4.4 - WP ++++++++++++++++++++++++++++++++++DD It should be recognized that it is not always legally possible to release software under GPL. For example, software written by or for employees of the U.S. Government, generally cannot be released under GPL, although it may still be possible to make the software freely available to other users. ---------------------------------------------------------------------- Reply: Discuss. The explicit requirement for GPL will be replaced with the actual important points in this section. To the section introduction will be added: TO ensure this, the user should be granted the following essential permissions: right to free re-distribute of the system, free access to source code, and right to make code modifications when proper acknowledgment of the original authors is made. And R1.4.1 to: The standard system must have a license which allows re-distribution, free access to source code, and code modification. Add to narrative: The GPL provides a sample for such a license. and R1.4.4 to: General science packages should allow re-distribution, free access to source code, and code modification. and R1.4.6 to: Contributed science packages should be made available with permission to re-distribution, access to source code, and modify code. ______________________________________________________________________ ++ 62 +++ p.009 - R1.4.5 - VH ++++++++++++++++++++++++++++++++++++ Even with elaborate documentation available ...(no IS) ... reliable or Affected by special assumptionS. ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 63 +++ p.009 - R1.4.6 - VH ++++++++++++++++++++++++++++++++++++ ... in order to FACILITATE further usage (see R1.4.4) ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 64 +++ p.009 - S2.1.4 - BC ++++++++++++++++++++++++++++++++++DD Weapons restrictions. Some oppressive governments consider software to be a weapon and place export restrictions; this is especially a problem for encryption software. It's probably worth a point that any required software should be universally available, independent of licensing issues. ---------------------------------------------------------------------- Reply: Discuss. The introduction to the section will modified to emphasize this. See comment 61 above. ______________________________________________________________________ ++ 65 +++ p.009 - S2.1.4 - HT ++++++++++++++++++++++++++++++++++DD Software patents could also become a problem. Though the European Commission recently stated that computer programs are not patentable subject matter, software patents have already been granted by the European Patent Office. This could render software development a hazardous activity. I do not have a solution to this, but I think it is good to keep this in mind and try to influence bad developments in this area whenever possible. ---------------------------------------------------------------------- Reply: Discuss. The introduction of this section will be modified to mention this - see comment 61 above. ______________________________________________________________________ ++ 66 +++ p.009 - S2.1.4 - VH ++++++++++++++++++++++++++++++++++++ One must consider license ISSUES to ensure that ... ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 67 +++ p.010 - R1.4.4 - DP ++++++++++++++++++++++++++++++++++++ Change "For science progress..." by "To foster science progress..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 68 +++ p.010 - R1.4.5 - DP ++++++++++++++++++++++++++++++++++++ in last sentence, change "effected" by "affected" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 69 +++ p.010 - R1.5.1 - NC ++++++++++++++++++++++++++++++++++DD Maybe better: "It must be possible .... on a single user, desktop workstation or laptop". Then: "This requirement specifies ... as a low cost single user workstation or laptop, so as to provide ...." ---------------------------------------------------------------------- Reply: Discuss. The requirement and narrative will be changed as follows: It must be possible .... on a single user, desktop workstation or laptop. This requirement specifies ... as a low cost single user workstation or laptop, so as to provide .... ______________________________________________________________________ ++ 70 +++ p.010 - R1.5.3 - WP ++++++++++++++++++++++++++++++++++DD It would be better to at least recommend that the software also run under Windows. It will be much easier to support a software system on Windows if this requirement is considered from the beginning, rather than trying to convert the system to work on Windows at a later date ---------------------------------------------------------------------- Reply: Discuss. A sentence will be added to the narrative as the last by one: Several products offer a POSIX compliant environment on Microsoft Windows systems. ______________________________________________________________________ ++ 71 +++ p.011 - R1.6.2 - KB ++++++++++++++++++++++++++++++++++DD f77 must be supported (A) since some features of Fortran 77 are deprecated by now, e.g. arithmetic IF statements: IF (IA) 100,200,300 are now marked as obsolete by gcc, I suggest to rather go for F95 compliance ---------------------------------------------------------------------- Reply: Discuss. The explicit reference to a FORTRAN version will be removed. ______________________________________________________________________ ++ 72 +++ p.011 - R1.6.2 - KR ++++++++++++++++++++++++++++++++++++ The narrative reads a bit discriminating for astronomomers. The last two sentence could be replaced by: "A large number of highly sophisticated astronomical software packages written in Fortran exists and is still maintained and used by the community. An easy way to use this applications from within the environment must be provided." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 73 +++ p.011 - R1.6.2 - NC ++++++++++++++++++++++++++++++++++++ Only Fortran f77? What about Fortran 90/95? Shouldn't we supoort it too? ---------------------------------------------------------------------- Reply: Accepted. See comment 71 above. ______________________________________________________________________ ++ 74 +++ p.011 - R1.6.2 - WP ++++++++++++++++++++++++++++++++++++ It is becoming difficult to find a decent F77 compiler on some platforms, so it would be better to state that "Fortran F95 must be supported for development of components". ---------------------------------------------------------------------- Reply: Accepted. See comment 71 above. ______________________________________________________________________ ++ 75 +++ p.011 - R1.6.3 - MU ++++++++++++++++++++++++++++++++++DD "should" changed to "must". If C, C++ and FORTRAN are required and Java only recommended, the system would be obsolete right from the start. B->A ---------------------------------------------------------------------- Reply: Discuss. Priority changed to (A). And the text changed accordingly. ______________________________________________________________________ ++ 76 +++ p.011 - R1.6.4 - MU ++++++++++++++++++++++++++++++++++DD "should" changed to "must". If C, C++ and FORTRAN are required and Python only recommended, the system would be obsolete right from the start. B->A ---------------------------------------------------------------------- Reply: Discuss. Priority changed to (A). And the text changed accordingly. ______________________________________________________________________ ++ 77 +++ p.011 - S2.1.6 - VH ++++++++++++++++++++++++++++++++++++ ... programming languageS IS used ... ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 78 +++ p.012 - R1.6.4 - VH ++++++++++++++++++++++++++++++++++++ ... currently undergoing TREMENDOUS GROWTH in usage... ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 79 +++ p.012 - R1.6.6 - DP ++++++++++++++++++++++++++++++++++++ Change "(see above)" by "(R1.6.5)" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 80 +++ p.012 - R2.2.10 - PG ++++++++++++++++++++++++++++++++++DD It is very similar to R2.2.9 ---------------------------------------------------------------------- Reply: Discuss. Note typo in page no. should be p.21. The two requirements should be joint at follows: Naming convention for parameters should be defined and described in a directory. The two narratives will also be joined. ______________________________________________________________________ ++ 81 +++ p.013 - R1.8.1 - BC ++++++++++++++++++++++++++++++++++++ recorder => recorded ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 82 +++ p.013 - R1.8.1 - DP ++++++++++++++++++++++++++++++++++++ Change "...recorder and tracable" by "...recorded and traceable". ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 83 +++ p.013 - R1.8.2 - BC ++++++++++++++++++++++++++++++++++++ generation => generating ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 84 +++ p.013 - R1.8.2 - DP ++++++++++++++++++++++++++++++++++++ Change "...system will used the same ..." by "...system will use the same ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 85 +++ p.013 - R1.8.2 - KR ++++++++++++++++++++++++++++++++++DD Insert "of" after generation. I do not understand the meaning of the narrative. ---------------------------------------------------------------------- Reply: Discuss. Change last sentence of narrative to: To provide the end-user with consistent version information, it should be possible to transform the internal used information on version to a generic format. ______________________________________________________________________ ++ 86 +++ p.013 - R1.8.2 - NC ++++++++++++++++++++++++++++++++++++ Perhaps "Tools for generating version information ..."? And, next sentence, "used" --> "use" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 87 +++ p.013 - R1.8.4 - BC ++++++++++++++++++++++++++++++++++++ "No all users" => "Not all users" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 88 +++ p.013 - R1.8.4 - DP ++++++++++++++++++++++++++++++++++++ Change last word "...problems" by "...problem" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 89 +++ p.013 - R1.8.6 - VH ++++++++++++++++++++++++++++++++++DD a note: would it not be wise to demand that each program gives its version information as output, both in the log and other output generated? ---------------------------------------------------------------------- Reply: Discuss. Add to narrative: The version of the environment may be given when it is started. For individual application programs or tasks either the environment or the actual program could report. ______________________________________________________________________ ++ 90 +++ p.013 - R1.8.7 - DP ++++++++++++++++++++++++++++++++++++ Change last word "...releases" by "...released" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 91 +++ p.013 - R1.8.7 - HT ++++++++++++++++++++++++++++++++++++ "... are released." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 92 +++ p.013 - R1.8.7 - NC ++++++++++++++++++++++++++++++++++++ In last sentence, last word: "releases" --> "released" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 93 +++ p.013 - R1.8.7 - VH ++++++++++++++++++++++++++++++++++++ ... as they are releaseD. ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 94 +++ p.013 - R1.8.7 - WP ++++++++++++++++++++++++++++++++++DD In today's security conscious environment, it is unrealistic to expect system administrators will allow the whole world to have read access to the operational CVS (for example) code repository. Perhaps instead, snapshots of the repository could be periodically placed on a FTP site for public download. ---------------------------------------------------------------------- Reply: Discuss. Change of wording to: Read acess to the system source code should be possible. Add to narrative: The access could either be directly to the source code repository of special registered users or through a mirror/ftp site for generic access. ______________________________________________________________________ ++ 95 +++ p.013 - S2.1.8 - HT ++++++++++++++++++++++++++++++++++DD How should the "version" of a task be defined in this context? The behavior of a task can also be influenced by changes in libraries, both the environment's and others. ---------------------------------------------------------------------- Reply: Discuss. Add to section introduction: The final version may need to be a combination of the system/application version, the system build version, and the version and patch level of the operating system. ______________________________________________________________________ ++ 96 +++ p.013 - S2.1.8 - WP ++++++++++++++++++++++++++++++++++++ In practice, the issue of documenting versions is more complicated than implied here. Any applications software package usually depends on many other libraries and packages; It can become very complicated to document the exact version of every library that is used to build a particular release of the software. ---------------------------------------------------------------------- Reply: Accepted. See comment 95 above. ______________________________________________________________________ ++ 97 +++ p.014 - 2.1.9 - NC ++++++++++++++++++++++++++++++++++DD There is considerable overlap between 2.1.9 and 2.2.5. Maybe these two sections could be merged together into one? ---------------------------------------------------------------------- Reply: Discuss. The two section will be merged ______________________________________________________________________ ++ 98 +++ p.014 - R1.9.2 - DP ++++++++++++++++++++++++++++++++++++ Put in boldface the words fatal, warning, information and debug. ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 99 +++ p.014 - R1.9.3 - BC ++++++++++++++++++++++++++++++++++++ Last sentence garbled. ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 100 +++ p.014 - R1.9.3 - HT ++++++++++++++++++++++++++++++++++++ "meaaging" -> "the logging" ? (my guess...) ---------------------------------------------------------------------- Reply: Accepted. ______________________________________________________________________ ++ 101 +++ p.014 - R1.9.3 - KR ++++++++++++++++++++++++++++++++++++ The narrative should cover not only logging of errors but also logging of task executions, parameter substitutions, intermediate and final results. ---------------------------------------------------------------------- Reply: Accepted. When merged and restructures this will be added. ______________________________________________________________________ ++ 102 +++ p.014 - R1.9.3 - NC ++++++++++++++++++++++++++++++++++++ Last sentence: What's "meaaging system"??? ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 103 +++ p.014 - R1.9.4 - BC ++++++++++++++++++++++++++++++++++++ Is this the same as R1.9.3? ---------------------------------------------------------------------- Reply: Accepted. See comment 97 above. ______________________________________________________________________ ++ 104 +++ p.014 - R1.9.4 - MU ++++++++++++++++++++++++++++++++++++ The logging output should also be filterable on the software module level (as is with e.g. Log4J) in addition to the logging level filtering. ---------------------------------------------------------------------- Reply: Accepted. Add to narrative: Both environment and applications filtering of log/error levels should be provided that is the environment should be able to filter the log levels it prints and applications should be able to choose a appropriate level. ______________________________________________________________________ ++ 105 +++ p.014 - R1.9.4 - NC ++++++++++++++++++++++++++++++++++++ First sentence in italic: "equal to higher" --> "equal or higher" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 106 +++ p.015 - R1.10.2 - HT ++++++++++++++++++++++++++++++++++++ "... to verify ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 107 +++ p.015 - S2.1.10 - PG ++++++++++++++++++++++++++++++++++++ A requirement on benchmarking should be added. ---------------------------------------------------------------------- Reply: Rejected ______________________________________________________________________ ++ 108 +++ p.016 - R1.11.1 - BC ++++++++++++++++++++++++++++++++++++ "language in English" => "language is English" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 109 +++ p.016 - R1.11.1 - HT ++++++++++++++++++++++++++++++++++++ "... in English, ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 110 +++ p.016 - R1.11.1 - VH ++++++++++++++++++++++++++++++++++++ ... be designed SUCH that ... ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 111 +++ p.016 - R1.11.4 - MU ++++++++++++++++++++++++++++++++++++ Generating logs in languages other than English makes little sense, so I suggest removing "Logs in other languages..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 112 +++ p.017 - R1.12.2 - PG ++++++++++++++++++++++++++++++++++++ 'open interfaces' -> 'open interfaces and protocols' ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 113 +++ p.017 - R1.12.4 - PG ++++++++++++++++++++++++++++++++++++ It is very similar to R1.3.2 ---------------------------------------------------------------------- Reply: Rejected ______________________________________________________________________ ++ 114 +++ p.017 - R1.12.7 - HT ++++++++++++++++++++++++++++++++++DD I think it is better to bypass HTML and require XHTML, which is XML conforming. (see e.g. http://www.w3.org/TR/xhtml1/) ---------------------------------------------------------------------- Reply: Discuss. Re-phrased requirement as follows: Standard languages for access to Internet information must be supported Add to narrative: For the future, XHTML should be supported as HTML becomes obsolete. ______________________________________________________________________ ++ 115 +++ p.017 - S2.1.12 - MU ++++++++++++++++++++++++++++++++++++ New requirement of using existing (de facto) standard software packages instead of writing new code whenever possible should be added. ---------------------------------------------------------------------- Reply: Accepted. Add to section introduction: Further, one should always carefully check if existing standards can be used as new code is expensive both in terms of development and maintenance. ______________________________________________________________________ ++ 116 +++ p.017 - S2.1.12 - PG ++++++++++++++++++++++++++++++++++++ A requirement on access to VO services should be added ---------------------------------------------------------------------- Reply: Accepted. Add the following (A) requirement: Access to VO services must be supported. An increasing amount of data and computer services will become available through Vo services. It is essential to get full access to them. ______________________________________________________________________ ++ 117 +++ p.018 - R.1.13.1 - DP ++++++++++++++++++++++++++++++++++++ Change "...with commercial packages in an as much standard way as possible (although differences driven by the commercial packages themselves are to be taken into account" by "... with commercial packages in a standard way. Differences driven by the commercial packages themselves are to be taken into account at system integration". (?) ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 118 +++ p.018 - S2.1.13 - VH ++++++++++++++++++++++++++++++++++++ with EXTERNAL licensed, not exteranel licensed ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 119 +++ p.019 - R2.1.4 - KR ++++++++++++++++++++++++++++++++++++ Duplicate requirement. Logging is already covered in more detail by R1.9.1 to R1.9.5. ---------------------------------------------------------------------- Reply: Accepted. See comment 97 above. Section to be merged. ______________________________________________________________________ ++ 120 +++ p.019 - R2.1.4 - PG ++++++++++++++++++++++++++++++++++++ It is very similar to R2.5.1 ---------------------------------------------------------------------- Reply: Accepted. See comment 97 above. ______________________________________________________________________ ++ 121 +++ p.019 - R2.1.6 - HT ++++++++++++++++++++++++++++++++++DD Same remark as for S2.1.8. When a specific version is run at a different time, its behavior may be different due to changes in libraries. ---------------------------------------------------------------------- Reply: Discuss. Add to narrative: For practical reason, only a limit set of such older version may be provided. The main usage would be for applications for which significant changes have been made. ______________________________________________________________________ ++ 122 +++ p.019 - R2.1.6 - VH ++++++++++++++++++++++++++++++++++++ this requires old versions te be available. But surely one cannot expect that all previous versions are kept. So I suppose there is a practical limit to how far back one can go. ---------------------------------------------------------------------- Reply: Accepted. See comment 121 above. ______________________________________________________________________ ++ 123 +++ p.019 - R2.1.6 - WP ++++++++++++++++++++++++++++++++++++ supporting previous versions of a task is complicated because it implies that the previous version of all underlying libraries that were used to build the task must also be supported. This requirement could become very expensive to implement rigorously. ---------------------------------------------------------------------- Reply: Accepted. See comment 121 above. ______________________________________________________________________ ++ 124 +++ p.019 - R2.2.2 - HT ++++++++++++++++++++++++++++++++++DD It should be possible to access parameters in a 'polymorphic' fashion. E.g. a parameter of type 'float' should also be available as the exact string entered by the user. (Which could the be the number entered in fixed point decimal notation, scientific notation, as an expression, etc.) ---------------------------------------------------------------------- Reply: Discuss. Add to narrative: It should be possible to bypass such type and range checking in cases where the actual value is represented by a string e.g. an expression including mathematical functions. In such cases, checking would first be done in the application. ______________________________________________________________________ ++ 125 +++ p.019 - S2.2.2 - BC ++++++++++++++++++++++++++++++++++DD If this section must be included, it should also include arrays and doubles (unless floats are doubles) o R2.2.3 Why are parameter sets "ordered sequences"? o R2.2.6 Should defaults be handled by the environment or the application? The application will be much better equipped to understand any dependencies which would be difficult to express in general terms. ---------------------------------------------------------------------- Reply: Discuss. Replace 'float' with 'real'. Add narrative in R2.2.3 on key=value vs. positional parameters: To make manual input easier, it is convenient that parameters are defined as an order sequence as one then can avoid typing the actual parameters names if the values are given in the foreseen sequence. Add narrative in R2.2.6 on defaults: Generic defaults may be defined together with the parameter set. In some cases, it would be better to allow the application to provide defaults as it know more about the actual usage. ______________________________________________________________________ ++ 126 +++ p.019 - S2.2.2 - HT ++++++++++++++++++++++++++++++++++DD "Type" - I think there should also be provisions for structured semantic types like coordinates. To represent these as separate psets may be counter-intuitive. "Mode" - I propose three modes: 'hidden', accept the default without user intervention; 'defaulted', present default to user who then can accept it or enter a different value; 'mandatory', user has to provide value. In interactive mode the system should allow the mode to be overridden, e.g. 'hidden' parameters could be treated as 'defaulted'. "Value" - expressions should also be possible. "Default" - dynamic, context-dependent defaults should also be possible. "Error", "Min", "Max" - dynamic, context-dependent values should also be possible. "Prompt" - the task should be able to modify the prompt string depending on the current context. ---------------------------------------------------------------------- Reply: Discuss. See comment 125 above. ______________________________________________________________________ ++ 127 +++ p.021 - R2.2.4 - WP ++++++++++++++++++++++++++++++++++DD It is not clear how a user would specify the units when entering the value for a parameter. This requirement should be given a "B" instead of an "A" priority, since this is not an essential requirement for a software system. ---------------------------------------------------------------------- Reply: Discuss. The general feeling was that units are too important to have a (B) priority. ______________________________________________________________________ ++ 128 +++ p.021 - R2.2.7 - PG ++++++++++++++++++++++++++++++++++++ This goes only for relevant data such as real numeric values change 'for parameters' -> 'for relevant parameters' ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 129 +++ p.021 - R2.2.7 - WP ++++++++++++++++++++++++++++++++++DD It is not clear how a user would specify the uncertainties when entering the value for a parameter. This requirement should be given a "B" instead of an "A" priority, since this is not an essential requirement for a software system. ---------------------------------------------------------------------- Reply: Discuss. The general feeling was that units are too important to have a (B) priority. ______________________________________________________________________ ++ 130 +++ p.021 - S2.2.3 - BC ++++++++++++++++++++++++++++++++++DD User interfaces are the difficult bit between the "environment" and applications. It is desirable to have a common set of user interfaces among applications but the user interfaces need to be application aware. For instance, the environment needs to understand astronomical projected geometries but many applications may have similar requirements. It's probably worth having a couple items like: R2.3.x B The scripting environment should support common astronomical conventions such as projective geometries and magnitudes. R2.3.y B The scripting environment should allow support of application dependent conventions (e.g. time, wavelength specification conventions). ---------------------------------------------------------------------- Reply: Discuss ______________________________________________________________________ ++ 131 +++ p.022 - R2.2.10 - WP ++++++++++++++++++++++++++++++++++++ What is meant by "directory". This requirement is unclear. ---------------------------------------------------------------------- Reply: Accepted. See comment 80 above. ______________________________________________________________________ ++ 132 +++ p.023 - R2.3.1 - DP ++++++++++++++++++++++++++++++++++++ Change "The system can expected to be used by users of various..." by "Users of the system are expect to have various..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 133 +++ p.023 - R2.3.1 - HT ++++++++++++++++++++++++++++++++++++ "... can be expected to be used ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 134 +++ p.023 - R2.3.1 - NC ++++++++++++++++++++++++++++++++++++ Second sentence in italic: "in order execute heavy" --> "in order to execute heavy" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 135 +++ p.023 - R2.3.5 - DP ++++++++++++++++++++++++++++++++++++ Change "It is normally safer only to used local variable in procedures..." by "It is normally safer to use only local variables in procedures..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 136 +++ p.023 - R2.3.5 - HT ++++++++++++++++++++++++++++++++++++ "... to use local variables ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 137 +++ p.024 - 2.2.4 - NC ++++++++++++++++++++++++++++++++++++ Is there an unwanted page break before R2.4.1? ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 138 +++ p.024 - S2.2.4 - BC ++++++++++++++++++++++++++++++++++DD There is nothing about moving data around. Getting data from where it exists to where the computational power is available is the most difficult problem facing astronomical usage of distributed computing. It would be useful for this document to at least say if this is an environment or application responsibility. This seems to be a problem with no known general solution so a solution need not be spelled out. A couple missing items: R2.4.x A Resource locking with a task's ability to suspend until a resource becomes available. In particular, locking of disk files is critical as a way of coordinating processing in a distributed system. R2.4.y A Suspend or abort processes externally. R2.4.z B Pass parameters to executing process. It is useful to modify the parameters of long running processes. In particular, for iterative algorithms it is very useful to tell a process that its result is now acceptable and to shut down gracefully. ---------------------------------------------------------------------- Reply: Discuss. Add to section introduction: A general problem is often to join both compute power and data. This may involve strategies for migrating data to computer resources. Although no standard solution can be be given, it is frequently better to let applications deal with algorithmic problems and have the environment to do data migration if needed. Special high performance, data intensive applications may have to consider be data location and structure themselves. Add 3 proposed requirements. ______________________________________________________________________ ++ 139 +++ p.024 - S2.2.4 - HT ++++++++++++++++++++++++++++++++++++ "... more powerful systems ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 140 +++ p.025 - R2.4.1 - NC ++++++++++++++++++++++++++++++++++++ Perhaps "The system is intended to be used on many different ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 141 +++ p.025 - R2.4.2 - KB ++++++++++++++++++++++++++++++++++DD Parallel execution of tasks must be possible (A) Besides that, it should be possible to execute several instances of the system in parallel. ---------------------------------------------------------------------- Reply: Discuss. Upgrade R2.4.2 to priority (A). Add requirement with (B) priority : It should be possible to execute several instances of the system in parallel No only should the environment be able to execute tasks in parallel during one session but several independent instances of the environment should also be allowed to be executed. ______________________________________________________________________ ++ 142 +++ p.025 - R2.4.3 - BC ++++++++++++++++++++++++++++++++++++ "re-synchronize of execution" => "re-synchronize execution". ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 143 +++ p.025 - R2.4.3 - HT ++++++++++++++++++++++++++++++++++++ "... re-synchronize execution ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 144 +++ p.025 - R2.4.3 - VH ++++++++++++++++++++++++++++++++++++ ... re-synchronize execution ... (not A execution ...) ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 145 +++ p.025 - R2.4.4 - NC ++++++++++++++++++++++++++++++++++++ "some which" --> "some of which" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 146 +++ p.026 - 2.2.5 - NC ++++++++++++++++++++++++++++++++++++ Perhaps here too an unwanted page break before R.2.5.1 ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 147 +++ p.026 - S2.2.5 - PG ++++++++++++++++++++++++++++++++++DD This section should be compared to Sec.2.1.9 and split so that requirements related to the general environment and applications are split ---------------------------------------------------------------------- Reply: Discuss. See comment 97 above. Merge with S2.1.9 and split into environment and application parts when reasonable ______________________________________________________________________ ++ 148 +++ p.027 - R2.5.1-6 - KR ++++++++++++++++++++++++++++++++++++ A third approach to the subject of logging, cf. R1.9.1 to R1.9.5, and R2.1.4. ---------------------------------------------------------------------- Reply: Accepted. See comment 147 above. ______________________________________________________________________ ++ 149 +++ p.027 - R2.5.2 - PG ++++++++++++++++++++++++++++++++++++ Very similar to R1.9.5 ---------------------------------------------------------------------- Reply: Accepted. See comment 147 above. ______________________________________________________________________ ++ 150 +++ p.027 - R2.5.3 - BC ++++++++++++++++++++++++++++++++++++ "cut and past" => "cut and paste" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 151 +++ p.027 - R2.5.3 - DP ++++++++++++++++++++++++++++++++++++ Change "(e.g. cut and past)" by "(e.g. cut and paste)" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 152 +++ p.027 - R2.5.3 - NC ++++++++++++++++++++++++++++++++++++ "cut and past" --> "cut and paste" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 153 +++ p.027 - R2.5.4 - BC ++++++++++++++++++++++++++++++++++++ "analysis if often broken" => "analysis is often broken" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 154 +++ p.027 - R2.5.5 - BC ++++++++++++++++++++++++++++++++++++ "it only way" =? "the only way" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 155 +++ p.027 - R2.5.5 - KB ++++++++++++++++++++++++++++++++++++ Errors occurring during execution must be checked, ... That's an operational requirement, should not be here. ---------------------------------------------------------------------- Reply: Accepted. See comment 147 above. ______________________________________________________________________ ++ 156 +++ p.027 - R2.5.5 - NC ++++++++++++++++++++++++++++++++++++ Reword first sentence in italic as: "If tasks ... in batch mode, the only way to verify that all was done is to check the logs"? ---------------------------------------------------------------------- Reply: Accepted. See comment 147 above. ______________________________________________________________________ ++ 157 +++ p.027 - R2.5.5 - VH ++++++++++++++++++++++++++++++++++++ ... done is TO check the logs. ... ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 158 +++ p.027 - R2.5.6 - BC ++++++++++++++++++++++++++++++++++++ Same as R1.9.3 & R1.9.4? ---------------------------------------------------------------------- Reply: Accepted. See comment 147 above. ______________________________________________________________________ ++ 159 +++ p.027 - R2.5.6 - HT ++++++++++++++++++++++++++++++++++DD I would rather turn things around: always log as much us possible (within reasonable limits - the system should not become inefficient because of this) and allow this log to be filtered later on, e.g. by means of a log viewer which allows the level to be specified. ---------------------------------------------------------------------- Reply: Discuss. See comment 147 above. ______________________________________________________________________ ++ 160 +++ p.027 - R2.5.6 - KB ++++++++++++++++++++++++++++++++++++ It should be possible to specify the logging level (B). That's already specified in 1.10.4 ---------------------------------------------------------------------- Reply: Accepted. See comment 147 above. ______________________________________________________________________ ++ 161 +++ p.027 - R2.5.6 - PG ++++++++++++++++++++++++++++++++++++ Very similar to R1.9.4 ---------------------------------------------------------------------- Reply: Accepted. See comment 147 above. ______________________________________________________________________ ++ 162 +++ p.028 - R2.6.1 - HT ++++++++++++++++++++++++++++++++++DD I think GUIs _must_ be available, though not required for _every_ task. ---------------------------------------------------------------------- Reply: Discuss. Add new requirement with priority (A): It must be possible to support GUI's GUI's can frequently improve the usability of a system. Thus it is essential that the environment allow the development and deployment of GUI's. ______________________________________________________________________ ++ 163 +++ p.028 - R2.6.1 - PG ++++++++++++++++++++++++++++++++++++ Should have priority 'B' ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 164 +++ p.028 - R2.6.3 - PG ++++++++++++++++++++++++++++++++++++ Should have priority 'B' ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 165 +++ p.028 - S2.2.6 - MU ++++++++++++++++++++++++++++++++++DD The priority of GUIs in general should be raised from C to B at least ---------------------------------------------------------------------- Reply: Discuss. Only R2.6.1 and R2.6.3 to priority (B). ______________________________________________________________________ ++ 166 +++ p.028 - S2.3.1 - BC ++++++++++++++++++++++++++++++++++++ in text, "that all quantify" probably should be "that all quantities". ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 167 +++ p.029 - R3.1.2 - HT ++++++++++++++++++++++++++++++++++++ "... to associate the ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 168 +++ p.029 - R3.1.3 - HT ++++++++++++++++++++++++++++++++++++ "..., it is very ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 169 +++ p.029 - R3.1.4 - DP ++++++++++++++++++++++++++++++++++++ Change "It should be possible to used powers..." by "It should be possible to use powers..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 170 +++ p.029 - R3.1.4 - HT ++++++++++++++++++++++++++++++++++++ "... to use powers ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 171 +++ p.029 - R3.1.7 - BC ++++++++++++++++++++++++++++++++++DD This is REALLY application specific and shouldn't be in a general definition. ---------------------------------------------------------------------- Reply: Discuss. To be moved to an application section. ______________________________________________________________________ ++ 172 +++ p.029 - S2.3.1 - HT ++++++++++++++++++++++++++++++++++++ "quantify" -> "quantities" ? ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 173 +++ p.030 - R3.2.2 - HT ++++++++++++++++++++++++++++++++++++ "... celestial coordinates should be supported ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 174 +++ p.030 - R3.2.2 - NC ++++++++++++++++++++++++++++++++++++ Last sentence in italic seems to be incomplete ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 175 +++ p.030 - R3.2.2-3 - KR ++++++++++++++++++++++++++++++++++++ References given in the requirement should be synchronized with those given in the narrative. ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 176 +++ p.030 - S2.3.2 - PG ++++++++++++++++++++++++++++++++++DD A requirement on support for solar/planetary coordinate systems should be added. ---------------------------------------------------------------------- Reply: Discuss. Add new requirement at (B) priority: Solar and planetary coordinate systems should be supported. The support for coordinate systems related to the surface of planets and stars is important for several areas of astronomy and should be given. ______________________________________________________________________ ++ 177 +++ p.030 - S2.3.2 - VH ++++++++++++++++++++++++++++++++++DD ... astronomical coordinatE systems Here I have a serious comment: in my opinion any decent astronomical software system MUST be able to handle coordinate systems and also transformations between the different coordinate systems. How can one otherwise compare different data sets (say radio and optical) properly as they usually come with their own projection system. In my opinion 3.2.2 - 3.2.5 should read MUST BE SUPPORTED, rather than should be supported. This is then something to debate at the face-to-face meeting. I feel strongly about this from the radio experience where coordinate systems have always been an important part of the software. In the era of VO the first thing we should get right is a common data structure and common coordinate systems (including conventions for redshift, velocity, frequency, wavelength and time). ---------------------------------------------------------------------- Reply: Discuss. Add to section introduction: The support for astronomical coordinate systems is essential when data sets from different sources are merged or compared. In an era where large, diverse data collections become available, through VO services, processing software must be able to deal with at least the most commonly used coordinate representation. Possibly upgrade priorities. ______________________________________________________________________ ++ 178 +++ p.032 - R3.3.9 - PG ++++++++++++++++++++++++++++++++++DD Very similar to R3.3.8 Note: during the face-to-face meeting it was suggested to remove 'hierarchical' from requirement R3.3.6 ---------------------------------------------------------------------- Reply: Discuss. Merger to one requirement at (A/B) priority: It should be possible to define data collections based on their meta-data The two narratives to be merged. ______________________________________________________________________ ++ 179 +++ p.032 - R3.4.1 - HT ++++++++++++++++++++++++++++++++++++ "... and functions must ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 180 +++ p.033 - S2.3.5 - PG ++++++++++++++++++++++++++++++++++DD Representation of numerics as strings should be mentioned ---------------------------------------------------------------------- Reply: Discuss. Add to section introduction: The basic data type important for astronomical data processing are listed. In addition to such basic types, string representation of numeric values should also be considered e.g. to express the number of significant digits for real values, or for expressions to be evaluated. ______________________________________________________________________ ++ 181 +++ p.034 - R3.7.5 - PG ++++++++++++++++++++++++++++++++++DD Although this makes it possible to migrate data, it make be good to mention this explicitly. ---------------------------------------------------------------------- Reply: Discuss. Add to narrative: This requirement also allows explicit migration of data. ______________________________________________________________________ ++ 182 +++ p.035 - R3.8.3 - PG ++++++++++++++++++++++++++++++++++DD It should be mentioned that such multiple copies may have different versions ---------------------------------------------------------------------- Reply:Discuss. Add to narrative: Since individual copies of a data set may have different versions, it should also be possible to select the explicit version to be used. ______________________________________________________________________ ++ 183 +++ p.036 - R3.9.2 - HT ++++++++++++++++++++++++++++++++++++ "... well defined sets of ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 184 +++ p.036 - R3.9.3 - VH ++++++++++++++++++++++++++++++++++++ It must be possible to protect data against ... ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 185 +++ p.036 - R3.9.6 - PG ++++++++++++++++++++++++++++++++++DD Explicit version of data sets may need an explicit requirement as one may not be able to trust time stamps. ---------------------------------------------------------------------- Reply: Discuss. Add new (B) priority requirements: It should be possible to associated a version to a data set. The actual version of a data set is often determined from several meta-data items such as time of creation, origin, date of modification and name of application modifying it. Instead of comparing multiple meta-data items, it is simpler to associate an explicit version number to it. ______________________________________________________________________ ++ 186 +++ p.036 - R3.9.7 - HT ++++++++++++++++++++++++++++++++++++ "... will use the same ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 187 +++ p.036 - R3.9.7 - NC ++++++++++++++++++++++++++++++++++++ First sentence in italic "all tasks will used the" --> "all tasks will use the" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 188 +++ p.036 - R3.9.8 - HT ++++++++++++++++++++++++++++++++++++ "... apply a locking ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 189 +++ p.037 - R3.10.1 - NC ++++++++++++++++++++++++++++++++++++ Missing closing parenthesis at the end of paragraph in italic ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 190 +++ p.037 - R3.10.1-3 - KR ++++++++++++++++++++++++++++++++++DD Duplication of requirement R1.12.6. ---------------------------------------------------------------------- Reply: Discuss. Requirements to be merged with R1.12.6 ______________________________________________________________________ ++ 191 +++ p.037 - R3.10.2 - PG ++++++++++++++++++++++++++++++++++++ Partly similar to R1.12.6 ---------------------------------------------------------------------- Reply: Accepted. See comment 190 above. ______________________________________________________________________ ++ 192 +++ p.037 - R3.10.3 - HT ++++++++++++++++++++++++++++++++++++ "... to update such ..." ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 193 +++ p.037 - R3.10.3 - NC ++++++++++++++++++++++++++++++++++++ Last sentence in italic: "updated" --> "update" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 194 +++ p.037 - R3.10.3 - PG ++++++++++++++++++++++++++++++++++++ Partly similar to R1.12.6 ---------------------------------------------------------------------- Reply: Accepted. See comment 190 above. ______________________________________________________________________ ++ 195 +++ p.038 - Appendix - DP ++++++++++++++++++++++++++++++++++++ Suggestion - add the following terms under Acronyms (Note: they appear in the text...) GPL GNU XML CORBA HTML TAI UTC WCS IAU SI FITS ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 196 +++ p.038 - AppendixA - DP ++++++++++++++++++++++++++++++++++++ Separate into two different sections: A1 Definition of Terms and A2 Acronyms. ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________ ++ 197 +++ p.038 - SA - HT ++++++++++++++++++++++++++++++++++++ "... different components" ---------------------------------------------------------------------- Reply: Accepted ______________________________________________________________________