incorporated LG's comments PR 7

DMTN-049.tex

@@ -290,29 +290,32 @@ \subsection{Technical Considerations}
 
 \section{Letters of Recommendation} \label{sec:lor}
 
-This call for Letters of Recommendation (LOR) for the LSST Object PZ Data Products will be advertised broadly starting May 1 2021.
-Letters should be sent to mlg3k@uw.edu by Sep 30 2021, with a subject line beginning ``LSST Object PZ LOR".
+\textbf{Deadline:} Sep 30 2021.
+
+\textbf{Submission:} 
+In the spirit of open cooperation and collaboration towards our collective goal of generating LSST Object PZ that serve a wide variety of science goals, all letters will be public.
+Letters should be submitted by creating a new topic in the "Science -- Photometric Redshifts" category at \url{Community.lsst.org}\footnote{Start at this link, \url{https://community.lsst.org/c/sci/photoz}, click "+New Topic" at upper right, enter a title and text (do not worry about tags), and if applicable upload a PDF using the up-arrow icon in the menu bar.}.
+Use a title that starts with ``LOR" and provides a bit of detail, e.g., ``LOR for the CMNN PZ Estimator", ``LOR: PZ and Local Volume Science".
+Short letters could be presented in the text body of the new topic; longer letters could be provided by uploading an accompanying PDF.
 
 \textbf{Introduction:} 
 The Rubin Observatory Data Management (DM) team is tasked with constructing LSST Science Pipelines that produce science-ready data products, and this includes photometric redshift (PZ) estimates for the LSST data release (DR) Object catalog (e.g., \url{ls.st/dpdd}).
 As described in the LSST PZ Roadmap (\url{ls.st/dmtn-049}), DM will select one or more existing, community-vetted algorithms to generate Object PZ which, at least initially, meet a set of minimum scientific attributes and serve the widest variety of science applications.
 
 \textbf{LOR Purpose:}
 The Rubin science community has a considerable wealth of expertise in generating PZ catalogs and will be the primary users of the Object PZ data products.
-These letters provide a formal opportunity for the science community to define their minimum scientific needs regarding the LSST Object PZ data product. 
+These letters provide a formal opportunity for the science community to advocate for one or more photo-$z$ estimators that will meet their minimum scientific needs, and/or to define these minimum needs so that DM can consider them when shortlisting PZ estimators.
 
 \textbf{LOR Writers:}
 Any group or individual who would use the LSST Object PZ for their future scientific analyses, and/or are developers of potentially suitable PZ estimators, are encouraged to submit an letter.
 The DM team is especially interested in hearing the needs of scientists who plan to use the LSST Object catalog but who would/could not generate custom PZ estimates.
+LORs are not restricted to Rubin data rights holders.
 
 \textbf{LOR Scope:}
-Letters should recommend minimum attributes of the LSST PZ data product that would enable basic LSST science, describe the science that the LSST PZ data product should enable, and/or qualitatively recommend a certain PZ estimator (or type of estimator).
-Letters do not have to recommend a certain PZ estimator, and can just focus on describing PZ-related science needs.
-Quantitative analyses are beyond the scope of these letters, as are discussions on the research and development of new or improved algorithms.
-
-\textbf{Beyond the LORs:}
-The Rubin DM team will use these letters to inform the evaluation criteria used to select PZ estimators, and to assemble a shortlist of viable PZ estimators to be evaluated quantitatively using Rubin Commissioning data during the ``PZ Validation Cooperative" phase of the PZ Roadmap.
-Writing an letter is not required (and will not be construed as a commitment) to participate in the PZ Validation Cooperative. 
+Letters could qualitatively (or quantitatively) recommend one or more specific PZ estimators (or type of estimator), but they do not have to: letters could instead recommend minimum attributes of the LSST PZ data product that would enable basic LSST science, or focus on describing the science that the LSST PZ data product should enable.
+Discussions on the research and development of new or improved algorithms can be considered as beyond the scope of these letters, as the shortlist will only include currently existing PZ estimators. 
+New in-depth quantitative analyses of PZ estimator performance can also be considered as beyond the scope of the LORs because such analyses are the focus of the next stage of the PZ roadmap (see below).
+That said, no letters will be rejected for extending beyond these scope boundaries, which are provided just to guide and inform the community's efforts. 
 
 \textbf{Guidelines for PZ LORs:}
 \begin{itemize}
@@ -323,6 +326,11 @@ \section{Letters of Recommendation} \label{sec:lor}
 \item Refer to DMTN-049 for more detail about the roadmap, evaluation criteria, and LOR.
 \end{itemize}
 
+\textbf{Beyond the LORs:}
+The Rubin DM team will use these letters to inform the evaluation criteria used to select PZ estimators, and to assemble a shortlist of viable PZ estimators to be evaluated quantitatively using Rubin Commissioning data during the ``PZ Validation Cooperative" phase of the PZ Roadmap.
+DM might add viable PZ estimators to the shortlist if DM thinks that they meet the evaluation criteria and the community's scientific needs, even if they were not mentioned by any of the LORs.
+Writing a letter is not required (and will not be construed as a commitment) to participate in the PZ Validation Cooperative. 
+
 \subsection{LOR Template}
 
 \textbf{Title:} E.g., ``LOR on behalf of X science", or ``LOR for the X PZ Estimator". \\
@@ -331,7 +339,7 @@ \subsection{LOR Template}
 
 \begin{enumerate}
 \item Summary Statement -- 
-\textit{Provide a short statement that introduces the writers and the letter's main recommendation(s).
+\textit{Provide a short statement that introduces the writers' and the letter's main recommendation(s).
 Include the citations for any software discussed.
 }
 \item Scientific Utility --